From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 00:07:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6933D16A4CE for ; Sun, 16 Jan 2005 00:07:20 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D79743D1F for ; Sun, 16 Jan 2005 00:07:17 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0G0Jf5B011549 for ; Sun, 16 Jan 2005 01:19:41 +0100 (MET) Message-ID: <41E9B02B.5070602@fer.hr> Date: Sun, 16 Jan 2005 01:07:07 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 00:07:20 -0000 What could be the reasons for "su root" to not work? I have a user that's in wheel group. Logging in as root works on the console, but su-ing from the user just writes 'Sorry', like the password's wrong. There are no clues in log files. /etc/pam.d/su is identical to another machine where everything works ok. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 00:09:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7235A16A4CE for ; Sun, 16 Jan 2005 00:09:37 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 322DF43D45 for ; Sun, 16 Jan 2005 00:09:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 30FAC519E7; Sat, 15 Jan 2005 16:09:36 -0800 (PST) Date: Sat, 15 Jan 2005 16:09:36 -0800 From: Kris Kennaway To: Ivan Voras Message-ID: <20050116000935.GA95376@xor.obsecurity.org> References: <41E9B02B.5070602@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <41E9B02B.5070602@fer.hr> User-Agent: Mutt/1.4.2.1i cc: stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 00:09:37 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote: > What could be the reasons for "su root" to not work? >=20 > I have a user that's in wheel group. Logging in as root works on the=20 > console, but su-ing from the user just writes 'Sorry', like the=20 > password's wrong. There are no clues in log files. >=20 > /etc/pam.d/su is identical to another machine where everything works ok. You forgot to mention what version (4.x doesn't use /etc/pam.d) Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6bC/Wry0BWjoQKURArEfAJ40YQJxUBA/SKSbwCmVZMnA5IhwcQCghrdy X0VJvX3Vlht60STNA+bDi68= =QS59 -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 00:19:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8551E16A4CE for ; Sun, 16 Jan 2005 00:19:43 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAFE843D2D for ; Sun, 16 Jan 2005 00:19:42 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0G0W75B022449; Sun, 16 Jan 2005 01:32:07 +0100 (MET) Message-ID: <41E9B316.6090402@fer.hr> Date: Sun, 16 Jan 2005 01:19:34 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41E9B02B.5070602@fer.hr> <20050116000935.GA95376@xor.obsecurity.org> In-Reply-To: <20050116000935.GA95376@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 00:19:43 -0000 Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote: >>/etc/pam.d/su is identical to another machine where everything works ok. > > You forgot to mention what version (4.x doesn't use /etc/pam.d) oops. 5.3-release. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 00:33:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D41FD16A4CE for ; Sun, 16 Jan 2005 00:33:35 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 874D843D2F for ; Sun, 16 Jan 2005 00:33:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 636C8513CE; Sat, 15 Jan 2005 16:33:34 -0800 (PST) Date: Sat, 15 Jan 2005 16:33:34 -0800 From: Kris Kennaway To: Ivan Voras Message-ID: <20050116003334.GA394@xor.obsecurity.org> References: <41E9B02B.5070602@fer.hr> <20050116000935.GA95376@xor.obsecurity.org> <41E9B226.40801@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <41E9B226.40801@fer.hr> User-Agent: Mutt/1.4.2.1i cc: stable@freebsd.org cc: Kris Kennaway Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 00:33:35 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote: > Kris Kennaway wrote: > >On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote: >=20 > >>/etc/pam.d/su is identical to another machine where everything works ok. > > > > > >You forgot to mention what version (4.x doesn't use /etc/pam.d) >=20 > oops. 5.3-release. OK. /etc/pam.d/su on 5.3 includes /etc/pam.d/system, so also make sure they're in sync. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6bZeWry0BWjoQKURArY1AKCjUXeAh7wsTpS7ydfqqt00F2D+qwCfWYi/ +FnVOXxf7033Cp6RoOig3MA= =Bma/ -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 00:51:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F70416A4CE for ; Sun, 16 Jan 2005 00:51:49 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C84A43D2D for ; Sun, 16 Jan 2005 00:51:47 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 3F9EE7A47 for ; Sun, 16 Jan 2005 00:51:45 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Sun, 16 Jan 2005 00:51:33 +0000 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501160051.33198.imobachgs@banot.net> Subject: USB mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 00:51:49 -0000 Hi all, Probably is my fault, but I can't get the mouse working on 5.3 STABLE. I've= =20 installed FreeBSD 5.3 RELEASE last night, and today I updated my sources an= d=20 rebuilt 'world'. I've googled for a while and I can't fix the problem, so I= 'm=20 posting the trouble to this list. I hope it's the correct list. Let me know= =20 if I'm wrong. Ok, when I start FreeBSD the mouse seems to be detected (usb mouse): ums0: Logitech USB Receiver, rev 1.10/17.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. However, I can't figure out how to configure moused with my mouse: I have t= his=20 settings in /etc/rc.conf: usbd_enable=3D"YES" usbd_flags=3D"" moused_enable=3D"YES" moused_type=3D"auto" moused_flags=3D"" moused_port=3D"/dev/ums0" But the mouse doesn't move on the console. And, when I fire up X.org,=20 everything goes right except the mouse stays in the center of the screen. Any tips about it? Thank you in advance and sorry if it's not the proper list. =2D-=20 Imobach Gonz=E1lez Sosa imobachgs at banot dot net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 01:18:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A1D516A4CF for ; Sun, 16 Jan 2005 01:18:20 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A038443D48 for ; Sun, 16 Jan 2005 01:18:19 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0G1Uh5B000082; Sun, 16 Jan 2005 02:30:44 +0100 (MET) Message-ID: <41E9C0D2.3000101@fer.hr> Date: Sun, 16 Jan 2005 02:18:10 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41E9B02B.5070602@fer.hr> <20050116000935.GA95376@xor.obsecurity.org> <41E9B226.40801@fer.hr> <20050116003334.GA394@xor.obsecurity.org> In-Reply-To: <20050116003334.GA394@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 01:18:20 -0000 Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote: > >>Kris Kennaway wrote: >>>>/etc/pam.d/su is identical to another machine where everything works ok. > > OK. /etc/pam.d/su on 5.3 includes /etc/pam.d/system, so also make > sure they're in sync. /etc/pam.d/system is the same as on the working system. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 03:24:30 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19E3A16A4CE; Sun, 16 Jan 2005 03:24:30 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5DCE43D39; Sun, 16 Jan 2005 03:24:29 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0G3OTlQ041376; Sat, 15 Jan 2005 22:24:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0G3OSRt066663; Sat, 15 Jan 2005 22:24:28 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A080F7306E; Sat, 15 Jan 2005 22:24:28 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050116032428.A080F7306E@freebsd-current.sentex.ca> Date: Sat, 15 Jan 2005 22:24:28 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/663/Tue Jan 11 17:44:48 2005 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 03:24:30 -0000 TB --- 2005-01-16 02:19:27 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-16 02:19:27 - starting RELENG_5 tinderbox run for i386/pc98 TB --- 2005-01-16 02:19:27 - checking out the source tree TB --- 2005-01-16 02:19:27 - cd /home/tinderbox/RELENG_5/i386/pc98 TB --- 2005-01-16 02:19:27 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-01-16 02:27:28 - building world (CFLAGS=-O -pipe) TB --- 2005-01-16 02:27:28 - cd /home/tinderbox/RELENG_5/i386/pc98/src TB --- 2005-01-16 02:27:28 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-16 03:18:56 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-01-16 03:18:56 - cd /home/tinderbox/RELENG_5/i386/pc98/src TB --- 2005-01-16 03:18:56 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 16 03:18:56 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug if_bge.ko ===> bktr ===> bktr/bktr cc -O -pipe -DPC98 -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/RELENG_5/i386/pc98/obj/pc98/tinderbox/RELENG_5/i386/pc98/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/RELENG_5/i386/pc98/obj/pc98/tinderbox/RELENG_5/i386/pc98/src/sys/GENERIC -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c: In function `vbi_read': /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: `FNDELAY' undeclared (first use in this function) /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: (Each undeclared identifier is reported only once /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr/bktr. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src/sys/modules/bktr. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src/sys/modules. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/obj/pc98/tinderbox/RELENG_5/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src. TB --- 2005-01-16 03:24:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-16 03:24:28 - ERROR: failed to build generic kernel TB --- 2005-01-16 03:24:28 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 03:32:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD1B216A4CE for ; Sun, 16 Jan 2005 03:32:34 +0000 (GMT) Received: from cedant2.abac.com (cedant2.abac.com [66.175.0.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852AC43D41 for ; Sun, 16 Jan 2005 03:32:34 +0000 (GMT) (envelope-from bob@vesterman.com) Received: from [192.168.0.11] (ool-44c40513.dyn.optonline.net [68.196.5.19]) (authenticated bits=0) by cedant2.abac.com (8.13.1/8.13.1) with ESMTP id j0G3WVoZ052736 for ; Sat, 15 Jan 2005 19:32:34 -0800 (PST) (envelope-from bob@vesterman.com) Message-ID: <41E9E37B.7020002@vesterman.com> Date: Sat, 15 Jan 2005 22:46:03 -0500 From: Robert William Vesterman User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41E9B02B.5070602@fer.hr> In-Reply-To: <41E9B02B.5070602@fer.hr> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 03:32:34 -0000 I have a similar problem, but only after I use X. I can su perfectly fine before using X, and I can su perfectly fine while using X (and a terminal window), but after exiting X, if I want to su, I have to reboot. Ivan Voras wrote: > What could be the reasons for "su root" to not work? > > I have a user that's in wheel group. Logging in as root works on the > console, but su-ing from the user just writes 'Sorry', like the > password's wrong. There are no clues in log files. > > /etc/pam.d/su is identical to another machine where everything works ok. > _______________________________________________ > 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 Jan 16 03:33:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4793116A4CE for ; Sun, 16 Jan 2005 03:33:47 +0000 (GMT) Received: from cedant2.abac.com (cedant2.abac.com [66.175.0.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2377C43D3F for ; Sun, 16 Jan 2005 03:33:47 +0000 (GMT) (envelope-from bob@vesterman.com) Received: from [192.168.0.11] (ool-44c40513.dyn.optonline.net [68.196.5.19]) (authenticated bits=0) by cedant2.abac.com (8.13.1/8.13.1) with ESMTP id j0G3XhD7053067 for ; Sat, 15 Jan 2005 19:33:46 -0800 (PST) (envelope-from bob@vesterman.com) Message-ID: <41E9E3C4.9050202@vesterman.com> Date: Sat, 15 Jan 2005 22:47:16 -0500 From: Robert William Vesterman User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <200501160051.33198.imobachgs@banot.net> In-Reply-To: <200501160051.33198.imobachgs@banot.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.44 Subject: Re: USB mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 03:33:47 -0000 I found that my USB mouse works if and only if I boot without APCI support. Imobach González Sosa wrote: >Hi all, > >Probably is my fault, but I can't get the mouse working on 5.3 STABLE. I've >installed FreeBSD 5.3 RELEASE last night, and today I updated my sources and >rebuilt 'world'. I've googled for a while and I can't fix the problem, so I'm >posting the trouble to this list. I hope it's the correct list. Let me know >if I'm wrong. > >Ok, when I start FreeBSD the mouse seems to be detected (usb mouse): > >ums0: Logitech USB Receiver, rev 1.10/17.00, addr 2, iclass 3/1 >ums0: 7 buttons and Z dir. > >However, I can't figure out how to configure moused with my mouse: I have this >settings in /etc/rc.conf: > >usbd_enable="YES" >usbd_flags="" >moused_enable="YES" >moused_type="auto" >moused_flags="" >moused_port="/dev/ums0" > >But the mouse doesn't move on the console. And, when I fire up X.org, >everything goes right except the mouse stays in the center of the screen. > >Any tips about it? > >Thank you in advance and sorry if it's not the proper list. > > > From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 04:14:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A89C16A4CF for ; Sun, 16 Jan 2005 04:14:57 +0000 (GMT) Received: from mortis.over-yonder.net (adsl-155-92-124.jan.bellsouth.net [68.155.92.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F0ED43D41 for ; Sun, 16 Jan 2005 04:14:56 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id C0C0520FBB; Sat, 15 Jan 2005 22:14:54 -0600 (CST) Date: Sat, 15 Jan 2005 22:14:54 -0600 From: "Matthew D. Fuller" To: CryBaby Message-ID: <20050116041454.GA2480@over-yonder.net> References: <20050116035709.AFCE.GUITAR@jazzcafe.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050116035709.AFCE.GUITAR@jazzcafe.no-ip.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.6i-fullermd.2 cc: freebsd-stable@freebsd.org Subject: Re: SSH Protocol mismatch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 04:14:57 -0000 On Sun, Jan 16, 2005 at 04:05:11AM +0800 I heard the voice of CryBaby, and lo! it spake thus: > OS: FreeBSD 4.11-STABLE #3: Fri Jan 14 23:53:07 CST 2005 > > I ssh my host by using putty or any ssh client in WindowsXP, and I > can't login lately. (But telnet and other services are ok.) Check that the version 1 protocol and/or PasswordAuthentication are enabled. I had to do one or both of those to let Putty work with sshd a while back; can't remember which it was. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 04:42:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9967D16A4CF; Sun, 16 Jan 2005 04:42:27 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4159243D53; Sun, 16 Jan 2005 04:42:27 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0G4gQiN045749; Sat, 15 Jan 2005 23:42:26 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0G4gPUS061666; Sat, 15 Jan 2005 23:42:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C377F7306E; Sat, 15 Jan 2005 23:42:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050116044225.C377F7306E@freebsd-current.sentex.ca> Date: Sat, 15 Jan 2005 23:42:25 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Scanned: ClamAV 0.80/649/Sun Jan 2 18:02:22 2005 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 04:42:27 -0000 TB --- 2005-01-16 03:24:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-16 03:24:28 - starting RELENG_5 tinderbox run for ia64/ia64 TB --- 2005-01-16 03:24:28 - checking out the source tree TB --- 2005-01-16 03:24:28 - cd /home/tinderbox/RELENG_5/ia64/ia64 TB --- 2005-01-16 03:24:28 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-01-16 03:32:30 - building world (CFLAGS=-O -pipe) TB --- 2005-01-16 03:32:30 - cd /home/tinderbox/RELENG_5/ia64/ia64/src TB --- 2005-01-16 03:32:30 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-16 04:34:36 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-01-16 04:34:36 - cd /home/tinderbox/RELENG_5/ia64/ia64/src TB --- 2005-01-16 04:34:36 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 16 04:34:36 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug if_bge.ko.debug if_bge.ko ===> bktr ===> bktr/bktr cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/RELENG_5/ia64/ia64/obj/ia64/tinderbox/RELENG_5/ia64/ia64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -g -I/tinderbox/RELENG_5/ia64/ia64/obj/ia64/tinderbox/RELENG_5/ia64/ia64/src/sys/GENERIC -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c: In function `vbi_read': /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: `FNDELAY' undeclared (first use in this function) /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: (Each undeclared identifier is reported only once /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr/bktr. *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/src/sys/modules/bktr. *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/src/sys/modules. *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/obj/ia64/tinderbox/RELENG_5/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/src. TB --- 2005-01-16 04:42:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-16 04:42:25 - ERROR: failed to build generic kernel TB --- 2005-01-16 04:42:25 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 06:58:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB2A116A4E2 for ; Sun, 16 Jan 2005 06:58:20 +0000 (GMT) Received: from smtp815.mail.sc5.yahoo.com (smtp815.mail.sc5.yahoo.com [66.163.170.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 6854243D49 for ; Sun, 16 Jan 2005 06:58:20 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noacks@swbell.net@70.240.249.100 with login) by smtp815.mail.sc5.yahoo.com with SMTP; 16 Jan 2005 06:58:20 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 59986622B; Sun, 16 Jan 2005 00:58:19 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 50161-09; Sun, 16 Jan 2005 00:58:16 -0600 (CST) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 5662D6215; Sun, 16 Jan 2005 00:58:16 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.1/8.13.1) with ESMTP id j0G6wFer089752; Sun, 16 Jan 2005 00:58:15 -0600 (CST) (envelope-from noackjr@alumni.rice.edu) Message-ID: <41EA1087.6090008@alumni.rice.edu> Date: Sun, 16 Jan 2005 00:58:15 -0600 From: Jon Noack User-Agent: Mozilla Thunderbird 1.0 (X11/20050103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: cognet@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org cc: stable@freebsd.org Subject: bktr_core.c commit breaks building kernels on RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 06:58:20 -0000 This commit broke building kernels on RELENG_5 (see tinderbox logs): > cognet 2005-01-16 01:01:15 UTC > > FreeBSD src repository > > Modified files: (Branch: RELENG_5) > sys/dev/bktr bktr_core.c > Log: > MFC rev 1.139: > revision 1.138 > date: 2005/01/09 17:42:03; author: cognet; state: Exp; lines: +64 -64 > Use uint32_t instead of u_long when appropriate. > That's enough to make my bt848 work on amd64. > > Revision Changes Path > 1.135.2.1 +65 -65 src/sys/dev/bktr/bktr_core.c I believe this change was unintended: > @@ -1258,7 +1258,7 @@ vbi_read(bktr_ptr_t bktr, struct uio *ui > LOCK_VBI(bktr); > > while(bktr->vbisize == 0) { > - if (ioflag & IO_NDELAY) { > + if (ioflag & FNDELAY) { > status = EWOULDBLOCK; > goto out; > } Jon From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 07:33:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C244316A4CE for ; Sun, 16 Jan 2005 07:33:52 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAD5443D5E for ; Sun, 16 Jan 2005 07:33:50 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0G7Xme06568 for ; Sun, 16 Jan 2005 18:33:48 +1100 (EST) Date: Sun, 16 Jan 2005 18:33:48 +1100 (EST) From: Dave Horsfall To: FreeBSD STABLE list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: bktr_core.c:1261: error: `FNDELAY' undeclared X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 07:33:52 -0000 FreeBSD 5.3-STABLE, last updated 1st Jan 2005. Just did a CVSUP of -STABLE. make buildworld - OK. make buildkernel KERNCONF=STINKY Goes swimmingly, then... cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/STINKY/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/STINKY -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c: In function `vbi_read': /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: `FNDELAY' undeclared (first use in this function) Nothing in /usr/src/UPDATING; nothing that Google can find. Did I miss something? I don't even know why it's being compiled, since it's not in my config file, so I've commented it out until if/when I get a chance to look at it... -- Dave From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 07:37:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4904C16A4CE for ; Sun, 16 Jan 2005 07:37:07 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81CE743D1F for ; Sun, 16 Jan 2005 07:37:05 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0G7b3706581 for ; Sun, 16 Jan 2005 18:37:03 +1100 (EST) Date: Sun, 16 Jan 2005 18:37:03 +1100 (EST) From: Dave Horsfall To: FreeBSD STABLE list In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: bktr_core.c:1261: error: `FNDELAY' undeclared X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 07:37:07 -0000 Skip it - someone else spotted the problem just before I did (seems to have been a broken commit). -- Dave From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 07:39:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F8C216A4CE; Sun, 16 Jan 2005 07:39:58 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E27F43D54; Sun, 16 Jan 2005 07:39:56 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0G7doT06590; Sun, 16 Jan 2005 18:39:50 +1100 (EST) Date: Sun, 16 Jan 2005 18:39:49 +1100 (EST) From: Dave Horsfall To: Jon Noack In-Reply-To: <41EA1087.6090008@alumni.rice.edu> Message-ID: References: <41EA1087.6090008@alumni.rice.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org cc: cognet@freebsd.org Subject: Re: bktr_core.c commit breaks building kernels on RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 07:39:58 -0000 On Sun, 16 Jan 2005, Jon Noack wrote: > This commit broke building kernels on RELENG_5 (see tinderbox logs): > > cognet 2005-01-16 01:01:15 UTC Thanks; I was wondering what broke... > I believe this change was unintended: > > @@ -1258,7 +1258,7 @@ vbi_read(bktr_ptr_t bktr, struct uio *ui > > LOCK_VBI(bktr); > > while(bktr->vbisize == 0) { > > - if (ioflag & IO_NDELAY) { > > + if (ioflag & FNDELAY) { > > status = EWOULDBLOCK; > > goto out; > > } Yep. -- Dave From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 10:20:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 097B616A4CE for ; Sun, 16 Jan 2005 10:20:52 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 30DBB43D53 for ; Sun, 16 Jan 2005 10:20:51 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Jan 2005 10:20:49 +0000 (GMT) Date: Sun, 16 Jan 2005 10:20:49 +0000 From: David Malone To: Robert William Vesterman Message-ID: <20050116102049.GA59394@walton.maths.tcd.ie> References: <41E9B02B.5070602@fer.hr> <41E9E37B.7020002@vesterman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E9E37B.7020002@vesterman.com> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie cc: freebsd-stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 10:20:52 -0000 On Sat, Jan 15, 2005 at 10:46:03PM -0500, Robert William Vesterman wrote: > I have a similar problem, but only after I use X. I can su perfectly > fine before using X, and I can su perfectly fine while using X (and a > terminal window), but after exiting X, if I want to su, I have to reboot. You might want to try the following C program to check that getlogin is returning the right name at each stage. David. 10:18:gonzo 17% cat printlogin.c #include #include int main(void) { puts(getlogin()); } 10:18:gonzo 18% gcc -o printlogin printlogin.c 10:18:gonzo 19% ./printlogin dwmalone From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 10:34:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C424216A4CE for ; Sun, 16 Jan 2005 10:34:03 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id A804743D1F for ; Sun, 16 Jan 2005 10:34:02 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 6C4857BA5 for ; Sun, 16 Jan 2005 10:34:00 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Sun, 16 Jan 2005 10:33:46 +0000 User-Agent: KMail/1.7.2 References: <200501160051.33198.imobachgs@banot.net> <41E9E3C4.9050202@vesterman.com> In-Reply-To: <41E9E3C4.9050202@vesterman.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501161033.47012.imobachgs@banot.net> Subject: Re: USB mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 10:34:03 -0000 On Sunday 16 January 2005 03:47, Robert William Vesterman wrote: > I found that my USB mouse works if and only if I boot without APCI suppor= t. Ok, it didn't work to me. I added hint.acpi.0.disabled=3D"1" (and also tried adding hint.apm.0.disabled=3D"0" too) 'dmesg | grep acpi' returns no results, same as 'devinfo | grep acpi'. So I= =20 suppose acpi is disabled at boot time. I also noticed that when moused star= t=20 while booting the machine, it throws me this error: 'unable to=20 open /dev/ums0: Device busy'. Any idea? > >However, I can't figure out how to configure moused with my mouse: I have > > this settings in /etc/rc.conf: > > > >usbd_enable=3D"YES" > >usbd_flags=3D"" > >moused_enable=3D"YES" > >moused_type=3D"auto" > >moused_flags=3D"" > >moused_port=3D"/dev/ums0" > > =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 10:45:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B437B16A4CE; Sun, 16 Jan 2005 10:45:56 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E1D643D41; Sun, 16 Jan 2005 10:45:55 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0GAjfoC025439 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 16 Jan 2005 21:45:42 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Sun, 16 Jan 2005 21:45:17 +1100 To: "Vinod Kashyap" X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with 9.1.5.2 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 10:45:56 -0000 Hello On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: > > Could you give the attached patch a try? Just a hunch... > I did... same behavior. it just hangs right after displaying the twa0 line. Actually, hangs is incorrect. As I had to drive to the office to reload a previous kernel (never, ever rely on nextboot my friends!) When I got there I saw that it went a little bit further, so it seems that it doesn't just hang... it is just very very slow Jean-Yves --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 12:12:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE21016A4CE for ; Sun, 16 Jan 2005 12:12:25 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDA243D58 for ; Sun, 16 Jan 2005 12:12:24 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0GCOn5B022235; Sun, 16 Jan 2005 13:24:49 +0100 (MET) Message-ID: <41EA5A1F.7050407@fer.hr> Date: Sun, 16 Jan 2005 13:12:15 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Dymond References: <41E9B02B.5070602@fer.hr> <20050116000935.GA95376@xor.obsecurity.org> <41E9B226.40801@fer.hr> <20050116003334.GA394@xor.obsecurity.org> <41E9C0D2.3000101@fer.hr> <20050116113424.GA35989@ruby.london.kmem.org> In-Reply-To: <20050116113424.GA35989@ruby.london.kmem.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 12:12:25 -0000 Thomas Dymond wrote: > > Could this be anything to do with : security.bsd.suser_enabled > > what's yours set to ? security.bsd.suser_enabled: 1 But, I noticed I've got security.mac.* enabled somehow (it's not my kernel...) - could MAC be interfering? From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 14:22:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D8F16A4CE for ; Sun, 16 Jan 2005 14:22:09 +0000 (GMT) Received: from congo.princess.dyns.cx (dynamic-62-56-53-84.park-s46b.dslaccess.co.uk [62.56.53.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D7E43D3F for ; Sun, 16 Jan 2005 14:22:08 +0000 (GMT) (envelope-from steve@acidy.com) Received: by congo.princess.dyns.cx (Postfix, from userid 1001) id 0ABBABC44; Sun, 16 Jan 2005 14:22:06 +0000 (GMT) From: Steve Hodgson To: freebsd-stable@freebsd.org Date: Sun, 16 Jan 2005 14:22:05 +0000 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501161422.05929.steve@acidy.com> Subject: make buildworld for RELENG_5 failing on RELENG_5_3 in /usr/src/usr.sbin/syslogd, _PATH_LOG_PRIV not defined X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 14:22:09 -0000 I'm getting the following error on a RELENG_5_3 box when trying to compile the RELENG_5 sources. I've been cvsupping now for about a week and continuing to get the same error when we get to syslogd. /usr/src/usr.sbin/syslogd/syslogd.c:141: error: `_PATH_LOG_PRIV' undeclared here (not in a function) /usr/src/usr.sbin/syslogd/syslogd.c:141: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:141: error: (near initialization for `funix_secure.name') /usr/src/usr.sbin/syslogd/syslogd.c:142: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:142: error: (near initialization for `funix_secure.next') If I apply the following patch then buildworld continues to completion. Note the same error appears in libc and the patch fixes that as well. Judging by the build logs and lack of others complaining I'm the only one with this problem, so clearly this isn't the correct solution, but it works for me. --- /usr/src/usr.sbin/syslogd/syslogd.c.old Sun Jan 16 12:16:25 2005 +++ /usr/src/usr.sbin/syslogd/syslogd.c Sun Jan 16 12:17:53 2005 @@ -74,6 +74,7 @@ #define DEFSPRI (LOG_KERN|LOG_CRIT) #define TIMERINTVL 30 /* interval for checking flush, mark */ #define TTYMSGTIME 1 /* timeout passed to ttymsg */ +#define _PATH_LOG_PRIV "/var/run/logpriv" #include #include --- /usr/src/lib/libc/gen/syslog.c.old Sun Jan 16 14:12:49 2005 +++ /usr/src/lib/libc/gen/syslog.c Sun Jan 16 13:03:41 2005 @@ -60,6 +60,8 @@ #include "libc_private.h" +#define _PATH_LOG_PRIV "/var/run/logpriv" + static int LogFile = -1; /* fd for log */ static int status; /* connection status */ static int opened; /* have done openlog() */ Any ideas on what could be wrong with my system? FYI In general I use ccache but i've disabled it for this run, by editing out the commands in /etc/make.conf. Steve From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 14:41:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DF2216A4CE for ; Sun, 16 Jan 2005 14:41:28 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 82F0943D5A for ; Sun, 16 Jan 2005 14:41:27 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 16 Jan 2005 14:41:25 -0000 Received: from p3EE2656C.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.101.108) by mail.gmx.net (mp001) with SMTP; 16 Jan 2005 15:41:25 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id j0GEfL0Z088398 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 16 Jan 2005 15:41:22 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Sun, 16 Jan 2005 15:41:15 +0100 User-Agent: KMail/1.7.2 References: <41E9B02B.5070602@fer.hr> In-Reply-To: <41E9B02B.5070602@fer.hr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7229141.pcNEWiqZlt"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501161541.19290.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: Ivan Voras Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 14:41:28 -0000 --nextPart7229141.pcNEWiqZlt Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 16. January 2005 01:07, Ivan Voras wrote: > What could be the reasons for "su root" to not work? > > I have a user that's in wheel group. Logging in as root works on the > console, but su-ing from the user just writes 'Sorry', like the > password's wrong. There are no clues in log files. Make sure /usr/sbin/su is suid root (and /usr isn't mounted nosuid). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart7229141.pcNEWiqZlt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB6n0PXhc68WspdLARAvoTAJ95lTq7GZhuAlxSxZA+J6sD7dy1NACeKNiL 4ov5z1PH6xZtKTBD6g2PTYU= =u8EF -----END PGP SIGNATURE----- --nextPart7229141.pcNEWiqZlt-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 17:14:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5780D16A4CE; Sun, 16 Jan 2005 17:14:01 +0000 (GMT) Received: from damo.axelero.hu (fe01.axelero.hu [195.228.240.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F6D843D1D; Sun, 16 Jan 2005 17:14:00 +0000 (GMT) (envelope-from kutizs@axelero.hu) Received: from damo (localhost-02 [127.0.2.1]) by damo.axelero.hu (8.12.11/8.12.11) with SMTP id j0GHDxQV023486; Sun, 16 Jan 2005 18:13:59 +0100 (CET) Received: from fe01.axelero.hu [127.0.2.1] via SMTP gateway by damo [195.228.240.89]; id A05BBA26CD1 at Sun, 16 Jan 2005 18:13:59 +0100 Received: from tinca.kuti.hu (ktv32-37-73.catv-pool.axelero.hu [62.201.73.37]) by fe01.axelero.hu (8.12.11/8.12.11) with SMTP id j0GHDr3M023454; Sun, 16 Jan 2005 18:13:58 +0100 (CET) Date: Sun, 16 Jan 2005 18:14:33 +0100 From: Zsolt =?ISO-8859-2?Q?K=FAti?= To: Jeffrey Williams Message-Id: <20050116181433.29ae0a21.kutizs@axelero.hu> In-Reply-To: <41E989E0.3000903@sailorfej.net> References: <20050114102346.GA53545@cirb503493.alcatel.com.au> <41E960BA.3010502@sailorfej.net> <20050115203049.GE53545@cirb503493.alcatel.com.au> <41E989E0.3000903@sailorfej.net> X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: PeterJeremy@optushome.com.au cc: freebsd-stable@freebsd.org cc: freebsd-openoffice@freebsd.org Subject: Re: Unkillable OpenOffice.org process in 5.3p2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 17:14:01 -0000 On Sat, 15 Jan 2005 13:23:44 -0800 Jeffrey Williams wrote: > When you rebooted, was the computer actually able to halt on its own? > Every time mine has locked up, I have had to do a hard power down, the > OS is unable to kill the process even when halting. I have noticed A can confirm this on my system (5.3 RELEASE, AMD 1400+, OO 1.1.3/1.1.4, java 1.4.2-p6). My OO frequently freezes when I start a new document or try load one (or spreadsheet or whatever). Very annoying. > that the OO app freezes typically after having Mozilla to use java > and/or adobe plugins, I am not sure which is the trigger yet. I am No Mozilla & java-adobe plugin here. > wondering if it is a problem with the interaction between the OO and > java, or OO the pdf libraries, or a some shared library that > facilitates the interaction between these components. I am afraid I I extensively use Java applications (jEdit, DBVisualizer, jCVS, Java Web Start and apps launched by JWS). I am going to try to experiment with all these in mind on Monday (at work). Here, at home I can't reproduce this , however. Its also an AMD machine, much faster (2600+), 5.3 B7 (latest RELEASE doesn't work unfortunately). Bye Zsolt ================= Zsolt Kuti From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 17:23:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6234416A4CE for ; Sun, 16 Jan 2005 17:23:18 +0000 (GMT) Received: from ruby.london.kmem.org (ssl1.kmem.org [84.40.1.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id B977D43D39 for ; Sun, 16 Jan 2005 17:23:17 +0000 (GMT) (envelope-from tom@ruby.london.kmem.org) Received: from ruby.london.kmem.org (localhost [127.0.0.1]) by ruby.london.kmem.org (8.13.1/8.13.1) with ESMTP id j0GBYQNM036167; Sun, 16 Jan 2005 11:34:26 GMT (envelope-from tom@ruby.london.kmem.org) Received: (from tom@localhost) by ruby.london.kmem.org (8.13.1/8.13.1/Submit) id j0GBYOfq036166; Sun, 16 Jan 2005 11:34:24 GMT (envelope-from tom) Date: Sun, 16 Jan 2005 11:34:24 +0000 From: Thomas Dymond To: Ivan Voras Message-ID: <20050116113424.GA35989@ruby.london.kmem.org> Mail-Followup-To: Ivan Voras , freebsd-stable@freebsd.org References: <41E9B02B.5070602@fer.hr> <20050116000935.GA95376@xor.obsecurity.org> <41E9B226.40801@fer.hr> <20050116003334.GA394@xor.obsecurity.org> <41E9C0D2.3000101@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <41E9C0D2.3000101@fer.hr> X-Operating-System: FreeBSD 5.3-RELEASE X-PGP-Key: http://www.kmem.org/~tom/pgp/oubkey.asc X-PGP-Fingerprint: 5668 F423 E53A CDC7 9942 0AFD 5A61 1352 8D42 3A2B Organization: Hmmm... I dunno User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 17:23:18 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable +++ Ivan Voras [Sunday 16 January 2005 02:18]: > Kris Kennaway wrote: > >On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote: > > > >>Kris Kennaway wrote: >=20 > >>>>/etc/pam.d/su is identical to another machine where everything works = ok. >=20 > > > >OK. /etc/pam.d/su on 5.3 includes /etc/pam.d/system, so also make > >sure they're in sync. >=20 > /etc/pam.d/system is the same as on the working system. > _______________________________________________ > 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" >=20 Could this be anything to do with : security.bsd.suser_enabled what's yours set to ? Cheers --=20 Thomas Dymond "a mouse is a device used to point at the xterm you want to type in" PGP ID : 0x8D423A2B PGP Key : http://www.kmem.org/~tom/pgp/pubkey.asc --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB6lFAWmETUo1COisRAteWAJ9x5xaf25muCFtbeA04Rib/K2NtNACfYXnd kQetqIMT2T5z/1v8tJ8BRuA= =lDfG -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 17:33:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D8116A4CE; Sun, 16 Jan 2005 17:33:20 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD8D543D60; Sun, 16 Jan 2005 17:33:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3227952438; Sun, 16 Jan 2005 09:33:18 -0800 (PST) Date: Sun, 16 Jan 2005 09:33:18 -0800 From: Kris Kennaway To: sparc64@FreeBSD.org, stable@FreeBSD.org Message-ID: <20050116173318.GB70453@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jho1yZJdad60DJr+" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic in ffs_write() on RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 17:33:20 -0000 --jho1yZJdad60DJr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline One of my U10s running RELENG_5 panicked with the following: panic: trap: data access error cpuid = 0 KDB: enter: panic [thread 100047] Stopped at kdb_enter+0x38: ta %xcc, 1 db> tr panic() at panic+0x214 trap() at trap+0x13c -- data access error %o7=0xc014fcb8 -- copyin() at copyin+0x64 ffs_write() at ffs_write+0x338 vn_rdwr() at vn_rdwr+0xb8 vn_rdwr_inchunks() at vn_rdwr_inchunks+0x98 elf64_coredump() at elf64_coredump+0x128 sigexit() at sigexit+0x884 postsig() at postsig+0x3a4 ast() at ast+0x440 -- data access error %o7=0x109600 -- Kris --jho1yZJdad60DJr+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6qVdWry0BWjoQKURAgndAKCpvnzXnvFwzz3eOFhpRa8tHZswNQCgz3d2 wuOvcZNS6O1kqFJMOfBLqxo= =YUAi -----END PGP SIGNATURE----- --jho1yZJdad60DJr+-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 17:38:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6873D16A4CE for ; Sun, 16 Jan 2005 17:38:01 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9668543D60 for ; Sun, 16 Jan 2005 17:38:00 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B877951A3A; Sun, 16 Jan 2005 09:37:58 -0800 (PST) Date: Sun, 16 Jan 2005 09:37:58 -0800 From: Kris Kennaway To: Steve Hodgson Message-ID: <20050116173758.GA70598@xor.obsecurity.org> References: <200501161422.05929.steve@acidy.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <200501161422.05929.steve@acidy.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: make buildworld for RELENG_5 failing on RELENG_5_3 in /usr/src/usr.sbin/syslogd, _PATH_LOG_PRIV not defined X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 17:38:01 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 02:22:05PM +0000, Steve Hodgson wrote: > I'm getting the following error on a RELENG_5_3 box when trying to compil= e the=20 > RELENG_5 sources. I've been cvsupping now for about a week and continuing= to=20 > get the same error when we get to syslogd. >=20 > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: `_PATH_LOG_PRIV' undeclar= ed=20 > here (not in a function) > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: initializer element is no= t=20 > constant > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: (near initialization for= =20 > `funix_secure.name') > /usr/src/usr.sbin/syslogd/syslogd.c:142: error: initializer element is no= t=20 > constant > /usr/src/usr.sbin/syslogd/syslogd.c:142: error: (near initialization for= =20 > `funix_secure.next') >=20 > If I apply the following patch then buildworld continues to completion. N= ote=20 > the same error appears in libc and the patch fixes that as well. Judging = by=20 > the build logs and lack of others complaining I'm the only one with this= =20 > problem, so clearly this isn't the correct solution, but it works for me. >=20 > --- /usr/src/usr.sbin/syslogd/syslogd.c.old Sun Jan 16 12:16:25 2005 > +++ /usr/src/usr.sbin/syslogd/syslogd.c Sun Jan 16 12:17:53 2005 > @@ -74,6 +74,7 @@ > #define DEFSPRI (LOG_KERN|LOG_CRIT) > #define TIMERINTVL 30 /* interval for checking flush, m= ark=20 > */ > #define TTYMSGTIME 1 /* timeout passed to ttymsg */ > +#define _PATH_LOG_PRIV "/var/run/logpriv" >=20 > #include > #include > --- /usr/src/lib/libc/gen/syslog.c.old Sun Jan 16 14:12:49 2005 > +++ /usr/src/lib/libc/gen/syslog.c Sun Jan 16 13:03:41 2005 > @@ -60,6 +60,8 @@ >=20 > #include "libc_private.h" >=20 > +#define _PATH_LOG_PRIV "/var/run/logpriv" > + > static int LogFile =3D -1; /* fd for log */ > static int status; /* connection status */ > static int opened; /* have done openlog() */ >=20 > Any ideas on what could be wrong with my system? FYI In general I use cca= che=20 > but i've disabled it for this run, by editing out the commands=20 > in /etc/make.conf. Try make cleandir make cleandir make buildworld Kris --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6qZ2Wry0BWjoQKURAuAPAKCSaui8R84rwzyK+BRBsXA2a1omYwCg9u6a 3HVBbbc1s/1nN8rAKBIRpHI= =uYS8 -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 18:06:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D289316A4CE for ; Sun, 16 Jan 2005 18:06:54 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31D4B43D48 for ; Sun, 16 Jan 2005 18:06:54 +0000 (GMT) (envelope-from jwm@sentinelchicken.net) Received: from sentinelchicken.net ([68.226.91.117]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with SMTP <20050116180653.OFKX1656.lakermmtao12.cox.net@sentinelchicken.net> for ; Sun, 16 Jan 2005 13:06:53 -0500 Received: (qmail 67957 invoked by uid 1000); 16 Jan 2005 18:10:22 -0000 Date: Sun, 16 Jan 2005 13:10:22 -0500 From: Jason Morgan To: freebsd-stable@freebsd.org Message-ID: <20050116181022.GC60212@sentinelchicken.net> References: <200501160051.33198.imobachgs@banot.net> <41E9E3C4.9050202@vesterman.com> <200501161033.47012.imobachgs@banot.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501161033.47012.imobachgs@banot.net> User-Agent: Mutt/1.4.1i Subject: Re: USB mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 18:06:55 -0000 On Sun, Jan 16, 2005 at 10:33:46AM +0000, Imobach Gonz?lez Sosa wrote: > On Sunday 16 January 2005 03:47, Robert William Vesterman wrote: > > I found that my USB mouse works if and only if I boot without APCI support. > > Ok, it didn't work to me. I added > > hint.acpi.0.disabled="1" > (and also tried adding hint.apm.0.disabled="0" too) > > 'dmesg | grep acpi' returns no results, same as 'devinfo | grep acpi'. So I > suppose acpi is disabled at boot time. I also noticed that when moused start > while booting the machine, it throws me this error: 'unable to > open /dev/ums0: Device busy'. > > Any idea? > > > >However, I can't figure out how to configure moused with my mouse: I have > > > this settings in /etc/rc.conf: > > > > > >usbd_enable="YES" > > >usbd_flags="" > > >moused_enable="YES" > > >moused_type="auto" > > >moused_flags="" > > >moused_port="/dev/ums0" > > > What brand of mouse you using? I have 2 IBM optical mice that need disconnected and reconnected about 1/2 the time before they will work. This happens to me in Linux, FreeBSD, and Windows so seems to be a mouse issue. Happens to my brother as well - he has the same mouse. Even when the mouse works at bootup, I get a /dev/ums0: Device busy error. Only thing I can see that is different in my setup compared to yours is that I have: usbd_flags="-vv" in rc.conf. I can't for the life of me remember why (scrolling maybe?). Cheers. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 19:00:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D4B016A4CE for ; Sun, 16 Jan 2005 19:00:56 +0000 (GMT) Received: from quark.cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F1D43D31 for ; Sun, 16 Jan 2005 19:00:55 +0000 (GMT) (envelope-from skylar@cs.earlham.edu) Received: from quark.cs.earlham.edu (localhost.cs.earlham.edu [127.0.0.1]) by quark.cs.earlham.edu (8.13.1/8.12.9) with ESMTP id j0GJ0tpu014120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 16 Jan 2005 14:00:55 -0500 (EST) (envelope-from skylar@cs.earlham.edu) Received: (from skylar@localhost) by quark.cs.earlham.edu (8.13.1/8.12.9/Submit) id j0GJ0swV014117 for stable@freebsd.org; Sun, 16 Jan 2005 14:00:54 -0500 (EST) (envelope-from skylar@cs.earlham.edu) X-Authentication-Warning: quark.cs.earlham.edu: skylar set sender to skylar@quark.cs.earlham.edu using -f Date: Sun, 16 Jan 2005 14:00:54 -0500 From: Skylar Thompson To: stable@freebsd.org Message-ID: <20050116190054.GA14094@quark.cs.earlham.edu> Mail-Followup-To: stable@freebsd.org References: <41E9B02B.5070602@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <41E9B02B.5070602@fer.hr> User-Agent: Mutt/1.4.2.1i X-Sender: "Skylar Thompson" X-Accept-Primary-Language: en X-Accept-Secondary-Language: es SMTP-Mailing-Host: quark.cs.earlham.edu X-Operating-System: FreeBSD 4.11-PRERELEASE X-Uptime: 2:00PM up 31 days, 10:08, 22 users, load averages: 0.44, 0.20, 0.19 X-Editor: VIM - Vi IMproved 6.3 (2004 June 7, compiled Aug 26 2004 10:37:04) Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Skylar Thompson List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 19:00:56 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote: > What could be the reasons for "su root" to not work? >=20 > I have a user that's in wheel group. Logging in as root works on the=20 > console, but su-ing from the user just writes 'Sorry', like the=20 > password's wrong. There are no clues in log files. >=20 > /etc/pam.d/su is identical to another machine where everything works ok. Are you using NIS? I've had issues where the machine tries to look up the root password using NIS because of improperly placed + and - commands in /etc/passwd. --=20 -- Skylar Thompson (skylar@cs.earlham.edu) -- http://www.cs.earlham.edu/~skylar/ --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFB6rnmsc4yyULgN4YRAv7aAKCkRwV4l5WN60IRaueIshbSwSHi9QCgszrw sMNGBjXGbixf5zHmsTJcKRk= =PjEe -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 22:39:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 727D316A4CE for ; Sun, 16 Jan 2005 22:39:55 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C71043D45 for ; Sun, 16 Jan 2005 22:39:52 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 199F23BEDF for ; Sun, 16 Jan 2005 22:39:43 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Sun, 16 Jan 2005 22:39:14 +0000 User-Agent: KMail/1.7.2 References: <200501160051.33198.imobachgs@banot.net> <200501161033.47012.imobachgs@banot.net> <20050116181022.GC60212@sentinelchicken.net> In-Reply-To: <20050116181022.GC60212@sentinelchicken.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200501162239.15299.imobachgs@banot.net> Subject: Re: USB mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 22:39:55 -0000 On Sunday 16 January 2005 18:10, Jason Morgan wrote: > What brand of mouse you using? I have 2 IBM optical mice that need > disconnected and reconnected about 1/2 the time before they will work.=20 > This happens to me in Linux, FreeBSD, and Windows so seems to be a mouse > issue. Happens to my brother as well - he has the same mouse. Even when > the mouse works at bootup, I get a /dev/ums0: Device busy error. Only thi= ng > I can see that is different in my setup compared to yours is that I have: I have a "Logitech Coordless Desktop Comfort"; it's a receiver with=20 keyboard+optical mouse. > usbd_flags=3D"-vv" This make no sense for me. > in rc.conf. I can't for the life of me remember why (scrolling maybe?). Ok, so now the good news: I've installed a 'macally mice' (a simple usb mou= se)=20 and it seems to work just fine. Anyway, I still wanna use my Logitech mice,= =20 so I suppose I'll continue trying with it. Thank you all for your responses. Anybody on this list have a Logitech mice as mine? =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Sun Jan 16 23:39:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44A8116A4CE for ; Sun, 16 Jan 2005 23:39:43 +0000 (GMT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9264343D1D for ; Sun, 16 Jan 2005 23:39:42 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 55122 invoked by uid 98); 16 Jan 2005 18:39:41 -0500 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 1003 with qmail-scanner-1.20 (spamassassin: 3.0.1. Clear:RC:1(128.227.47.18):. Processed in 0.028419 secs); 16 Jan 2005 23:39:41 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.028419 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with (RC4-MD5 encrypted) SMTP; 16 Jan 2005 18:39:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sun, 16 Jan 2005 18:39:41 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED80504A3E1@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Machine(s) not able to reboot Thread-Index: AcT8JKZlIZMfvbb0S9a/tta+g1+3vA== From: "Will Saxon" To: Subject: Machine(s) not able to reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Jan 2005 23:39:43 -0000 Hello, I have two HP Proliant DL360G3 servers which I recently upgraded from = 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines = to shut down or reboot on their own. I always have to physically power = them off and then back on. They are SMP machines and I am using ACPI. = There are no other apparent problems although one machine did panic = today and as a result I had to drive in and power cycle it.=20 I saw some posts about this in mail archives, but they were very old. = Has anyone else experienced this problem? What should I look for to fix = this? -Will From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 01:22:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C300116A4CE; Mon, 17 Jan 2005 01:22:24 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7473E43D1D; Mon, 17 Jan 2005 01:22:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9942851506; Sun, 16 Jan 2005 17:22:23 -0800 (PST) Date: Sun, 16 Jan 2005 17:22:23 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050117012223.GA96318@xor.obsecurity.org> References: <20050116173318.GB70453@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <20050116173318.GB70453@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: stable@FreeBSD.org cc: sparc64@FreeBSD.org Subject: Re: panic in ffs_write() on RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 01:22:24 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 09:33:18AM -0800, Kris Kennaway wrote: > One of my U10s running RELENG_5 panicked with the following: >=20 > panic: trap: data access error > cpuid =3D 0 > KDB: enter: panic > [thread 100047] > Stopped at kdb_enter+0x38: ta %xcc, 1 > db> tr > panic() at panic+0x214 > trap() at trap+0x13c > -- data access error %o7=3D0xc014fcb8 -- > copyin() at copyin+0x64 > ffs_write() at ffs_write+0x338 > vn_rdwr() at vn_rdwr+0xb8 > vn_rdwr_inchunks() at vn_rdwr_inchunks+0x98 > elf64_coredump() at elf64_coredump+0x128 > sigexit() at sigexit+0x884 > postsig() at postsig+0x3a4 > ast() at ast+0x440 > -- data access error %o7=3D0x109600 -- I think this was bad RAM; I got a RED exception when I tried to dump. Kris --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6xNPWry0BWjoQKURAszzAJ9SKngyMKGn+zfTFtvuz5ziFUmB2QCghw7G 18wQmerlo4sn1AENNABlUDQ= =G7b1 -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 02:05:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DD2116A4CE for ; Mon, 17 Jan 2005 02:05:35 +0000 (GMT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 107C543D46 for ; Mon, 17 Jan 2005 02:05:35 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 61216 invoked by uid 98); 16 Jan 2005 21:05:34 -0500 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 1003 with qmail-scanner-1.20 (spamassassin: 3.0.1. Clear:RC:1(128.227.47.18):. Processed in 0.013283 secs); 17 Jan 2005 02:05:34 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.013283 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with (RC4-MD5 encrypted) SMTP; 16 Jan 2005 21:05:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sun, 16 Jan 2005 21:05:33 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED80504A3E4@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Machine(s) not able to reboot Thread-Index: AcT8JxUyewW2+zwBRte6+T8F+Hap3AAEZ6mw From: "Will Saxon" To: "Peter Jeremy" cc: stable@freebsd.org Subject: RE: Machine(s) not able to reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 02:05:35 -0000 > -----Original Message----- > From: Peter Jeremy [mailto:peter.jeremy@alcatel.com.au] > Sent: Sunday, January 16, 2005 6:56 PM > To: Will Saxon > Cc: stable@freebsd.org > Subject: Re: Machine(s) not able to reboot >=20 >=20 >=20 > [Please wrap your mail before 80 columns] Sorry, have to do it manually and I forgot. >=20 > On 2005-Jan-16 18:39:41 -0500, Will Saxon=20 > wrote: > >I have two HP Proliant DL360G3 servers which I recently upgraded from > >5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the > >machines to shut down or reboot on their own. I always have to > >physically power them off and then back on. >=20 > I have this problem with some DL380's. I have been unable to work out > what the root cause is but I've found that the problem is triggered by > kldload(8). If I don't use any modules other than acpi.ko (which is > loaded by /boot/loader) then I don't have the problem. >=20 This works for me also. I had not added device vlan to my kernel config and was also loading the sysvipc stuff, usb and linux/linprocfs.=20 Thanks! -Will From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 02:07:42 2005 Return-Path: Delivered-To: freebsd-stable@mx1.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CD1416A4CE for ; Mon, 17 Jan 2005 02:07:42 +0000 (GMT) Received: from bobbi.cse.buffalo.edu (bobbi.cse.Buffalo.EDU [128.205.32.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FB2843D3F for ; Mon, 17 Jan 2005 02:07:41 +0000 (GMT) (envelope-from kensmith@FreeBSD.org) Received: from bobbi.cse.buffalo.edu (localhost.cs.Buffalo.EDU [127.0.0.1]) by bobbi.cse.buffalo.edu (8.13.1/8.12.4) with ESMTP id j0H27e4f002758 for ; Sun, 16 Jan 2005 21:07:40 -0500 (EST) Received: (from kensmith@localhost) by bobbi.cse.buffalo.edu (8.13.1/8.13.1/Submit) id j0H27eOX002757 for freebsd-stable@freebsd.org; Sun, 16 Jan 2005 21:07:40 -0500 (EST) (envelope-from kensmith) Date: Sun, 16 Jan 2005 21:07:39 -0500 From: Ken Smith To: freebsd-stable@FreeBSD.org Message-ID: <20050117020739.GA2736@bobbi.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: FreeBSD 4.11-RC3 available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 02:07:42 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Announcement ------------ The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 4.11-RC3. This will be the last Release Candidate for the FreeBSD 4.11 release unless a "show-stopper" problem is found while testing RC3. A schedule for the Release Cycle is available at: http://www.freebsd.org/releases/4.11R/schedule.html We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images and support for doing FTP based installs is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_4_11. Problem reports can be submitted using the send-pr(1) command. It has been decided to provide two disc1 ISO images, one with the KDE windowing system packages on it and the other with the GNOME windowing system packages. They are named disc1-kde and disc1-gnome respectively. Other than which major windowing system is on them they are identical. Most users can choose one of the disc1 ISOs to download and install from. At this time disc1-gnome for Alpha is not available. It may be made available later this week. At the moment there are no known severe issues. Changes since RC2: - fix to some string handling in file(1) - additional device support to mpt(4) - tcp fix to make RST attacks harder plus knob to turn off new behavior - fixes to sk(4) and em(4) - fixes to USB - fixes to kernel linux emulation - addition of ips(4) driver - lots of doc fixes/updates Availability ------------ The RC3 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (4.11-RC3-alpha-disc1-kde.iso) = b0b829a27d32e035e10d76fa5c517376 MD5 (4.11-RC3-alpha-disc2.iso) = 1a842a0b0f039b4059ccc84da3dc854e MD5 (4.11-RC3-alpha-miniinst.iso) = 4d8e8ea552cbe1a76de29ae5f56211f2 MD5 (4.11-RC3-i386-disc1-gnome.iso) = 35a1edeec3efdabccd2ba2a90bfe4cd0 MD5 (4.11-RC3-i386-disc1-kde.iso) = dd3eb1a0a9474557fb607bd7467fcee2 MD5 (4.11-RC3-i386-disc2.iso) = c081a7a6f0762a1e2bf5ca34a3a8ac85 MD5 (4.11-RC3-i386-miniinst.iso) = 8bfa7a081641cfe0befe1ea9679459ed --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB6x3p/G14VSmup/YRAszYAJ4pQu+K17Dkb0CMtOROJnyJ0J/gEACfczd0 OZQ+IWvy0S9Zvj+oWkKkwFg= =/OJ7 -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 03:04:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E50A816A4CE for ; Mon, 17 Jan 2005 03:04:28 +0000 (GMT) Received: from flora.securenet.com.au (ns1.securenet.com.au [202.125.0.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75D6C43D1D for ; Mon, 17 Jan 2005 03:04:27 +0000 (GMT) (envelope-from carl@xena.IPAustralia.gov.au) Received: from leal.securenet.com.au (leal.isecure.com.au [202.125.0.94]) j0H34MWf015308; Mon, 17 Jan 2005 14:04:22 +1100 Received: (from root@localhost) by leal.securenet.com.au (8.12.6/8.12.6) id j0H34LKO004276; Mon, 17 Jan 2005 14:04:21 +1100 (EST) Received: from nodnsquery(10.11.3.10) by leal.securenet.com.au via csmap (V6.0) id srcAAApNaqwi; Mon, 17 Jan 05 14:04:21 +1100 Received: from vmail.aipo.gov.au (localhost [127.0.0.1]) j0H34LRh004137; Mon, 17 Jan 2005 14:04:21 +1100 Received: from xena.aipo.gov.au (xena.aipo.gov.au [10.0.100.52]) by vmail.aipo.gov.au (8.12.9p2/8.12.9) with ESMTP id j0H34KFb051810; Mon, 17 Jan 2005 14:04:20 +1100 (EST) (envelope-from carl@xena.IPAustralia.gov.au) Received: from [10.0.100.18] (newton.aipo.gov.au [10.0.100.18]) by xena.aipo.gov.au (8.12.9p2/8.12.9) with ESMTP id j0H34KGV017428; Mon, 17 Jan 2005 14:04:20 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Message-ID: <41EB2B34.6050803@xena.ipaustralia.gov.au> Date: Mon, 17 Jan 2005 14:04:20 +1100 From: Carl Makin User-Agent: Mozilla Thunderbird 1.0 (X11/20050111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <20050114102346.GA53545@cirb503493.alcatel.com.au> In-Reply-To: <20050114102346.GA53545@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 10.0.100.191 cc: stable@freebsd.org Subject: Re: Unkillable OpenOffice.org process in 5.3p2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 03:04:29 -0000 Hi Peter, Peter Jeremy wrote: >I have an OOo process that refuses to die. ps says it is stopped and waiting > > I had the same problem here as well however I upgraded to 5.3-STABLE as of Jan 6 and have had no problems since. I also had "PREEMPTION" enabled in the kernel, which I have removed. Carl. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 03:29:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51BD716A4CE for ; Mon, 17 Jan 2005 03:29:31 +0000 (GMT) Received: from pttx.ptt.cc (patty.csie.ntu.edu.tw [140.112.90.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id E806B43D58 for ; Mon, 17 Jan 2005 03:29:30 +0000 (GMT) (envelope-from in@pttx.ptt.cc) Received: by pttx.ptt.cc (Postfix, from userid 1001) id 1FC8A3D1BAF; Mon, 17 Jan 2005 11:29:25 +0800 (CST) Date: Mon, 17 Jan 2005 11:29:25 +0800 From: in2 To: freebsd-stable@freebsd.org Message-ID: <20050117032925.GA29922@in2home.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: panic: PAE with 16GB ram X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 03:29:31 -0000 Hi, I use Tyan S2882 with dual Opteron and FreeBSD 4.10-RELEASE with PAE support. it works fine with 8GB and 12GB ram, but panics with 16GB (with the same kernel) : Fatal trap 12: page fault while in kernel mode mp_lock = 00000009; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x69bc8000 fault code = supervisor write, page not present instruction pointer = 0x8:0x6a259d26 stack pointer = 0x10:0x6a3b3f44 frame pointer = 0x10:0x6a3b3f5c 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 = Idle interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000009; cpuid = 0; lapic.id = 00000000 Uptime: 0s The same thing occurs in both 4.10-RELEASE and 4.11-stable. I even loaded the fault-safe setting in BIOS but it was still not working. my dmesg is in http://www.in2home.org/download/dmesg, and kernel config is in http://www.in2home.org/download/kernel . thanks for your help. :) From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 04:39:12 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4279916A4CE for ; Mon, 17 Jan 2005 04:39:12 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0B143D3F for ; Mon, 17 Jan 2005 04:39:11 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so188191rna for ; Sun, 16 Jan 2005 20:39:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Do3KLxMTu08KdwEBI6TKJY6G3Cvyz0r0+Aq7lweGrymctqoVcT+dgLVvjbMLmzxKiqq6dU5VX3vyNalZs3fHjCQEPL2uL7aokNaBSdcfm3yRNMJWOH+wWtiZdYHQ44+0pg7cpJ+PcV2pKsC+vSssZsBdSaWUYsZVDN3Fi042d4Y= Received: by 10.38.13.52 with SMTP id 52mr32959rnm; Sun, 16 Jan 2005 20:39:10 -0800 (PST) Received: by 10.38.90.77 with HTTP; Sun, 16 Jan 2005 20:39:06 -0800 (PST) Message-ID: <6863f0c9050116203956de93dd@mail.gmail.com> Date: Sun, 16 Jan 2005 22:39:06 -0600 From: jmc To: Will Saxon In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED80504A3E1@bragi.housing.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <0E972CEE334BFE4291CD07E056C76ED80504A3E1@bragi.housing.ufl.edu> cc: stable@freebsd.org Subject: Re: Machine(s) not able to reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmc List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 04:39:12 -0000 On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon wrote: > Hello, > > I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R > to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down > or reboot on their own. I always have to physically power them off and then back > on. They are SMP machines and I am using ACPI. There are no other apparent > problems although one machine did panic today and as a result I had to drive in > and power cycle it. I haven't heard of this problem before, and I was wondering if today's 5.3-R errata notice (more than one IPI per APIC causes deadlock) might have something to do with it. Are these machines running SMP? - John From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 05:11:36 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC47C16A4CE for ; Mon, 17 Jan 2005 05:11:36 +0000 (GMT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4437D43D31 for ; Mon, 17 Jan 2005 05:11:36 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 68892 invoked by uid 98); 17 Jan 2005 00:11:35 -0500 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 1003 with qmail-scanner-1.20 (spamassassin: 3.0.1. Clear:RC:1(128.227.47.18):. Processed in 0.014012 secs); 17 Jan 2005 05:11:35 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.014012 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with (RC4-MD5 encrypted) SMTP; 17 Jan 2005 00:11:35 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Jan 2005 00:11:35 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED80504A3E8@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Machine(s) not able to reboot Thread-Index: AcT8ToBITcoCKv67SbiKXdwGhUt+KAAA6XDw From: "Will Saxon" To: "jmc" cc: stable@freebsd.org Subject: RE: Machine(s) not able to reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 05:11:36 -0000 > -----Original Message----- > From: jmc [mailto:jcagle@gmail.com] > Sent: Sunday, January 16, 2005 11:39 PM > To: Will Saxon > Cc: stable@freebsd.org > Subject: Re: Machine(s) not able to reboot >=20 >=20 > On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon=20 > wrote: > > Hello, > >=20 > > I have two HP Proliant DL360G3 servers which I recently=20 > upgraded from 5.2.1-R > > to 5.3-R. Since the upgrade, I am not able to cause the=20 > machines to shut down > > or reboot on their own. I always have to physically power=20 > them off and then back > > on. They are SMP machines and I am using ACPI. There are no=20 > other apparent > > problems although one machine did panic today and as a=20 > result I had to drive in > > and power cycle it. >=20 > I haven't heard of this problem before, and I was wondering if today's > 5.3-R errata notice (more than one IPI per APIC causes deadlock) might > have something to do with it. Are these machines running SMP? >=20 > - John >=20 They are. I believe the panic could be related to the problem announced today also, as the panicked machine occasionally sees bursts of high load caused by multiple hungry processes. The other email response to this issue, about this happening=20 when using loaded modules, fixed the problem for me. I compiled new kernels with linux emulation, etc. in kernel and the=20 problem stopped. What a relief. I have verified that at least=20 on one machine the hangup problem will continue even when only=20 usb and acpi are loaded via module. This will happen by default=20 on the Proliant servers since by default usbd is loaded at boot.=20 -Will From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 07:02:40 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45C1A16A4CE for ; Mon, 17 Jan 2005 07:02:40 +0000 (GMT) Received: from cgp.sovintel.ru (cgp.sovintel.ru [212.44.130.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F32E43D31 for ; Mon, 17 Jan 2005 07:02:36 +0000 (GMT) (envelope-from borman@blank.spb.ru) Received: from [212.44.130.15] (HELO xy.blank.spb.ru) by cgp.sovintel.ru (CommuniGate Pro SMTP 4.2.1) with ESMTP-TLS id 130396252 for stable@freebsd.org; Mon, 17 Jan 2005 10:02:34 +0300 Received: from xy.blank.spb.ru (localhost.blank.spb.ru [127.0.0.1]) by xy.blank.spb.ru (8.13.1/8.13.1/blank) with ESMTP id j0H72wsS090357 for ; Mon, 17 Jan 2005 10:02:58 +0300 (MSK) (envelope-from borman@xy.blank.spb.ru) Received: (from borman@localhost) by xy.blank.spb.ru (8.13.1/8.13.1/Submit) id j0H72w00090356 for stable@freebsd.org; Mon, 17 Jan 2005 10:02:58 +0300 (MSK) (envelope-from borman) Date: Mon, 17 Jan 2005 10:02:58 +0300 From: boris karlov To: stable@freebsd.org Message-ID: <20050117070258.GA90236@xy.blank.spb.ru> Mail-Followup-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: twa module - make kernel (modules) failure RELENG_5 i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 07:02:40 -0000 Hello All, I have make kernel failure during compiling twa module (see below). cvsupped RELENG_5 Fri Jan 14. have no any twa devices in the system. (please Cc: me in reply - not subscribed to stable@) thanks. ===> twa cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/twa/../../dev/twa/twa_freebsd.c cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c: In function `twa_scsi_complete': /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: structure has no member named `err_desc' /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: structure has no member named `err_desc' /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:636: error: structure has no member named `err_desc' *** Error code 1 Stop in /usr/src/sys/modules/twa. *** Error code 1 /etc/make.conf: CPUTYPE=p2 NO_CVS=true NO_BIND=true NO_BLUETOOTH=true NO_FORTRAN=true NO_GDB=true NO_I4B=true NO_IPFILTER=true NO_PF=true NO_AUTHPF=true NO_KERBEROS=true NO_NIS=true NO_TCSH=true NO_USB=true NO_VINUM=true NOATM=true NOGAMES=true NOINET6=true NOINFO=true NOPROFILE=true From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 08:34:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4757C16A4CE for ; Mon, 17 Jan 2005 08:34:56 +0000 (GMT) Received: from congo.princess.dyns.cx (dynamic-62-56-53-84.park-s46b.dslaccess.co.uk [62.56.53.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id A532243D41 for ; Mon, 17 Jan 2005 08:34:53 +0000 (GMT) (envelope-from steve@acidy.com) Received: by congo.princess.dyns.cx (Postfix, from userid 1001) id 58140BC4B; Mon, 17 Jan 2005 08:34:50 +0000 (GMT) From: Steve Hodgson To: freebsd-stable@freebsd.org Date: Mon, 17 Jan 2005 08:34:49 +0000 User-Agent: KMail/1.7.2 References: <200501161422.05929.steve@acidy.com> <20050116173758.GA70598@xor.obsecurity.org> In-Reply-To: <20050116173758.GA70598@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501170834.49690.steve@acidy.com> cc: Kris Kennaway Subject: Re: make buildworld for RELENG_5 failing on RELENG_5_3 in /usr/src/usr.sbin/syslogd, _PATH_LOG_PRIV not defined X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 08:34:56 -0000 On Sunday 16 January 2005 17:37, Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 02:22:05PM +0000, Steve Hodgson wrote: > > I'm getting the following error on a RELENG_5_3 box when trying to > > compile the RELENG_5 sources. I've been cvsupping now for about a week > > and continuing to get the same error when we get to syslogd. > > > > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: `_PATH_LOG_PRIV' > > undeclared here (not in a function) > > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: initializer element is > > not constant > > /usr/src/usr.sbin/syslogd/syslogd.c:141: error: (near initialization for > > `funix_secure.name') > > /usr/src/usr.sbin/syslogd/syslogd.c:142: error: initializer element is > > not constant > > /usr/src/usr.sbin/syslogd/syslogd.c:142: error: (near initialization for > > `funix_secure.next') > > > > If I apply the following patch then buildworld continues to completion. > > Note the same error appears in libc and the patch fixes that as well. > > Judging by the build logs and lack of others complaining I'm the only one > > with this problem, so clearly this isn't the correct solution, but it > > works for me. > > > > --- /usr/src/usr.sbin/syslogd/syslogd.c.old Sun Jan 16 12:16:25 > > 2005 +++ /usr/src/usr.sbin/syslogd/syslogd.c Sun Jan 16 12:17:53 2005 > > @@ -74,6 +74,7 @@ > > #define DEFSPRI (LOG_KERN|LOG_CRIT) > > #define TIMERINTVL 30 /* interval for checking flush, > > mark */ > > #define TTYMSGTIME 1 /* timeout passed to ttymsg */ > > +#define _PATH_LOG_PRIV "/var/run/logpriv" > > > > #include > > #include > > --- /usr/src/lib/libc/gen/syslog.c.old Sun Jan 16 14:12:49 2005 > > +++ /usr/src/lib/libc/gen/syslog.c Sun Jan 16 13:03:41 2005 > > @@ -60,6 +60,8 @@ > > > > #include "libc_private.h" > > > > +#define _PATH_LOG_PRIV "/var/run/logpriv" > > + > > static int LogFile = -1; /* fd for log */ > > static int status; /* connection status */ > > static int opened; /* have done openlog() */ > > > > Any ideas on what could be wrong with my system? FYI In general I use > > ccache but i've disabled it for this run, by editing out the commands > > in /etc/make.conf. > > Try > > make cleandir > make cleandir > make buildworld > > Kris This fixed the first error in usr.sbin/syslogd/syslogd.c, but the error in lib/libc/gen/syslog.c still occured, same (half) patch fixes it. Unless anyone has any other ideas I guess I'll continue reattempting this. Are there any objections to doing a make installworld/installkernel on the results after applying my patches - will that bork my system, could it help in anyway? From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 08:40:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 497DA16A4CE; Mon, 17 Jan 2005 08:40:55 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2FFC43D2D; Mon, 17 Jan 2005 08:40:53 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0H8ivSq018844; Mon, 17 Jan 2005 01:44:57 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EB7A11.7030602@freebsd.org> Date: Mon, 17 Jan 2005 01:40:49 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, current@freebsd.org, stable@freebsd.org Content-Type: multipart/mixed; boundary="------------030205060202020502090801" X-Spam-Status: No, hits=0.6 required=3.8 tests=DOMAIN_4U2 autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org Subject: FreeBSD Status Report July-December 2004 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 08:40:55 -0000 This is a multi-part message in MIME format. --------------030205060202020502090801 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit --------------030205060202020502090801 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="report-july-2004-dec-2004.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="report-july-2004-dec-2004.txt" July-December 2004 Status Report Introduction The FreeBSD status report is back again after another small break. The second half of 2004 was incredibly busy; FreeBSD 5.3 was released, the 6-CURRENT development branch started, and EuroBSDCon 2004 was a huge success, just to name a few events. This report is packed with an impressive 44 submissions, the most of any report ever! It's also my pleasure to welcome Max Laier and Tom Rhodes to the status report team. They kindly volunteered to help keep the reports on time and help improve their quality. Max in particular is responsible for the reports being divided up into topics for easier browsing. Many thanks to both for their help! _________________________________________________________________ Projects * Common Address Redundancy Protocol - CARP * Dingo Monthly Report * FreeBSD profile.sh * FreeBSD Release Engineering * FreeSBIE Status Report * Funded FreeBSD kernel development * Improved Multibyte/Wide Character Support * Project Frenzy (FreeBSD-based Live-CD) * Secure Updating Documentation * Hardware Notes * The FreeBSD Dutch Documentation Team Kernel * ATA Driver Status Report * CPU Cache Prefetching * i386 Interrupt Code & PCI Interrupt Routing * kgi4BSD * Layer 2 PFIL_HOOKS * Low-overhead performance monitoring for FreeBSD * Move ARP out of routing table * Network Stack Locking * New Modular Input Device Layer * SMPng Status Report * Sync Protocols (SPPP and NETGRAPH) * TCP Cleanup and Optimizations * TCP Reassembly Rewrite and Optimization * TTCPv2: Transactional TCP version 2 Architectures * FreeBSD on Xen * FreeBSD/arm status report * PowerPC Port Ports * FreeBSD GNOME Project Status Report * OpenOffice.org port status * Ports Collection * Update of the Linux userland infrastructure Vendor / 3rd Party Software * ALTQ * Cronyx Adapters Drivers * OpenBSD packet filter - pf Miscellaneous * EuroBSDCon 2004 submitted papers are online * EuroBSDCon 2005 - Basel / Switzerland * FreeBSD Security Officer and Security Team * FreeBSD Source Repository Mirror for svn/svk * Wiki with new software * Atheros Wireless Support * ifconfig Overhaul * New DHCP Client * Wireless Networking Support _________________________________________________________________ ALTQ URL: http://people.freebsd.org/~mlaier/ALTQ_driver/ URL: http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-curr ent&format=html Contact: Max Laier ALTQ is part of FreeBSD 5.3 release and can be used to do traffic shaping and classification with PF. In CURRENT IPFW gained the ability to do ALTQ classification as well. A steadily increasing number of NIC drivers has been converted to support ALTQ. For details see the ALTQ(4) man-page. Open tasks: 1. Convert/test more NIC drivers. 2. Write documentation. _________________________________________________________________ ATA Driver Status Report Contact: Søren Schmidt The ATA driver is undergoing quite a few important changes, mainly it is being converted into modules so it can be loaded/unloaded at will, and just the pieces for wanted functionality need be present. This calls for ata-raid to finally be rewritten. This is almost done for reading metadata so arrays defined in the BIOS can be used, and its grown quite a few new metadata formats. This also paves the way for ataraid to finally be able to take advantage of some of the newer controllers "RAID" abilities. However this needs more work to materialize but now its finally possible There is also support coming for a few new chipsets as usual. The work is just about finished enough that it can be released as patches to sort out eventual problems before hitting current. The changes are pretty massive as this touches all over the driver infrastructure, so lots of old bugs and has also been spotted and fixed during this journey _________________________________________________________________ Atheros Wireless Support Contact: Sam Leffler The ath driver was updated to support all the new features added to the net80211 layer. As part of this work a new version of the Hardware Access Layer (HAL) module was brought in; this version supports all available Atheros parts found in PCI and Cardbus products. Otherwise, adhoc mode should now be usable, antenna management has been significantly improved, and soft LED support now identifies traffic patterns. The transmit rate control algorithm was split out of the driver into an independent module. Two different algorithms are available with other algorithms (hopefully) to be added. Work is actively going on to add Atheros' SuperG capabilities. _________________________________________________________________ Common Address Redundancy Protocol - CARP URL: http://people.freebsd.org/~mlaier/CARP/ Contact: Max Laier CARP is an alternative to VRRP. In contrast to VRRP it has full support for IPv6 and uses crypto to protect the advertisements. It was developed by OpenBSD due to concerns that the HSRP patent might cover VRRP and CISCO might defend its patent. CARP has, since then, improved a lot over VRRP. CARP is implemented as an in-kernel multicast protocol and displays itself as a pseudo interface to the user. This makes configuration and administration very simple. CARP also incorporates MAC based load-balancing. Patches for RELENG_5 and recent HEAD are available from the URL above. I plan to import these patches in the course of the next two to four month. RELENG_5 has all necessary ABI to support CARP and I might MFC it for release 5.4 or 5.5 - depending how well the HEAD import goes. Open tasks: 1. Please test and send feedback! 2. Write documentation. 3. Import newest OpenBSD changes. _________________________________________________________________ CPU Cache Prefetching URL: http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch Contact: Andre Oppermann Modern CPU's can only perform to their maximum if their working code is in fast L1-3 cache memory instead of the bulk main memory. All of today's CPU's support certain L1-3 cache prefetching instructions which cause data to be retrieved from main memory to the cache ahead of the time that it is already in place when it is eventually accessed by the CPU. CPU Cache Prefetching however is not a golden bullet and has to be used with extreme care and only in very specific places to be beneficial. Incorrect usage can lead to massive cache pollution and a drop in effective performance. Correct and very carefully usage on the other can lead to drastic performance increases in common operations. In the linked patch CPU cache prefetching has been used to prefetch the packet header (OSI layer 2 to 4) into the CPU caches right after entering into the network stack. This avoids a complete CPU stall on the first access to the packet header because packets get DMA'd into main memory and thus never are already pre-cache in the CPU caches. A second use in the patch is in the TCP input code to prefetch the entire struct tcpcb which is very large and used with a very high probability. Use in both of these places show a very significant performance gain but not yet fully quantified. The final patch will include documentation and a guide to evaluate and assess the use of CPU cache prefetch instructions in the kernel. _________________________________________________________________ Cronyx Adapters Drivers URL: http://www.cronyx.ru/software Contact: Roman Kurakin Currently FreeBSD supports three family of Cronyx sync adapters: Tau-PCI - cp(4), Tau-ISA - ctau(4) and Sigma - cx(4). All these drivers were updated (in 6.current) and now they are Giant free. However, this is true only for sppp(4). If you are using Netgraph or async mode (for Sigma) you may need to turn mpsafenet off for that driver with appropriate kernel variable. Open tasks: 1. Now all these drivers and sppp(4) are using recursive lock. So the first task is to make these locks non recursive. 2. Second task is to check/make drivers workable in netgraph/async mode. 3. I think about ability to switch between sppp/netgraph mode at runtime. For now you should recompile module/kernel to change mode. _________________________________________________________________ Dingo Monthly Report URL: http://www.freebsd.org/projects/dingo/index.html Contact: George Neville-Neil In the last month we set up the project page noted above and also created a p4 branch for those of us who use p4 to do work outside of CVS. _________________________________________________________________ EuroBSDCon 2004 submitted papers are online URL: http://www.eurobsdcon2004.de/papers.html Contact: Patrick M. Hausen Finally all of the papers and presentations are online for download from our conference website. Thanks again to all who helped make EuroBSDCon 2004 a success. _________________________________________________________________ EuroBSDCon 2005 - Basel / Switzerland URL: http://www.eurobsdcon.org/ Contact: Max Laier This year's EuroBSDCon will be held at the University of Basel, Switzerland from 25th through 27th November. The call for papers should happen shortly. Please consider attending or even presenting. Check the conference homepage for more information. _________________________________________________________________ FreeBSD GNOME Project Status Report URL: http://www.FreeBSD.org/gnome/ Contact: Joe Marcus We haven't produced a status report in a while, but that's just because we've been busy. Since our last report in March 2004, we have added three new team members: Koop Mast (kwm), Jeremy Messenger (mezz), and Michael Johnson (ahze). Jeremy has been quite helpful in GNOME development porting while Michael and Koop have been focusing on improving GNOME multimedia, especially GStreamer. The stable release of GNOME is now up to 2.8.2, and we are actively working on the GNOME 2.9 development branch with is slated to become 2.10 on March 9 of this year. The GNOME Tinderbox is still cranking away, and producing packages for both the stable and development releases of GNOME for all supported i386 versions of FreeBSD. Thanks to Michael Johnson, the FreeBSD GNOME team has recently been given permission to use the Firefox and Thunderbird names , official icons, and to produce officially branded builds. Mozilla has also been very interested in merging our local patches back into the official source tree. This should greatly improve the quality of Firefox and Thunderbird on FreeBSD moving forward. Finally, Adam Weinberger (adamw) has been pestering the team for photos so that we can finally show the community who we are. It is still unclear as to whether or not this will attract more FreeBSD GNOME users, or land us on the Homeland Security no-fly list. Open tasks: 1. Need help porting HAL to FreeBSD (contact marcus@FreeBSD.org ) 2. Need help porting libburn to FreeBSD (contact bland@FreeBSD.org ) 3. Anyone interested in reviving Gnome Meeting should contact kwm@FreeBSD.org _________________________________________________________________ FreeBSD on Xen URL: http://www.fsmware.com/xenofreebsd/ URL: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Contact: Kip Macy FreeBSD 5.2.1 is stable on the stable branch of Xen as a guest. FreeBSD 5.3 runs on the stable branch of Xen as a guest, but a couple of bugs need to be tracked down. Open tasks: 1. FreeBSD support for running in Domain 0 (host) 2. FreeBSD support for VM checkpoint and migration _________________________________________________________________ FreeBSD profile.sh URL: https://projects.fsck.ch/profile Contact: Tobias Roth FreeBSD profile.sh is targeted at laptops. It allows to define multiple network environments (eg, home, work), and will then detect in which environment the laptop is started and configure it accordingly. Almost everything from under /etc can be configured per environment, and only the overrides to the default /etc have to be defined. Suspending in one environment and resuming in a different one is also supported. Proper integration into the acpi/apm and several small improvements are underway. More testing with different system configurations is needed. _________________________________________________________________ FreeBSD Release Engineering URL: http://www.FreeBSD.org/releng Contact: Scott Long At long last, FreeBSD 5.3 was released in November of 2004. This marked the start of the RELENG_5/5-STABLE branch and the beginning of the 6-CURRENT development branch. Many thanks to the tireless efforts of the FreeBSD developer and user community for making this release a success. FreeBSD 4.11 release engineering is also now in progress. This will be the final release from the 4.x series and is mainly incremental bug fixes and a handful of feature additions. Of note is that the IBM ServeRAID 'IPS' driver is now supported on 4.x and will be included in this release, and the Linux emulation layer has been updated to support a RedHat 8.0 userland. The release is expected to be available on January 24. Looking forward, there will be several FreeBSD 5.x releases in the coming year. FreeBSD 5.4 release engineering will start in March, and FreeBSD 5.5 release engineering will likely start in June. These releases are expected to be more conservative than previous 5.x releases and will follow the same philosophy as previous -STABLE branches of fixing bugs and adding incremental improvements while maintaining API stability. For the 6-CURRENT development branch as well as all future development and stable branches, we are planning to move to a schedule with fixed timelines that move away from the uncertainty and wild schedule fluctuations of the previous 5.x releases. This means that major branches will happen at 18 month intervals, and releases from those branches will happen at 4 month intervals. There will also be a dedicated period of testing and bug fixing at the beginning of each branch before the first release is cut from that branch. With the shorter and more defined release schedules, we hope to lessen the problem of needed features not reaching users in a reasonable time, as happened too often with 5.x. This is a significant change in our strategy, and we look forward to realizing the benefits of it. This will kick off with the RELENG_6 branch happing in June of 2005, followed by the 6.0 release in August of 2005. Also on the roadmap is a plan to combine the live-iso disk2 and the install distributions of disk1 into a single disk which can be used for both installation and for recovery. 3rd party packages that currently reside on disc1 will be moved to a disk2 that will be dedicated to these packages. This move will allow us to deal with the ever growing size of packages and also provide more flexibility to vendors that wish to add their own packages to the releases. It also opens the door to more advanced installers being put in place of sysinstall. Anyone interested in helping with this is encouraged to contact us. _________________________________________________________________ FreeBSD Security Officer and Security Team URL: http://www.freebsd.org/security/ URL: http://www.freebsd.org/security/charter.html URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff -listing.html#STAFF-SECTEAM URL: http://vuxml.freebsd.org/ URL: http://cvsweb.freebsd.org/ports/security/portaudit/ Contact: Jacques Vidrine Contact: Security Officer Contact: Security Team During 2004, there were several notable changes and events related to the FreeBSD Security Officer role and Security Team. The charter for the Security Officer (SO) as approved by Core in 2002 was finally published on the web site. This document describes the mission, responsibilities, and authorities of the SO. (The current SO is Jacques Vidrine.) The SO is supported by a Deputy SO and the Security Team. In April, Chris Faulhaber resigned as Deputy SO and Dag-Erling Smorgrav was appointed in his place. Also during the year, the following team members resigned: Julian Elischer, Bill Fumerola, Daniel Harris, Trevor Johnson, Kris Kennaway, Mark Murray, Wes Peters, Bruce Simpson, and Bill Swingle; while the following became new members: Josef El-Rayes, Simon L. Nielsen, Colin Percival, and Tom Rhodes. A huge thanks is due to all past and current members! The current Security Team membership is published on the web site. With the release of FreeBSD 4.8, the SO began extended support for some FreeBSD releases and their corresponding security branches. "Early adopter" branches, such as FreeBSD 5.0 (RELENG_5_0), are supported for at least six months. "Normal" branches are supported for at least one year. "Extended" branches, such as FreeBSD 5.3 (RELENG_5_3), are supported for at least two years. The currently supported branches and their estimated "end of life" (EoL) dates are published on the FreeBSD Security Information web page. In 2004, four releases "expired": 4.7, 4.9, 5.1, and 5.2. With the releases of FreeBSD 4.10 and 5.3, the SO and the Release Engineering team extended the scope of security branches to incorporate critical bug fixes unrelated to security issues. Currently, separate Errata Notices are published for such fixes. In the future, Security Advisories and Errata Notices will be merged and handled uniformly. 17 Security Advisories were published in 2004, covering 8 issues specific to FreeBSD and 9 general issues. 2004 also saw the introduction of the Vulnerabilities and Exposures Markup Language (VuXML). VuXML is a markup language designed for the documentation of security issues within a single package collection. Over 325 security issues in the Ports Collection have been documented already in the FreeBSD Project's VuXML document by the Security Team and other committers. This document is currently maintained in the ports repository, path ports/security/vuxml/vuln.xml. The contents of the document are made available in a human-readable form at the FreeBSD VuXML web site. The "portaudit" tool can be used to audit your local system against the listed issues. Starting in November, the popular FreshPorts.org web site also tracks issues documented in VuXML. _________________________________________________________________ FreeBSD Source Repository Mirror for svn/svk URL: http://svn.clkao.org/svnweb/freebsd/ URL: http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/ URL: http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/ URL: http://svk.elixus.org/ Contact: Kao Chia-liang A public Subversion mirror of the FreeBSD repository is provided at svn://svn.clkao.org/freebsd/. This is intended for people who would like to try the svk distributed version control system. svk allows you to mirror the whole repository and commit when offline. It also provides history-sensitive branching, merging, and patches. Non-committers can easily maintain their own branch and track upstream changes while their patches are being reviewed. _________________________________________________________________ FreeBSD/arm status report URL: http://www.freebsd.org/platforms/arm Contact: Olivier Houchard FreeBSD/arm made some huge progress. It can boot multiuser, and run things like "make world" and perl on the IQ31244 board. It also now has support for various things, including DDB, KTR, ptrace and kernel modules. A patch is available for early gdb support, and the libpthread almost works. _________________________________________________________________ FreeSBIE Status Report URL: http://www.FreeSBIE.org URL: http://liste.gufi.org/mailman/listinfo/freesbie Contact: FreeSBIE Staff FreeSBIE is a Live-CD based on the FreeBSD Operating system, or even easier, a FreeBSD-based operating system that works directly from a CD, without touching your hard drive. On December, 6th, 2004, FreeSBIE Staff released FreeSBIE 1.1, based on FreeBSD 5.3-RELEASE. Some of the innovations are: a renewed series of scripts to support power users in the use of FreeSBIE 1.1, an installer to let users install FreeSBIE 1.1 on their hard drives, thus having a powerful operating system such as FreeBSD, but with all the personalizations FreeSBIE 1.1 carries, the presence of the best open source software, chosen and personalized, such as X.Org 6.7, XFCE 4.2RC1, Firefox 1.0 and Thunderbird 0.9.2. For a complete list of the included software, please consult: http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt At EuroBSDCon 2004 in Karlsruhe, Germany, people from the FreeSBIE staff gave a talk, deeping into FreeSBIE scripts implementation and use. Open tasks: 1. Translating website and documentation _________________________________________________________________ Funded FreeBSD kernel development URL: http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/0009 71.html Contact: Poul-Henning Kamp A longish status report for the 6 months of funded development was posted on announce, rather than repeat it here, you can find it at the link provided. _________________________________________________________________ Hardware Notes URL: http://www.FreeBSD.org/releases/5.3R/hardware-i386.html URL: http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html Contact: Simon L. Nielsen Contact: Christian Brueffer The FreeBSD Hardware Notes have been (mostly) converted to being directly generated from the driver manual pages. This makes it much simpler to maintain the Hardware Notes, so they should be more accurate. The Hardware Notes for FreeBSD 5.3 use this new system. _________________________________________________________________ i386 Interrupt Code & PCI Interrupt Routing Contact: John Baldwin The ACPI PCI link support code was reworked to work around some limitations in the previous implementation. The new version more closely matches the current non-ACPI $PIR link support. Enhancements include disabling unused link devices during boot and using a simpler and more reliable algorithm for choosing ISA IRQs for unrouted link devices. Support for using the local APIC timer to drive the kernel clocks instead of the ISA timer and i8254 clock is currently being worked on in the jhb_clock perforce branch. It is mostly complete and will probably hit the tree in the near future. By letting each CPU use its own private timer to drive the kernel clocks, the kernel no longer has to IPI all the other CPUs in the system every time a clock interrupt occurs. _________________________________________________________________ ifconfig Overhaul Contact: Sam Leffler The ifconfig program used to configure network interfaces was overhauled. Over the years ifconfig has grown into a complex and often contorted piece of software that is hard to understand and difficult to maintain. The primary motivation for this work was to enable minimal configurations (for embedded use) without changing the code and to support future additions in a modular way. Functionality is now broken out into separate files and operations are registered with the central ifconfig code base. Features are configured simply by specifying which code is to be included when building the program. In the future the plan is for ifconfig to auto-load functionality through dynamic libraries. This mechanism will allow, for example, third party software packages to provide kernel services and ifconfig add-on code without changing the base system. _________________________________________________________________ Improved Multibyte/Wide Character Support Contact: Tim Robbins Support for multibyte characters has been added to many more base system utilities, including basename, col, colcrt, colrm, column, fmt, look, nl, od, rev, sed, tr, and ul. As a result of changes to the C library (see below), most utilities that perform regular expression matching or pathname globbing now support multibyte characters in these aspects. The regular expression matching and pathname globbing routines in the C library have been improved and now recognize multibyte characters. Various performance improvements have been made to the wide character I/O functions. The obsolete 4.4BSD "rune" interface and UTF2 encoding have been removed from the 6-CURRENT branch. Work is progressing on implementations of the POSIX iconv and localedef interfaces for potential inclusion into the FreeBSD 6.0 release. _________________________________________________________________ kgi4BSD URL: http://www.freebsd.org/~nsouch/kgi4BSD URL: http://wiki.daemon.li/moin.cgi/KGI Contact: Nicholas Souchu The project was very quiet (but still alive!) and mostly dedicated to testing by volunteers. New documentation at http://wiki.daemon.li/moin.cgi/KGI . Open tasks: 1. Help improving the documentation _________________________________________________________________ Layer 2 PFIL_HOOKS URL: http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html Contact: Andre Oppermann IPFW2 has been converted to use PFIL_HOOKS for the IP[46] in/output path. (See link.) Not converted yet is the Layer 2 Etherfilter functionality of IPFW2. It is still directly called from the ether_input/output and bridging code. Layer 2 PFIL_HOOKS provide a general abstraction for packet filters to hook into the Layer 2 packet path and filter or manipulate such packets. This makes it possible to use not only IPFW2 but also PF and others for Layer 2 filtering. _________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: http://people.freebsd.org/~jkoshy/projects/perf-measurement/ Contact: Joseph Koshy System-wide and process-virtual counting-mode performance monitoring counters are now supported for the AMD Athlon and Intel P4 CPUs. SMP works, but is prone to freezes. Immediate next steps include: (1) implementing the system-wide and process-virtual sampling modes, (2) debugging, (3) writing a test suite and (4) improving the project's documentation. _________________________________________________________________ Move ARP out of routing table URL: http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.h tml Contact: Andre Oppermann Contact: Qing Li The ARP IP address to MAC address mapping does not belong into the routing table (FIB) as it is currently done. This will move it to its own hash based structure which will be instantiated per each 802.1 broadcast domain. With this change it is possible to have more than one interface in the same IP subnet and layer 2 broadcast domain. The ARP handling and the routing table will be quite a bit simplified afterwards. As an additional benefit full MAC address based accounting will be provided. Qing Li has become the driver and implementor of this project and is expected to post a first patch for comments shortly in February 2005. _________________________________________________________________ Network Stack Locking URL: http://www.freebsd.org/projects/netperf/ URL: http://www.watson.org/~robert/freebsd/netperf/ Contact: Robert Watson The netperf project is working to enhance the performance of the FreeBSD network stack. This work grew out of the SMPng Project, which moved the FreeBSD kernel from a "Giant Lock" to more fine-grained locking and multi-threading. SMPng offered both performance improvement and degradation for the network stack, improving parallelism and preemption, but substantially increasing per-packet processing costs. The netperf project is primarily focused on further improving parallelism in network processing while reducing the SMP synchronization overhead. This in turn will lead to higher processing throughput and lower processing latency. Tasks include completing the locking work, optimizing locking strategies, amortizing locking costs, introducing new synchronization primitives, adopting non-locking synchronization strategies, and improving opportunities for parallelism through additional threading. Between July, 2004, and December, 2004, the Netperf project did a great deal of work, for which there is room only to include limited information. Much more information is available by visiting the URLS above, including information on a variety of on-going activities. Accomplishments include: July, 2004: A variety of improvements to PCB locking in the IPv6 implementation; locking for the if_xl driver; socket locking for the NFS client; cleanup of the soreceive() code path including structural improvements, assertions, and locking fixes; cleanup of the IPX/SPX code in preparation for locking; additional locking and locking assertions for the TCP implementation; bug fixes for locking and memory allocation in raw IP; netatalk cleanup and locking merged to FreeBSD CVS ; locking for many netgraph nodes merged to FreeBSD CVS ; SLIP structural improvements; experimental locking for netatalk ifaddrs; BPF locking optimizations (merged); Giant assertions for VFS to check VFS/network stack boundaries; UNIX domain socket locking optimizations; expansion of lock order documentation in WITNESS, additional NFS server code running MPSAFE; pipe locking optimizations to improve pipe allocation performance; Giant no longer required for fstat on sockets and pipes (merged); Giant no longer required for socket and pipe file descriptor closes (merged); IFF_NEEDSGIANT interface flag added to support compatibility operation for unlocked device drivers (merged) ; merged accept filter locking to FreeBSD CVS; documented uidinfo locking strategy (merged); Giant use reduced in fcntl(). August, 2004: UMA KTR tracing (merged); UDP broadcast receive locking optimizations (merged); TCP locking cleanup and documentation; IPv6 inpcb locking, cleanup, and structural improvements; IPv6 inpcb locking merged to FreeBSD CVS ; KTR for systems calls added to i386; substantial optimizations of entropy harvesting synchronization (merged) ; callout(9) sampling converted to KTR (merged); inpcb socket option locking (merged); GIANT_REQUIRED removed from netatalk in FreeBSD CVS; merged ADAPTIVE_GIANT to FreeBSD CVS, resulting in substantial performance improvements in many kernel IPC-intensive benchmarks ; prepend room for link layer headers to the UDP header mbuf to avoid one allocation per UDP send (merged); a variety of UDP bug fixes (merged); additional network interfaces marked MPSAFE; UNIX domain socket locking reformulated to protect so_pcb pointers; MP_WATCHDOG, a facility to dedicate additional HTT logical CPUs as watchdog CPUs developed (merged) ; annotation of UNIX domain socket locking merged to FreeBSD CVS; kqueue locking developed and merged by John-Mark Gurney ; task list for netinet6 locking created; conditional locking relating to kqueues and socket buffers eliminated (merged); NFS server locking bugfixes (merged); in6_prefix code removed from netinet6 by George Neville-Neil, lowering the work load for netinet6 (merged); unused random tick code in netinet6 removed (merged); ng_tty, IPX, KAME IPSEC now declare dependence on Giant using compile-time declaration NET_NEEDS_GIANT("component") permitting the kernel to detect unsafe components and automatically acquire the Giant lock over network stack operation if needed (merged) ; additional locking optimizations for entropy code (merged); Giant disabled by default in the netperf development branch (merged). September, 2004: bugs fixed relating to Netgraph's use of the kernel linker while not holding Giant (merged); merged removal of Giant over the network stack by default to FreeBSD CVS ; races relating to netinet6 and if_afdata corrected (merged); annotation of possible races in the BPF code; BPF code converted to queue(3) (merged); race in sopoll() corrected (merged). October, 2004: IPv6 netisr marked as MPSAFE; TCP timers locked, annotated, and asserted (merged); IP socket option locking and cleanup (merged); Netgraph ISR marked MPSAFE; netatalk ISR marked MPSAFE (merged); some interface list locking cleanup (merged); use after free bug relating to entropy harvesting and ethernet fixed (merged); soclose()/sofree() race fixed (merged); IFF_LOCKGIANT() and IFF_UNLOCKGIANT() added to acquire Giant as needed when entering the ioctls of non-MPSAFE network interfaces. November, 2004: cleanup of UDPv6 static global variables (merged); FreeBSD 5.3 released! First release of FreeBSD with an MPSAFE and Giant-free network stack as the default configuration! ; additional TCP locking documentation and cleanup (merged); optimization to use file descriptor reference counts instead of socket reference counts for frequent operations results in substantial performance optimizations for high-volume send/receive (merged) ; an accept bug is fixed (merged) experimental network polling locking introduced; substantial measurement and optimization of mutex and locking primitives (merged) ; experimental modifications to UMA to use critical sections to protect per-CPU caches instead of mutexes yield substantial micro-benchmark benefits when combined with experimental critical section optimizations ; FreeBSD Project Netperf page launched; performance micro-benchmarks benchmarks reveal IP forwarding latency in 5.x is measurably better than 4.x on UP when combined with optional network stack direct dispatch; several NFS server locking bugfixes (merged); development of new mbufqueue primitives and substantial experimentation with them permits development of amortized cost locking APIs for handoff between the network stack and network device drivers (work in collaboration with Sandvine, Inc) ; Linux TCP_INFO API added to allow user-space monitoring of TCP state (merged); SMPng task list updated; UDP static/global fixes merged to RELENG_5. December, 2004: UDP static/global fixes developed for multi-threaded in-bound UDP processing (merged); socket buffer locking fixes for urgent TCP input processing (merged); lockless read optimizations for IF_DEQUEUE() and IF_DRAIN(); Giant-free close for sockets/pipes/... merged to FreeBSD CVS; optimize mass-dequeues of mbuf chains in netisr processing; netrate tool merged to RELENG_5; TCP locking fixes merged to RELENG_5; "show alllocks" added to DDB (merged); IPX locking bugfixes (merged); IPX/SPX __packed fixes (merged); IPX/SPX moved to queue(9) (merged); TCP locking fixes and annotations merged to FreeBSD CVS; IPX/SPX globals and pcb locking (merged); IPX/SPX marked MPSAFE (merged) ; IP socket options locking merged to FreeBSD; SPPP locked by Roman Kurakin (merged); UNIX domain socket locking fixes by Alan Cox (merged). On-going work continues with regard to locking down network stack components, including additional netinet6 locking, mbuf queue facilities and operations; benchmarking; moving to critical sections or per-CPU mutexes for UMA per-CPU caches; moving to critical sections or per-CPU mutexes for malloc(9) statistics; elimination of separate mbuf allocator statistics; additional interface locking; a broad variety of cleanups and documentation of locking; a broad range of optimizations. _________________________________________________________________ New DHCP Client Contact: Sam Leffler The OpenBSD dhcp client program has been ported and enhanced to listen for 802.11-related events from the kernel. This enables immediate IP address acquisition when roaming (as opposed to the polling done by the old code). The main change from the previous client is that there is one dhclient process per interface as opposed to one for the entire system. This necessitates changes to the system startup scripts. Incorporation into the base system is waiting on a volunteer who will shepherd the changes into the tree and deal with bugs. _________________________________________________________________ New Modular Input Device Layer URL: http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html Contact: Philip Paeps Following a number of mailing lists discussions on the topic, work has been progressing on the development of a new modular input device layer for FreeBSD. The purpose of this is twofold: * Easier development of new input device drivers. * Support for concurrent use of multiple input devices, particularly the hot-pluggable kind. Currently, implementing support for new input devices is a painful process and there is great potential for code-duplication. The new input device layer will provide a simple API for developers to send events from their hardware on to the higher regions of the kernel in a consistent way, much like the 'input-core' driver in the Linux kernel. Using multiple input devices at the moment is painful at best. With the new input device layer, events from different devices will be properly serialized before they are sent to other parts of the kernel. This will allow one to easily use, for instance, multiple USB keyboards in a virtual terminal. The work on this is still in very rudimentary state. It is expected that the first visible changes will be committed to -CURRENT around late February or early March. _________________________________________________________________ OpenBSD packet filter - pf URL: http://pf4freebsd.love2party.net/ Contact: Max Laier Contact: Daniel Hartmeier FreeBSD 5.3 is the first release to include PF. It went out okay, but some bugs were discovered too late to make it on the CD. It is recommend to update `src/sys/contrib/pf' to RELENG_5. The specific issues addressed are: * Possible NULL-deref with user/group rules. * Crash with binat on dynamic interfaces. * Silent dropping of IPv6 packets with option headers. * Endless loops with `static-port' rules. Most of these issues were discovered by FreeBSD users and got fed back to OpenBSD. This is a prime example of open source at work. The Handbook's Firewall section was modified to mention PF as an alternative to IPFW and IPF. Open tasks: 1. Write more documentation/articles. 2. Write an IPFilter to PF migration guide/tool. _________________________________________________________________ OpenOffice.org port status URL: http://porting.openoffice.org/freebsd/ URL: http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/Free BSD/ URL: http://sourceforge.jp/projects/waooo/files/ Contact: Maho Nakata OpenOffice.org 2.0 status * OpenOffice.org 2.0 is planned to be released in March 2005. Currently developer snapshot versions are available. Now one of the developer version has been ported, and committed to ports tree (/usr/ports/editors/openoffice-2.0-devel). * Packages for 5.3-RELEASE are available at http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53I ntel_install_en-US.tbz etc., and soon it will also available at : http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/ FreeBSD/ with the language pack. * Almost all of the patches required to build will be integrated to master. http://www.openoffice.org/issues/show_bug.cgi?id=40187 * Now we have three external ports : lang/gcc-ooo, devel/bison-devel and devel/epm. To avoid regressions and bugs of gcc, we use the exactly same gcc as Hamburg team (former StarDivision) uses. We need bison later than 1.785a. Note this port CONFLICTS with devel/bison. Epm is a package manager which now OpenOffice.org uses. OpenOffice.org 1.1 status * 1.1.4 has been ported and committed to ports tree. * Packages are available at http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/ FreeBSD/ . * Now recognizes Linux version of Java JDKs. General * Invoking OpenOffice.org from command line has been changed. Now `.org' is mandatory. e.g. openoffice-1.1.4 -> openoffice.org-1.1.4. Since the name of the software is OpenOffice.org, not OpenOffice. We are also considering the name of the ports (/usr/ports/editors/openoffice-2.0-devel -> openoffice.org2-devel etc) * Now marked as BROKEN OOo ports for prior than 5.3-RELEASE and 4.11-RELEASE. These ports have been suffering from a minor implementation difference of rtld.c between FreeBSD and Linux, Solaris, NetBSD. We have been applying a patch adding _end in mapfile. We need this since rtld depend on existence of _end symbol in obj_from_addr_end, unfortunately this seem to induce hard-to-solve errors. A great progress has been made kan, rtld now do not depend on _end. A fix was committed 2004/02/25 17:06:16, http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c. diff?r1=1.91&r2=1.92&f=h . * Benchmark test! Building OOo requires huge resources. We just would like to know the build timings, so that how your machine is well tuned for demanding jobs. http://porting.openoffice.org/freebsd/benchmark.html . Currently, GOTO daichi (daichi)'s Pentium 4 3.0GHz machine build fastest. Just 1h25m22.42s for second build of OOo 1.1.4, using ccache. * SDK tutorial is available at http://porting.openoffice.org/freebsd/sdk.html * Still implementation test and quality assurance have not yet been done. Even systematic documentations are not yet available for FreeBSD. http://porting.openoffice.org/freebsd/testing.html and http://porting.openoffice.org/freebsd/QA.html for details. Acknowledgments Two persons contributed in many aspects. Pavel Janik (reviewing and giving me much advice) and Kris Kennaway (extremely patient builder). and (then, alphabetical order by first name). daichi, Eric Bachard, kan, lofi, Martin Hollmichel, nork, obrien, Sander Vesik, sem, Stefan Taxhet, and volunteers of OpenOffice.org developers (esp. SUN Microsystems, Inc.) for cooperation and warm encouragements. _________________________________________________________________ Ports Collection URL: http://www.FreeBSD.org/ports/ URL: http://portsmon.firepipe.net/index.html Contact: Mark Linimon Contact: Erwin Lansing Since the last report on the Ports Collection, much has changed. Organizationally, the portmgr team saw the departure of some of the long-term members, and the addition of some newer members, Oliver Eikemeier, Kirill Ponomarew and Mark Linimon. Later on, portmgr also had to say goodbye to Will Andrews. In addition, we have gained quite a few new ports committers during this time period, and their contributions are quite welcome! Most effort was devoted to two releases. The 5.3 release saw an especially long freeze period, but due to the good shape of the ports tree, the freeze for the 4.11 could be kept to a minimum. Several iterations of new infrastructure changes were tested on the cluster and committed. Also, the cluster now builds packages for 6-CURRENT, increasing the total number of different build environment to 10. Additionally, several sweeps through the ports tree were made to bring more uniformity in variables used in the different ports and their values, e.g. BROKEN , IGNORE , DEPRECATED , USE_GCC , and and others. In technical terms, the largest change was moving to the X.org codebase as our default X11 implementation. At the same time, code was committed to be able to select either the X.org code or the XFree86 code, which also saw an update during that time. Due to some hard work by Eric Anholt, new committer Dejan Lesjak, and Joe Marcus Clarke, all of this happened more smoothly than could have reasonably been expected. As well, GNOME and KDE saw updates during this time, as did Perl and the Java framework. Further, there were some updates to the Porter's Handbook, but more sections are still in need of updates to include recent changes in practices. Also, during this time, Bill Fenner was able to fix a bug in his distfile survey . Shortly before the release for 4.11 our existing linux_base was marked forbidden due to security issues. A lot of effort was spent to upgrade the default version to 8 from 7 to ship 4.11 with a working linuxolator. Due to stability problems in the April-May timeframe, the package builds for the Alpha were dropped. After Ken Smith and others put some work into the Alphas in the build cluster, package builds for 4.X were reenabled late in 2004. Ports QA reminders -- portmgr team members are now sending out periodic email about problems in the Ports Collection. The current set includes: * a public list of all ports to be removed due to security problems, build failures, or general obsolescence, unless they are fixed first * private email to all maintainers of the affected ports (including ports dependent on the above) * private email to all maintainers of ports that are marked BROKEN and/or FORBIDDEN * private email to maintainers who aren't committers, who have PRs filed against their ports (to flag PRs that might never have been Cc:ed to them) * public email about port commits that break building of INDEX * public email about port commits that send the revision metadata backwards (and thus confuse tools like portupgrade) The idea behind each of these reminders is to try to increase the visibility of problems in the Ports Collection so that problems can be fixed faster. Finally, it should be noted that we passed yet another milestone and the Ports Collection now contains over 12,000 ports. Open tasks: 1. The majority of our build errors are still due to compilation problems, primarily from the gcc upgrades. Thanks to the efforts of many volunteers, these are decreasing, but there is still much more work to be done. 2. The next highest number of build errors are caused by code that does not build on our 64-bit architectures due to the assumption that "all the world's a PC." Here is the entire list ; the individual bars are clickable. This will become more and more important now that the amd64 port has been promoted to tier-1 status. 3. A lot of progress has been meed to crack down on ports that install files outside the approved directories and/or do not de-install cleanly (see "Extra files not listed in PLIST" on pointyhat ) and this will remain a focus area. _________________________________________________________________ PowerPC Port URL: http://www.freebsd.org/~grehan/miniinst.iso URL: http://www.freebsd.org/~grehan/miniinst.txt Contact: Peter Grehan A natively built 6.0-CURRENT miniinst ISO is available at the above link. It runs best on G4 Powermacs, but may run on other Newworld machines. See the release notes for full details. As usual, lots of help is needed. This is a great project for those who want to delve deeply into FreeBSD kernel internals. _________________________________________________________________ Project Frenzy (FreeBSD-based Live-CD) URL: http://frenzy.osdn.org.ua/ URL: http://frenzy.osdn.org.ua/eng/ Contact: Sergei Mozhaisky Frenzy is a "portable system administrator toolkit," Live-CD based on FreeBSD. It generally contains software for hardware tests, file system check, security check and network setup and analysis. Current version 0.3, based on FreeBSD 5.2.1-RELEASE, contains almost 400 applications in 200MB ISO-image. Tasks for next release: script for installation to HDD; unified system configuration tool; updating of software collection. _________________________________________________________________ Secure Updating URL: http://www.daemonology.net/portsnap/ URL: http://www.daemonology.net/freebsd-update/ Contact: Colin Percival In my continuing quest to secure the mechanisms by which FreeBSD users keep their systems up to date, I've added a new tool: Portsnap. Available as sysutils/portsnap in the ports tree, this utility securely downloads and updates a compressed snapshot of the ports tree; this can then be used to extract or update an uncompressed ports tree. In addition to operating in an end-to-end secure manner thanks to RSA signatures, portsnap operates entirely over HTTP and can use under one tenth of the bandwidth of cvsup for users who update their ports tree more than once a week. FreeBSD Update -- my utility for secure and efficient binary tracking of the Security/Errata branches -- continues to be widely used, with over 100 machines downloading security or errata updates daily. At some point in the future I intend to bring both of these utilities into the FreeBSD base system, probably starting with portsnap. _________________________________________________________________ SMPng Status Report URL: http://www.FreeBSD.org/smp/ Contact: John Baldwin Contact: Lots of changes happened inside the network stack that will hopefully be covered by a separate report. Outside of the network stack, several changes were made however including changes to proc locking, making the kernel thread scheduler preemptive, fixing several priority inversion bugs in the scheduler, and a few performance tweaks in the mutex implementation. Locking work on struct proc and its various substructures continued with locking added where needed for struct uprof, struct rusage, and struct pstats. This also included reworking how the kernel stores process time statistics to store the raw struct bintime and tick counts internally and only compute the more user friendly values when requested via getrusage() or wait4(). Support for kernel thread preemption was added to the scheduler. Basically, when a thread makes another thread runnable, it may yield the current CPU to the new thread if the new thread has a more important priority. Previously, only interrupt threads preempted other threads and the implementation would occasionally trigger spurious context switches. This change exposed bugs in other parts of the kernel and was turned off by default in RELENG_5. Currently, only the i386, amd64, and alpha platforms support native preemption. Several priority inversion bugs present in the scheduler due to various changes to the kernel from SMPng were also fixed. Most of the credit for these fixes belongs Stephan Uphoff who has recently been added as a new committer. Fixes include: closing a race in the turnstile wakeup code, changing the sleep queue code to store threads in FIFO order so that the sleep queue wakeup code properly handles having a thread's priority changes, and abstracting the concept of priority lending so that the thread scheduler is now able to properly track priority inheritance and handle priority changes for threads blocked on a turnstile. Works in progress include separating critical sections from spin mutexes some so that bare critical sections become very cheap as well as continuing to change the various ABI compatibility layers to use in-kernel versions of system calls to reduce stackgap usage and make the system call wrappers MPSAFE. _________________________________________________________________ Sync Protocols (SPPP and NETGRAPH) URL: http://www.freebsd.org/~rik Contact: Roman Kurakin sppp(4) was updated (in 6.current) to be able to work in mpsafe mode. For compatibility if an interface is unable to work in mpsafe mode, sppp will not use mpsafe locks. Support of FrameRelay AnnexD was added as a historical commit. Many of Cronyx users were expecting this commit for a long long time, and most of them still prefer sppp vs netgraph because of simplicity of its configuration (especially for ppp (vs mpd) and fr (vs a couple of netgraph modules). After MFCing this I'll finally close a PR 21771, from 2000/10/05 _________________________________________________________________ TCP Cleanup and Optimizations URL: http://people.freebsd.org/~andre/tcpcleanup.html Contact: Andre Oppermann The TCP code in FreeBSD has evolved significantly since the fork from 4.4BSD-Lite2 in 1994 primarily due to new features and refinements of the TCP specifications. The TCP code now needs a general overhaul, streamlining a cleanup to make it easily comprehensible, maintainable and extensible again. In addition there are many little optimizations that can be done during such an operation propelling FreeBSD back at the top of the best performing TCP/IP stacks again, a position it has held for the longest time in the 90's. This overhaul is a very involved and delicate matter and needs extensive formal and actual testing to ensure no regressions compared to the current code. The effort needed for this work is about two man-month of fully focused and dedicated time. To get it done I need funding to take time off my day job and to dedicate me to FreeBSD work much the way PHK did with his buffer cache and vnode rework projects. In February 2005 I will officially announce the funding request with a detailed description of the work and how the funding works. In general I can write invoices for companies wishing to sponsor this work on expenses. Tax exempt donations can probably be arranged through the FreeBSD foundation. Solicitations of money are already welcome, please contact me on the email address above. Open tasks: 1. Funding for two man-month equivalents of my time. 2. If you want or intend to sponsor US$1k or more please contact me in advance already now. _________________________________________________________________ TCP Reassembly Rewrite and Optimization URL: http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch URL: http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.ht ml Contact: Andre Oppermann Currently TCP segment reassembly is implemented as a linked list of segments. With today's high bandwidth links and large bandwidth*delay products this doesn't scale and perform well. The rewrite optimizes a large number of operational aspects of the segments reassembly process. For example it is very likely that the just arrived segment attaches to the end of the reassembly queue, so we check that first. Second we check if it is the missing segment or alternatively attaches to the start of the reassembly queue. Third consecutive segments are merged together (logically) and are skipped over in one jump for linear searches instead of each segment at a time. Further optimizations prototyped merge consecutive segments on the mbuf level instead of only logically. This is expected to give another significant performance gain. The new reassembly queue is tracking all holes in the queue and it may be beneficial to integrate this with the scratch pad of SACK in the future. Andrew Gallatin was able to get 3.7Gb/sec TCP performance on dual-2Gbit Myrinet cards with severe packet reordering (due to a firmware bug) with the new TCP reassembly code. See second link. _________________________________________________________________ The FreeBSD Dutch Documentation Team URL: http://www.evilcoder.org/content/section/6/39/ URL: http://www.FreeBSD.org/doc/nl/books/handbook/ URL: http://www.evilcoder.org/freebsd_html/ Contact: Remko Lodder The FreeBSD Dutch Documentation Project is a ongoing project to translate the documentation into the Dutch language. Currently we are mainly focused on the Handbook, which is progressing pretty well. However, lots need to be translated and checked before we have a 'complete' translation ready. So if you are willing to help out, please checkout our website and/or contact me. Open tasks: 1. Translating the Handbook 2. Checking the grammar of the Dutch Handbook 3. Translate the rest of the documentation _________________________________________________________________ TTCPv2: Transactional TCP version 2 URL: http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html Contact: Andre Oppermann The old TTCP according to RFC1644 was insecure, intrusive, complicated and has been removed from FreeBSD >= 5.3. Although the idea and semantics behind it are still sound and valid. The rewrite uses a much easier and more secure system with 24bit long client and server cookies which are transported in the TCP options. Client cookies protect against various kinds of blind injection attacks and can be used as well to generally secure TCP sessions (for BGP for example). Server cookies are only exchanged during the SYN-SYN/ACK phase and allow a server to ensure that it has communicated with this particular client before. The first connection is always performing a 3WHS and assigning a server cookie to a client. Subsequent connections can send the cookie back to the server and short-cut the 3WHS to SYN->OPEN on the server. TTCPv2 is fully configurable per-socket via the setsockopt() system call. Clients and server not capable of TTCPv2 remain fully compatible and just continue using the normal 3WHS without any delay or other complications. Work on implementing TTCPv2 is done to 90% and expected to be available by early February 2005. Writing the implementation specification (RFC Draft) has just started. _________________________________________________________________ Update of the Linux userland infrastructure Contact: Alexander Leidinger The default linux_base port port was changed from the RedHat 7 based emulators/linux_base to the RedHat 8 based emulators/linux_base-8 just in time for FreeBSD 4.11-Release because of a security problem in emulators/linux_base. In the conversion process several problems where fixed in some Linux ports. Both RedHat 7 and 8 are at their end of life, so expect an update to a more recent Linux distribution in the future. For QA reasons this update wasn't scheduled before FreeBSD 4.11-Release. _________________________________________________________________ Wiki with new software URL: http://wikitest.freebsd.org/ Contact: Josef El-Rayes After experiencing spam attacks on the old wiki-engine caused by non-existent authentification mechanism, I had to replace it with a more advanced software. Instead of usemod, we now run moinmoin. As a consequence it's no longer just a 'browse & edit', but you have to sign up and let someone who is already in the ACL group 'developers' add you to the group. So it is a 'developers-only' resource now. The old wiki is found at http://wiki2.daemon.li Open tasks: 1. Move content from old wiki to new one. _________________________________________________________________ Wireless Networking Support Contact: Sam Leffler The wireless networking layer was updated to support the 802.1x, WPA, and 802.11i security protocols, and the WME/WMM multi-media protocol. As part of this work extensible frameworks were added for cryptographic methods, authentication, and access control. Extensions are implemented as loadable kernel modules that hook into the net80211 layer. This mechanism is used, for example, to implement WEP, TKIP, and CCMP crypto protocols. The Atheros driver (ath) is currently the only driver that uses the full set of features. Adding support to other drivers is simple but waiting on volunteers. Ports of the wpa_supplicant and hostapd programs enable use of the new security protocols. The support for tracking stations in a bss (managed or adhoc) and stations found when scanning was overhauled. Multiple tables are now used, each with different management policies, reference counting is now done consistently, and inactivity processing is done more intelligently (e.g. associated stations are probed before removal). This is the first step towards proper roaming support and other advanced features. AP power save support was added. Associated stations may now operate in power save mode; frames sent to them will be buffered while they are sleeping and multicast traffic will be deferred until after the next beacon (per the 802.11 protocol). Power save support is required in a standards-compliant access point. Only the ath driver currently implements power save support. Work is actively going on to add Atheros' SuperG capabilities, WDS, and for multi-bss support (ssid and/or bssid) on a single device. Open tasks: 1. Drivers other than ath need updates to support the new security protocols 2. hostapd needs work to support the IAPP and 802.11i preauthentication protocols (these are simple conversion of existing Linux code) _________________________________________________________________ Copyright 1995-2005 the FreeBSD Project. All rights reserved. --------------030205060202020502090801-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 09:29:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E35FD16A4CE; Mon, 17 Jan 2005 09:29:01 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BED743D2D; Mon, 17 Jan 2005 09:29:01 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])420774F4FB; Mon, 17 Jan 2005 10:29:00 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05673-04-2; Mon, 17 Jan 2005 10:28:55 +0100 (CET) Received: from m2a2.dyndns.org (p508EFC70.dip.t-dialin.net [80.142.252.112]) 5ABDE4F4F0; Mon, 17 Jan 2005 10:28:54 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 7C23C7761B; Mon, 17 Jan 2005 10:28:54 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24806-05; Mon, 17 Jan 2005 10:28:53 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id A357E7761C; Mon, 17 Jan 2005 10:28:53 +0100 (CET) From: Matthias Andree To: freebsd-stable@freebsd.org, re@freebsd.org In-Reply-To: <20050117020739.GA2736@bobbi.cse.buffalo.edu> (Ken Smith's message of "Sun, 16 Jan 2005 21:07:39 -0500") References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> Date: Mon, 17 Jan 2005 10:28:53 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: kensmith@FreeBSD.org Subject: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 09:29:02 -0000 Ken Smith writes: > Announcement > ------------ > > The FreeBSD Release Engineering Team is pleased to announce the availability > of FreeBSD 4.11-RC3. This will be the last Release Candidate for the > FreeBSD 4.11 release unless a "show-stopper" problem is found while testing > RC3. critical: kern/60313 (silent data corruption on block devices) still open, may be FreeBSD 4 specific after the GEOM flurry in FreeBSD 5 and 6. serious: bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open bin/46866 (false data from getpwent, easy to fix) still open non-critical: kern/44260 (missing device in LINT configuration) is long-standing although trivial to fix (patch included) -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 10:28:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8A4916A4CE; Mon, 17 Jan 2005 10:28:37 +0000 (GMT) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CCE243D41; Mon, 17 Jan 2005 10:28:37 +0000 (GMT) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id 262AA347BA8; Mon, 17 Jan 2005 11:31:38 +0100 (CET) Date: Mon, 17 Jan 2005 11:31:38 +0100 From: Pawel Malachowski To: Matthias Andree Message-ID: <20050117103138.GA65688@shellma.zin.lublin.pl> References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2i cc: re@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 10:28:37 -0000 On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote: > critical: > kern/60313 (silent data corruption on block devices) > still open, may be FreeBSD 4 specific after the GEOM flurry > in FreeBSD 5 and 6. > > serious: > bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open > bin/46866 (false data from getpwent, easy to fix) still open > > non-critical: > kern/44260 (missing device in LINT configuration) > is long-standing although trivial to fix (patch included) And ipnat still not allowing traceroute(8) to pass over NAT ;-) (but working just fine with identical setup on previous releases). -- Pawe³ Ma³achowski From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 11:01:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9BF116A568; Mon, 17 Jan 2005 11:01:43 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AE0843D1F; Mon, 17 Jan 2005 11:01:42 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 318D830008EB; Mon, 17 Jan 2005 12:01:40 +0100 (CET) Message-ID: <41EB9B0C.90305@uni-mainz.de> Date: Mon, 17 Jan 2005 12:01:32 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050102 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-smp@freebsd.org, freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="------------000308020804060806030307" X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: FreeBSD 5.3-SMP/IRQ problems (again) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 11:01:44 -0000 This is a multi-part message in MIME format. --------------000308020804060806030307 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Dear Sirs. I reported very strange behaviours of FreeBSD 5.3 on a suspicous hardware platform of mine and now I would like to repeat this and hope someone can offer me some help. The reason why I repeat this suspected bug is because I do not really beliefe in a hardware fault due to some very strange behaviours of FreeBSD 5.3 on this box. So, hope you can follow off my non-engeneer-English. I utilize FreeBSD now for about 8 years on several plattforms especially SMP plattforms as they became available for FreeBSD. These boxes were uitilized for scientif-server-services and as high-performance-desktop plattforms as FreeBSD was prior to 5.X as solid as a rock (with the exeception of the start off of 4.0). Today I work with my private plattform at my lab because our computer center prefers Linux and I do not. So my hardware plattform seems to be a little bit 'ancient', but I think a lot of ours still use these boxes for high-duty tasks. All right, here the facts. Hardware: Mainboard ASUS CUR-DLS, two 1GHz PIII, 2x 512MB ECC/reg, 3x SCSI U160 harddrives, 1x Intel 1000/Pro 64Bit PCI server 1GBit server NIC, DVD-RW NEC ND3500AG/2.18 attached to ATA controler. Please keep in mind that this mobo has a built in PCI VGA controler. BIOS has been updated to the latest avaiable BIOS and after this hasn't fixed any problem I updated to the latest BETA BIOS available for this mobo. After POST I get a summary screen and realized, that VGA controler is not attached to an IRQ (and I suspect FreeBSD 5.3 having much troubles with IRQ routing, but I will report more later on). Firt thing I suspect courios: Booting machine in single user mode for maintainance-purposes remains box buggy! After a while of heavy screen output as done via compiling a kernel or building world or 'find'-ing all files of the file system or showing the contents of a file via more or similar freezes the box/the screen. I can then type 'return' and watch the blank lines filled in, but there is nothing more, the box seems to be stuck. Only rescue is a reboot. This happens to all variants of booting off single user mode, SMP enabled/disabled in the kernel, apic enabled/disabled, acpi enabled/disabled. The only way to get rid of this is to plugg in a separate PCI VGA card into another slot!! Then machine boots correctly into single user mode - but dies immediately when booting off multi-user mode anyway. With UP and multiuser mode, this box is with X11 GUI (Xorg or XFree86) very stable (using built in VGA). Next harsh problem is plugging in sound- or VGA-cards. It seems to be highly dependend on which slot such cards get plugged in. Different sound cards, different PCI VGA cards - same problem. FreeBSD 5.3 starts off and then freezes after init of the SCSI controller. The same thing happens when disabling both serial ports! FreeBSD dies after init of the SCSI controler. The mobo has two 64 Bit PCI slots and I use one of them for the Intel 1000/Pro GBit NIC. At the now choosen slot usage of a sound card is impossible (most near 64 bit slot to the CPUs). FreeBSD dies on every combination (w/ or w/o SCPI) I tried. SMP is impossible, w/ or w/o ACPI. FreeBSD 5.3 dies after a while of doing graphical output with the X11 GUI. I stressed the machine today with buildworld and build kernel and building openoffice 1.1.4 with console output and for 15 hours the box was stable as a rock. But switching to the X11 GUI doing some FireFox jobs (simply surfing the www) let the system die within minutes. Sometimes I can 'feel' when a crash is arising, the box is a kind of 'calm' and I can switch to the console sometimes catching the error message from the debugger, but sometimes not. This let me suspect the operating system 'waiting' for something related to the second CPU or similar and waiting forever. I'm not familiar with kernel programming and development, so my report seems to be a bit of 'strange', sorry for that. Another couriosity is booting the box in 'safe mode', I thing APIC is off, SMP is off and acpi is off. The box becomes slow, grapical output 'hangs' for seconds, freezes and defreezes and the system remains a kind of 'not useable'. The utilized mobo ASUS CUR-DLS uses the RCC LE 3.0 champion chipset. The IRQ problems (using of PCI cards in any PCI slot impossible) are similar to problems I had in the past with FreeBSD 5.0 on a TYAN Thunder 2500 box, were I wasn't able plugging the AMI RAID controler in any of the 6 64Bit slots. FreeBSD got stuck at the same place: when the built in SCSI controler (LSI logic 1010-33 or 894-33) get initialised. This makes me very courios. Now I build akernel with debug options and I will try to catch a kernel dump. maybe someone of yours is interested in that. I will attach mptabel -dmesg output, hope it is of your convenience. Oliver --------------000308020804060806030307 Content-Type: text/plain; name="mptable" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mptable" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f5270 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xe3 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f4e60 signature: 'PCMP' base table length: 276 version: 1.4 checksum: 0x12 OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 26 local APIC address: 0xfee00000 extended table length: 124 extended table checksum: 198 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 3 0x11 BSP, usable 6 8 6 0x387fbff 0 0x11 AP, usable 6 8 6 0x387fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 3 0x11 usable 0xfec01000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT conforms conforms 2 8 2 8 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 0 15:A 3 14 INT active-lo level 2 9 2 9 INT active-lo level 1 2:A 3 5 INT active-lo level 1 5:A 3 8 INT active-lo level 1 5:B 3 9 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 2 0 255 0 NMI active-hi edge 2 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- System Address Space bus ID: 0 address type: I/O address address base: 0x0 address range: 0x10000 -- System Address Space bus ID: 0 address type: memory address address base: 0x40000000 address range: 0xbebe0000 -- System Address Space bus ID: 0 address type: prefetch address address base: 0xfebe0000 address range: 0xe9420000 -- System Address Space bus ID: 0 address type: memory address address base: 0xe8000000 address range: 0x18000000 -- System Address Space bus ID: 0 address type: memory address address base: 0xa0000 address range: 0x20000 -- Bus Heirarchy bus ID: 2 bus info: 0x01 parent bus ID: 0 -- Compatibility Bus Address bus ID: 0 address modifier: add predefined range: 0x00000000 -- Compatibility Bus Address bus ID: 0 address modifier: add predefined range: 0x00000001 ------------------------------------------------------------------------------- dmesg output: Copyright (c) 1992-2005 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 5.3-STABLE #35: Sun Jan 16 17:27:11 UTC 2005 root@edda.physik.uni-mainz.de:/usr/obj/usr/src/sys/EDDA ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (1000.04-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x387fbff real memory = 1073721344 (1023 MB) avail memory = 1041166336 (992 MB) ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 7.0 (no driver attached) isab0: port 0xe800-0xe80f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xd400-0xd40f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xfc000000-0xfc000fff irq 9 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ugen0: OmniVision OV511+ Camera, rev 1.00/1.00, addr 2 pcib1: on acpi0 pci1: on pcib1 em0: port 0xd000-0xd03f mem 0xfb800000-0xfb81ffff irq 21 at device 2.0 on pci1 em0: Ethernet address: 00:07:e9:14:8f:7b em0: Speed:N/A Duplex:N/A sym0: <1010-33> port 0xb800-0xb8ff mem 0xfa800000-0xfa801fff,0xfb000000-0xfb0003ff irq 24 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0xb400-0xb4ff mem 0xf9800000-0xf9801fff,0xfa000000-0xfa0003ff irq 25 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 Timecounter "TSC" frequency 1000040215 Hz quality 800 Timecounters tick every 1.250 msec Fast IPsec: Initialized Security Association Processing. acd0: DVDR at ata0-master UDMA33 Waiting 3 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da2: 17429MB (35694904 512 byte sectors: 255H 63S/T 2221C) cd0 at ata0 bus 0 target 0 lun 0 cd0: <_NEC DVD_RW ND-3500AG 2.18> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present GEOM_LABEL: Label for provider da0s1d is ufs/var. GEOM_LABEL: Label for provider da0s1e is ufs/compat. GEOM_LABEL: Label for provider da0s1f is ufs/src. GEOM_LABEL: Label for provider da0s1g is ufs/usr. GEOM_LABEL: Label for provider da0s1h is ufs/local. GEOM_LABEL: Label for provider da1s1d is ufs/obj. GEOM_LABEL: Label for provider da1s1e is ufs/ports. GEOM_LABEL: Label for provider da1s1f is ufs/scratch. GEOM_LABEL: Label for provider da1s1g is ufs/data. Mounting root from ufs:/dev/da0s1a GEOM_LABEL: Label for provider da0s1e is ufs/compat. GEOM_LABEL: Label for provider da1s1g is ufs/data. GEOM_LABEL: Label for provider da1s1d is ufs/obj. GEOM_LABEL: Label for provider da0s1g is ufs/usr. GEOM_LABEL: Label for provider da1s1e is ufs/ports. GEOM_LABEL: Label for provider da1s1f is ufs/scratch. GEOM_LABEL: Label for provider da0s1h is ufs/local. GEOM_LABEL: Label for provider da0s1f is ufs/src. GEOM_LABEL: Label for provider da0s1d is ufs/var. pflog0: promiscuous mode enabled em0: Link is up 100 Mbps Full Duplex =============================================================================== --------------000308020804060806030307-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 14:16:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DABF16A4CE; Mon, 17 Jan 2005 14:16:43 +0000 (GMT) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id B571443D3F; Mon, 17 Jan 2005 14:16:42 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) j0HEGUCH091349; Mon, 17 Jan 2005 15:16:30 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id j0HEGUmq003897; Mon, 17 Jan 2005 15:16:30 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id j0HEGUf8003896; Mon, 17 Jan 2005 15:16:30 +0100 (CET) (envelope-from wb) Date: Mon, 17 Jan 2005 15:16:30 +0100 From: Wilko Bulte To: Pawel Malachowski Message-ID: <20050117141630.GA3877@freebie.xs4all.nl> References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> <20050117103138.GA65688@shellma.zin.lublin.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117103138.GA65688@shellma.zin.lublin.pl> X-OS: FreeBSD 4.11-RC2 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-stable@freebsd.org cc: Matthias Andree cc: re@freebsd.org Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 14:16:43 -0000 On Mon, Jan 17, 2005 at 11:31:38AM +0100, Pawel Malachowski wrote.. > On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote: > > > critical: > > kern/60313 (silent data corruption on block devices) > > still open, may be FreeBSD 4 specific after the GEOM flurry > > in FreeBSD 5 and 6. > > > > serious: > > bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open > > bin/46866 (false data from getpwent, easy to fix) still open > > > > non-critical: > > kern/44260 (missing device in LINT configuration) > > is long-standing although trivial to fix (patch included) > > And ipnat still not allowing traceroute(8) to pass over NAT ;-) > (but working just fine with identical setup on previous releases). Why is it that people always wait til at least RC3 to scream murder about their favorite PR? /me is just wondering... W/ -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 14:53:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502B316A4CE for ; Mon, 17 Jan 2005 14:53:25 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6740E43D31 for ; Mon, 17 Jan 2005 14:53:22 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0HF5o5B023590; Mon, 17 Jan 2005 16:05:50 +0100 (MET) Message-ID: <41EBD155.7040309@fer.hr> Date: Mon, 17 Jan 2005 15:53:09 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock , stable@freebsd.org References: <41E9B02B.5070602@fer.hr> <200501161541.19290.michaelnottebrock@gmx.net> In-Reply-To: <200501161541.19290.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 14:53:25 -0000 Michael Nottebrock wrote: > On Sunday, 16. January 2005 01:07, Ivan Voras wrote: > >>What could be the reasons for "su root" to not work? >> >>I have a user that's in wheel group. Logging in as root works on the >>console, but su-ing from the user just writes 'Sorry', like the >>password's wrong. There are no clues in log files. > > > Make sure /usr/sbin/su is suid root (and /usr isn't mounted nosuid). Bingo! It's stupid of me not to have checked that, but this is a very good candidate for more information/verbosity - failure mode was just like password/credentials were invalid. I installed the computer from the FreeSBIE live CD, as it already includes a bunch of desktop & multimedia programs I use, and during installation it seems that suid bits were not replicated! Thanks for the help! From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 14:57:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2CF916A4CE for ; Mon, 17 Jan 2005 14:57:05 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FB8C43D2F for ; Mon, 17 Jan 2005 14:57:05 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])9574F3F748; Mon, 17 Jan 2005 15:57:04 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25397-02-6; Mon, 17 Jan 2005 15:57:02 +0100 (CET) Received: from m2a2.dyndns.org (p548547B1.dip.t-dialin.net [84.133.71.177]) A36873BCE8; Mon, 17 Jan 2005 15:57:01 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id AB1FD77931; Mon, 17 Jan 2005 15:56:59 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20278-01-4; Mon, 17 Jan 2005 15:56:58 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id DF04F7794B; Mon, 17 Jan 2005 15:56:58 +0100 (CET) Date: Mon, 17 Jan 2005 15:56:58 +0100 From: Matthias Andree To: Wilko Bulte Message-ID: <20050117145658.GA18774@merlin.emma.line.org> Mail-Followup-To: Wilko Bulte , freebsd-stable@freebsd.org References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> <20050117103138.GA65688@shellma.zin.lublin.pl> <20050117141630.GA3877@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117141630.GA3877@freebie.xs4all.nl> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: freebsd-stable@freebsd.org Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 14:57:05 -0000 [Cutting down Cc: list.] On Mon, 17 Jan 2005, Wilko Bulte wrote: > Why is it that people always wait til at least RC3 to scream murder about > their favorite PR? I for one have regularly reported these PR numbers, last time after 4.11-RC1. I haven't re-reported them against -RC2 because I was too busy to do that at the time, and when I had the time, -RC3 was already out. So... are we supposed to flood developers with reminders weekly? Most certainly not, we still want them to be able to do actual work. And it's certainly not my fault that bugs reported against 4.7 or so with patches attached remain unfixed in 4.11-RC3 when a reminder has been sent after 4.11-RC1... What this means for code quality is left to the reader's appreciation. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 15:14:14 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B41016A4CE; Mon, 17 Jan 2005 15:14:14 +0000 (GMT) Received: from news.hunter.com (news.hunter.com [128.242.141.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2294743D54; Mon, 17 Jan 2005 15:14:12 +0000 (GMT) (envelope-from KHamilton@Hunter.Com) Received: from hunter.com (mailbox.Hunter.com [10.2.1.21]) by news.hunter.com (8.13.1/8.12.9) with ESMTP id j0HEswnB033358; Mon, 17 Jan 2005 09:13:24 -0600 (CST) (envelope-from KHamilton@Hunter.Com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Jan 2005 08:59:58 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Qt33 Build Problem Thread-Index: AcT8pTZ+8X/wq1nwRYCU4ptQs84qZA== From: "Hamilton, Kent" To: , X-Hunter-Relay-Host: mailbox.Hunter.com (10.2.1.21) X-IsSpam: No (Score: -4.9) X-Spam-Score: -4.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.44 Subject: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 15:14:14 -0000 I have two systems that I'm having problems building qt33 on. Both are RELENG_5_3 with perl-threaded-5.8.5 on dual processor Dell PowerEdge systems. =20 I'm getting the same error building on both systems. I'm trying to build with all the config options turned on (CUPS, NAS, OpenGL, XFt). The uic that gets built dies with a thread error so I can't finish the build.=20 =20 The error is: Fatal error 'Spinlock called when not threaded.' at line 83 in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno =3D 0) Abort (code dumped) kernel: pid 14119 (uic), uid 0: existed on signal 6 (core dumped) =20 I'd really appreciate any suggestions.=20 I don't subscribe to freebsd-ports so if you are answering on that list please add me to the message. Thanks, Kent From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 15:30:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D47016A4CE for ; Mon, 17 Jan 2005 15:30:39 +0000 (GMT) Received: from pttx.ptt.cc (patty.csie.ntu.edu.tw [140.112.90.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBAE443D1F for ; Mon, 17 Jan 2005 15:30:38 +0000 (GMT) (envelope-from in@pttx.ptt.cc) Received: by pttx.ptt.cc (Postfix, from userid 1001) id 9ACE63D4433; Mon, 17 Jan 2005 23:30:39 +0800 (CST) Date: Mon, 17 Jan 2005 23:30:39 +0800 From: in2 To: freebsd-stable@freebsd.org Message-ID: <20050117153039.GA54135@in2home.org> References: <20050117032925.GA29922@in2home.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117032925.GA29922@in2home.org> User-Agent: Mutt/1.5.6i Subject: Re: panic: PAE with 16GB ram X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 15:30:39 -0000 On Mon, Jan 17, 2005 at 11:29:25AM +0800, in2 wrote: > Hi, > I use Tyan S2882 with dual Opteron and FreeBSD 4.10-RELEASE with > PAE support. it works fine with 8GB and 12GB ram, but panics with > 16GB (with the same kernel) : the kernel panics just after booting: Console: serial port BIOS drive C: is disk0 BIOS 639kB/4127744kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (root@, Mon Jan 10 12:08:32 CST 2005) Loading /boot/defaults/loader.conf /kernel text=0x19be7d data=0x23080+0x1d670 syms=[0x4+0x27350+0x4+0x2dc3e] / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-2005 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. Fatal trap 12: page fault while in kernel mode mp_lock = 00000009; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x69bc8000 fault code = supervisor write, page not present instruction pointer = 0x8:0x6a259d26 stack pointer = 0x10:0x6a3b3f44 frame pointer = 0x10:0x6a3b3f5c 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 = Idle interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000009; cpuid = 0; lapic.id = 00000000 Uptime: 0s and here is my /boot/loader.conf: userconfig_script_load="YES" console=comconsole kern.maxproc=30000 I tried to increase KVA_PAGES from 1200 to 1400 but it did not work. is there any suggestion? thanks for your help :) From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 15:34:10 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE79F16A4CE; Mon, 17 Jan 2005 15:34:10 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96D6F43D1D; Mon, 17 Jan 2005 15:34:10 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1CqYsv-000Piy-1m; Mon, 17 Jan 2005 16:33:41 +0100 Date: Mon, 17 Jan 2005 16:33:41 +0100 From: Kirill Ponomarew To: "Hamilton, Kent" Message-ID: <20050117153341.GO93155@voodoo.oberon.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 15:34:11 -0000 On Mon, Jan 17, 2005 at 08:59:58AM -0600, Hamilton, Kent wrote: > I have two systems that I'm having problems building qt33 on. Both are > RELENG_5_3 with perl-threaded-5.8.5 on dual processor Dell PowerEdge > systems. > > I'm getting the same error building on both systems. I'm trying to build > with all the config options turned on (CUPS, NAS, OpenGL, XFt). The uic > that gets built dies with a thread error so I can't finish the build. > > The error is: > Fatal error 'Spinlock called when not threaded.' at line 83 in file > /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0) > Abort (code dumped) > kernel: pid 14119 (uic), uid 0: existed on signal 6 (core dumped) > > I'd really appreciate any suggestions. > > I don't subscribe to freebsd-ports so if you are answering on that list > please add me to the message. You can rebuild all your ports, or use libmap.conf(5), or even better, search the archives to understand this problem. We should really put it into FAQ, if it's not there. -Kirill From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 16:52:50 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC5916A4CE; Mon, 17 Jan 2005 16:52:50 +0000 (GMT) Received: from mail.foolishgames.com (mail.foolishgames.com [216.55.178.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id C07A443D3F; Mon, 17 Jan 2005 16:52:49 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [192.168.0.49] (24.247.120.6.kzo.mi.chartermi.net [24.247.120.6]) (authenticated bits=0)j0HHuKkh008764 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 17 Jan 2005 09:56:21 -0800 (PST) (envelope-from luke@foolishgames.com) X-Authentication-Warning: mail.foolishgames.com: Host 24.247.120.6.kzo.mi.chartermi.net [24.247.120.6] claimed to be [192.168.0.49] Message-Id: <71F0D3ED-689E-11D9-BF7D-000A95EFF4CA@foolishgames.com> X-Habeas-Swe-6: email in exchange for a license for this Habeas X-Habeas-Swe-3: like Habeas SWE (tm) Date: Mon, 17 Jan 2005 10:42:50 -0500 X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this From: Lucas Holt X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-Swe-2: brightly anticipated In-Reply-To: <41EB9B0C.90305@uni-mainz.de> References: <41EB9B0C.90305@uni-mainz.de> To: "O. Hartmann" X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant Mime-Version: 1.0 (Apple Message framework v619) X-Habeas-Swe-4: Copyright 2002 Habeas (tm) Content-Type: text/plain; charset=US-ASCII; format=flowed X-Habeas-Swe-1: winter into spring Content-Transfer-Encoding: 7bit X-Habeas-Swe-9: mark in spam to . X-Mailer: Apple Mail (2.619) cc: freebsd-smp@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 5.3-SMP/IRQ problems (again) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 16:52:50 -0000 On Jan 17, 2005, at 6:01 AM, O. Hartmann wrote: > Dear Sirs. > > I reported very strange behaviours of FreeBSD 5.3 on a suspicous > hardware platform of mine and now I would like to repeat this and hope > someone can offer me some help. The reason why I repeat this suspected > bug is because I do not really beliefe in a hardware fault due to some > very strange behaviours of FreeBSD 5.3 on this box. > After reading your post, I find it rather odd that you do not suspect hardware problems at least with compatibility with your hardware. I have a Dell Precision 650 dual xeon 2.0 ghz system with an onboard version of your Intel NIC. The network driver has known issues and takes a very long time to negotiate the speed at which it operates. Most of the time my system is almost completely booted before the NIC interface is up. Aside from that issue, my system behaves normally and seems very stable. I am using FreeBSD 5.3 Release P5. I've had problems with several asus motherboards in the past. I used to love them, but after I built a 733mhz P3 system for a friend, i soon realized that their bioses were not good. I believe the decline occured when they switched to "soft bios" instead of jumpers. (I miss jumpers!) Seriously, the system had problems with video and sound cards in WINDOWS depending on the slot they were placed in. Its the same problem you describe only in windows from a mobo thats probably from about the same time period. The 733 was one of the lowest chips that would go in the board at the time. In addition, i've had problems with FreeBSD 5.2.1 with patchlevel greater than I think 4 but below 5.3 release on an asus nforce2 AMD Athelon XP 2000+ based system. My point is that not all freebsd SMP systems have problems, so its not a global fault in the OS as your post may suggest. (note: i have hyperthreading disabled on my system) Also, ASUS boards are known to have problems. I asked about my reboot problem on freebsd-questions at the time and I was told many horror stories about asus boards and non windows/linux oses. Finally, I'd like to ask why you are running stable? Did someone suggest that you upgrade to stable to try to resolve an issue? Stable occasionally has new features or changes that are not tested thoroughly. It might be more reliable with 5.3 Release P(whatever). I'll close with a summary of the hardware in my system which is known to work in 5.3 release. Dual Xeon 2.0 ghz (dual cpu working great, no HTT) 1 gig ecc memory Intel gigabit nic onboard using em0 driver (slow to negotiate speed, fine afterword unless i'm stress testing) Creative Sound Blaster Audigy Gamer ATI AIW Radeon 9600 XT (2d acceleration only since dri isn't supported on this one) AGP 8x ATA100 IDE disks using onboard IDE controller DVD reader, cd burner firewire 400, USB 2/1.1 ports I have the onboard sound, onboard LSI scsi ultra 320, serial ports, and paralell port disabled to make windows happy. :) Also, I have gentoo installed and quite frankly its very slow! Its running on the 2.6.9 linux kernel w/ smp enabled. If only I didn't need it for my CS class, i'd be running 6 current too :) (i'm not subscribed to the stable mailing list, but am on SMP) Lucas Holt Luke@FoolishGames.com ________________________________________________________ FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) FoolishGames.net (Enemy Territory IoM site) From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 17:16:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6464E16A4CE for ; Mon, 17 Jan 2005 17:16:39 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3A3043D48 for ; Mon, 17 Jan 2005 17:16:38 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.43 (FreeBSD)) id 1CqaUW-0001AW-Vn for stable@freebsd.org; Mon, 17 Jan 2005 17:16:37 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.43 (FreeBSD)) id 1CqaUW-000IcA-NH for stable@freebsd.org; Mon, 17 Jan 2005 17:16:36 +0000 To: stable@freebsd.org Message-Id: From: Pete French Date: Mon, 17 Jan 2005 17:16:36 +0000 Subject: 4.11 + Xorg mga/dri problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 17:16:39 -0000 Just giving 4.11 a whirl. Thought I would try and get dri working with my mga card. It's never worked in the past, so I am not too worried that it doesnt work now. But it's getting closer to woorking, so I thought I would ask to see if anyone had any good ideas. I have agp and mgadrm compiled into the kernel. dmesg output at boot is: drm0: mem 0xfd000000-0xfd7fffff,0xfdefc000-0xfdefffff,0xf8000000-0xf9ffffff irq 14 at device 0.0 on pci6 info: [drm] AGP at 0xf0000000 32MB info: [drm] Initialized mga 3.1.0 20021029 on minor 0 drm1: mem 0xfc800000-0xfcffffff,0xfdef8000-0xfdefbfff,0xf6000000-0xf7ffffff irq 14 at device 4.0 on pci6 info: [drm] AGP at 0xf0000000 32MB info: [drm] Initialized mga 3.1.0 20021029 on minor 1 drm2: mem 0xfc000000-0xfc7fffff,0xfdef4000-0xfdef7fff,0xf4000000-0xf5ffffff irq 14 at device 8.0 on pci6 info: [drm] AGP at 0xf0000000 32MB info: [drm] Initialized mga 3.1.0 20021029 on minor 2 drm3: mem 0xfb800000-0xfbffffff,0xfdef0000-0xfdef3fff,0xf2000000-0xf3ffffff irq 14 at device 12.0 on pci6 info: [drm] AGP at 0xf0000000 32MB info: [drm] Initialized mga 3.1.0 20021029 on minor 3 So that looks very good. It was not doing this before, so I thought this might enable me to get it working with Xorg (6.8.1_2 - cvsup this morning). But I I include the "dri" options in my xorg.conf file, I get a black screen which a while 'X' cursor which moves with the mouse, but noithing else. X cannot be killed either and so I have to resort to rebooting the machine! So near and yet so far... any suggestions ? -pcf. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 17:28:16 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45CA316A4CE for ; Mon, 17 Jan 2005 17:28:16 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7CB643D49 for ; Mon, 17 Jan 2005 17:28:15 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0HHWNbG020763; Mon, 17 Jan 2005 10:32:23 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EBF5AD.2040403@freebsd.org> Date: Mon, 17 Jan 2005 10:28:13 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: in2 References: <20050117032925.GA29922@in2home.org> <20050117153039.GA54135@in2home.org> In-Reply-To: <20050117153039.GA54135@in2home.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-stable@freebsd.org Subject: Re: panic: PAE with 16GB ram X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 17:28:16 -0000 in2 wrote: > On Mon, Jan 17, 2005 at 11:29:25AM +0800, in2 wrote: > >>Hi, >>I use Tyan S2882 with dual Opteron and FreeBSD 4.10-RELEASE with >>PAE support. it works fine with 8GB and 12GB ram, but panics with >>16GB (with the same kernel) : > > the kernel panics just after booting: > This is a known deficiency in the low-level startup code. Try editing /sys/i386/include/pmap.h and doubling or quadroupling the value of NKPT. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 17:38:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C68316A4CE for ; Mon, 17 Jan 2005 17:38:04 +0000 (GMT) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDFBA43D2D for ; Mon, 17 Jan 2005 17:38:03 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) j0HHc2ri060202; Mon, 17 Jan 2005 18:38:02 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 20781616B; Mon, 17 Jan 2005 18:39:08 +0100 (CET) Date: Mon, 17 Jan 2005 18:39:08 +0100 From: Roland Smith To: freebsd-stable@freebsd.org Message-ID: <20050117173908.GA57956@slackbox.xs4all.nl> Mail-Followup-To: freebsd-stable@freebsd.org, Pete French References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner cc: Pete French Subject: Re: 4.11 + Xorg mga/dri problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 17:38:04 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 05:16:36PM +0000, Pete French wrote: > Just giving 4.11 a whirl. Thought I would try and get dri working > with my mga card. It's never worked in the past, so I am not too > worried that it doesnt work now. What hardware are you on? The radeon driver had 64-bit issues on amd64. Maybe Matrox has a similar problem? > drm3: mem 0xfb800000-0xfbffffff,0xfdef0000-0xfde= f3fff,0xf2000000-0xf3ffffff irq 14 at device 12.0 on pci6 > info: [drm] AGP at 0xf0000000 32MB > info: [drm] Initialized mga 3.1.0 20021029 on minor 3 > > So that looks very good. It was not doing this before, so I thought > this might enable me to get it working with Xorg (6.8.1_2 - cvsup this > morning). The kernel side looks good. =20 > But I I include the "dri" options in my xorg.conf file, I get a black > screen which a while 'X' cursor which moves with the mouse, but noithing > else. X cannot be killed either and so I have to resort to rebooting > the machine! >=20 > So near and yet so far... any suggestions ? Not only do you have to enable the "dri" option, you should also have a DRI section, like: Section "DRI" Mode 0666 EndSection in your xorg.conf. Do the /dev/dri/card* devices actually exist? Have a look at /var/log/Xorg.0.log, and see what it says about dri/drm. Look for things like "drmOpenDevice", "[drm]" and "[dri]", and for the string "direct rendering". If it says "direct rendering enabled", then dri works. Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \ Respect for open standards --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6/g8EnfvsMMhpyURAg4GAJ9xH6/DVJu741otzCns8M+zTpOTAACfcnGi fUJzOod0ysjSp5t6phvePpA= =lBK5 -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 17:51:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9F6B16A4CE for ; Mon, 17 Jan 2005 17:51:56 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B48F43D3F for ; Mon, 17 Jan 2005 17:51:56 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cqb2h-0002OW-Ll; Mon, 17 Jan 2005 17:51:55 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.43 (FreeBSD)) id 1Cqb2h-00005T-GV; Mon, 17 Jan 2005 17:51:55 +0000 To: freebsd-stable@freebsd.org, rsmith@xs4all.nl In-Reply-To: <20050117173908.GA57956@slackbox.xs4all.nl> Message-Id: From: Pete French Date: Mon, 17 Jan 2005 17:51:55 +0000 cc: petefrench@ticketswitch.com Subject: Re: 4.11 + Xorg mga/dri problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 17:51:57 -0000 > What hardware are you on? The radeon driver had 64-bit issues on > amd64. Maybe Matrox has a similar problem? It's just straight i386 (aP4) - though I am interested in what you say above, as I also have an amd64 machine running 5-STABLE with a Radeon which also will not do drm for love nor money! Got any references for that ? > Not only do you have to enable the "dri" option, you should also have a > DRI section, like: Well, I didnt have, but I added one in. Same result - hang and reboot required. > Do the /dev/dri/card* devices actually exist? Yup. > Have a look at /var/log/Xorg.0.log, and see what it says about > dri/drm. Look for things like "drmOpenDevice", "[drm]" and "[dri]", and > for the string "direct rendering". If it says "direct rendering > enabled", then dri works. There are no references to either dri or drm in the logfiles. Will the logfile actually be written if the X server doesnt startup properly though ? Thanks for the advice. -pcf. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 18:51:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB8D616A4D0 for ; Mon, 17 Jan 2005 18:51:44 +0000 (GMT) Received: from smartmx-05.inode.at (smartmx-05.inode.at [213.229.60.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D94E43D49 for ; Mon, 17 Jan 2005 18:51:44 +0000 (GMT) (envelope-from mailinglist@petermair.at) Received: from [81.223.147.232] (port=49713 helo=[192.168.0.2]) by smartmx-05.inode.at with esmtp (Exim 4.34) id 1CqbyZ-0002qS-IG for freebsd-stable@freebsd.org; Mon, 17 Jan 2005 19:51:43 +0100 Message-ID: <41EC099E.5040001@petermair.at> Date: Mon, 17 Jan 2005 19:53:18 +0100 From: Patrick Petermair User-Agent: Mozilla Thunderbird 1.0 (X11/20041230) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41E7BE4B.6060103@petermair.at> In-Reply-To: <41E7BE4B.6060103@petermair.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: keymap and rc.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mailinglist@petermair.at List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:51:45 -0000 For the archive: I noticed that everything went fine with my keymap as soon as I booted without my USB mouse connected. I also got the "Configuring syscons..." messages during boot (which I didn't get before). I then plugged my USB mouse in another USB port and now everything works like expected. Nevertheless...strange how an USB port can prevent syscons from running.. Patrick From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 19:30:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F399D16A4CE for ; Mon, 17 Jan 2005 19:30:55 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D93D43D2F for ; Mon, 17 Jan 2005 19:30:55 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])6D2B94DB5B for ; Mon, 17 Jan 2005 20:30:54 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10763-01 for ; Mon, 17 Jan 2005 20:30:49 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFBEDD.dip.t-dialin.net [217.255.190.221]) 81861287C8 for ; Mon, 17 Jan 2005 20:30:46 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id B034979B09 for ; Mon, 17 Jan 2005 20:30:44 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16678-01-2 for ; Mon, 17 Jan 2005 20:30:43 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id CD27879B0B; Mon, 17 Jan 2005 20:30:43 +0100 (CET) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: (Matthias Andree's message of "Mon, 17 Jan 2005 10:28:53 +0100") References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> Date: Mon, 17 Jan 2005 20:30:42 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 19:30:56 -0000 My open 4.11* bug list is now down to: > critical: > kern/60313 (silent data corruption on block devices) > still open, may be FreeBSD 4 specific after the GEOM flurry > in FreeBSD 5 and 6. > > serious: > bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open > bin/46866 (false data from getpwent, easy to fix) still open -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 19:38:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4016216A4CE for ; Mon, 17 Jan 2005 19:38:52 +0000 (GMT) Received: from wrzx28.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61E5B43D3F for ; Mon, 17 Jan 2005 19:38:49 +0000 (GMT) (envelope-from q@uni.de) Received: from wrzx34.rz.uni-wuerzburg.de (wrzx34.rz.uni-wuerzburg.de [132.187.3.34]) by wrzx28.rz.uni-wuerzburg.de (Postfix) with ESMTP id 84A68D643F; Mon, 17 Jan 2005 20:38:48 +0100 (CET) Received: from virusscan (localhost [127.0.0.1]) by wrzx34.rz.uni-wuerzburg.de (Postfix) with ESMTP id 629DA5972C; Mon, 17 Jan 2005 20:38:48 +0100 (CET) Received: from wrzx28.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by wrzx34.rz.uni-wuerzburg.de (Postfix) with ESMTP id 2E8C458F43; Mon, 17 Jan 2005 20:38:48 +0100 (CET) Received: from coyote.q.local (wwsx14.win-screen.uni-wuerzburg.de [132.187.253.14]) by wrzx28.rz.uni-wuerzburg.de (Postfix) with ESMTP id BF9DAD643F; Mon, 17 Jan 2005 20:38:47 +0100 (CET) Received: from roadrunner.q.local (roadrunner.q.local [192.168.0.148]) by coyote.q.local (8.13.1/8.13.1) with ESMTP id j0HJclXT098275; Mon, 17 Jan 2005 20:38:47 +0100 (CET) (envelope-from q@uni.de) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.1/8.13.1) with ESMTP id j0HJclmb028231; Mon, 17 Jan 2005 20:38:47 +0100 (CET) (envelope-from q@uni.de) Received: (from q@localhost) by roadrunner.q.local (8.13.1/8.13.1/Submit) id j0HJci8O028230; Mon, 17 Jan 2005 20:38:44 +0100 (CET) (envelope-from q@uni.de) Date: Mon, 17 Jan 2005 20:38:44 +0100 From: Ulrich Spoerlein To: Mike Tancsa Message-ID: <20050117193844.GB1110@galgenberg.net> Mail-Followup-To: Mike Tancsa , freebsd-stable@freebsd.org References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p2kqVDKq5asng8Dg" Content-Disposition: inline In-Reply-To: <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new (Rechenzentrum Universitaet Wuerzburg) cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 19:38:52 -0000 --p2kqVDKq5asng8Dg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 13.01.2005 at 19:38:27 -0500, Mike Tancsa wrote: > >I'm using -Os -pipe ever since installing 5.x after the gcc update. > >Haven't encountered any problem so far.. > There are some differences between O2 and Os according to the man=20 > page. Are you using that on your kernel and for buildworld ? Both, that is everything. Kernel, World, Ports. (Guess I'm lucky) > I let the box run over night building world 8 times with -j2 through -j5= =20 > and all worked just fine. Ok, that should put hardware out of the question. Sorry, no more ideas, besides getting rid of CPUTYPE as that is know to cause problems. btw, any status update on ICC + Kernel/World? Ulrich Spoerlein --=20 PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand? --p2kqVDKq5asng8Dg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7BREmArGtfDbn0QRAqOAAJ9T4WtcHAIvBHt9sGM1W09NTp9zEQCfUhzf RvZV7cEpQLFVaJ25clmrfAk= =hDqG -----END PGP SIGNATURE----- --p2kqVDKq5asng8Dg-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 19:50:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F7CD16A4CE for ; Mon, 17 Jan 2005 19:50:02 +0000 (GMT) Received: from seed.net.tw (sn16.seed.net.tw [139.175.54.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D7BF43D41 for ; Mon, 17 Jan 2005 19:50:02 +0000 (GMT) (envelope-from guitar@jazzcafe.no-ip.org) Received: from [221.169.112.158] (port=57036 helo=[192.168.0.222]) by seed.net.tw with esmtp (Seednet 4.23:1) id 1Cqcsy-000DHg-F8; Tue, 18 Jan 2005 03:50:00 +0800 Date: Tue, 18 Jan 2005 03:50:11 +0800 From: CryBaby To: CryBaby In-Reply-To: <20050116035709.AFCE.GUITAR@jazzcafe.no-ip.org> References: <20050116035709.AFCE.GUITAR@jazzcafe.no-ip.org> Message-Id: <20050118034550.E879.GUITAR@jazzcafe.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12.01 [en] cc: freebsd-stable@freebsd.org Subject: Re: SSH Protocol mismatch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 19:50:02 -0000 I already fixed it. % less /var/log/auth.log Jan 18 01:57:55 jazzcafe login: _pam_init_handlers: no default config /etc/pam.d/other Jan 18 01:57:55 jazzcafe login: error reading PAM configuration file % man pam ... files located in the /etc/pam.d/ directory. The presence of this directory will cause PAM to ignore /etc/pam.conf. ... % rmdir /etc/pam.d % END --- CryBaby From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 19:59:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B78B16A4CF for ; Mon, 17 Jan 2005 19:59:51 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB0543D48 for ; Mon, 17 Jan 2005 19:59:50 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0HJxiZ5014456; Mon, 17 Jan 2005 14:59:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0HJxeMH014451; Mon, 17 Jan 2005 19:59:44 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 17 Jan 2005 19:59:39 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ivan Voras In-Reply-To: <41EBD155.7040309@fer.hr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 19:59:51 -0000 On Mon, 17 Jan 2005, Ivan Voras wrote: > >>I have a user that's in wheel group. Logging in as root works on the > >>console, but su-ing from the user just writes 'Sorry', like the > >>password's wrong. There are no clues in log files. > > > > Make sure /usr/sbin/su is suid root (and /usr isn't mounted nosuid). > > It's stupid of me not to have checked that, but this is a very good > candidate for more information/verbosity - failure mode was just like > password/credentials were invalid. I've modified the su(1) source in HEAD to print a message if su(1) is executed without an effective uid of 0 (i.e., as root, or setuid as another user). Hopefully this error message will be more suggestive than "sorry": paprika:~/freebsd/commit/src/usr.bin/su> ./su su: not running setuid Assuming I didn't shoot any feet, I'll MFC this to RELENG_5 in a couple of weeks. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 20:19:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C0F416A4CE for ; Mon, 17 Jan 2005 20:19:09 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DD1543D2D for ; Mon, 17 Jan 2005 20:19:08 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (fybura@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id j0HKJ5Ta033790 for ; Mon, 17 Jan 2005 21:19:06 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id j0HKJ5gv033789; Mon, 17 Jan 2005 21:19:05 +0100 (CET) (envelope-from olli) Date: Mon, 17 Jan 2005 21:19:05 +0100 (CET) Message-Id: <200501172019.j0HKJ5gv033789@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20050115152249.GA51734@frontfree.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: backporting tail from HEAD to RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 20:19:09 -0000 Xin LI wrote: > On Thu, Jan 13, 2005 at 01:01:44PM -0600, Doug Poland wrote: > > Cool, I currently get this functionality from misc/xtail. xtail was on > > my short list of "must-have" ports. > > Would you please share the list with us? I think it would be helpful > if we know the needs :-) I'm surprised that nobody else replied. This is a list of small non-X11 ports that I install on most machines (even non-FreeBSD if applicable). This list is certainly not complete, and everyone probably has his/her own favourite tools. - cpdup (great to copy/sync directory trees) - cvsup-without-gui (cannot use FreeBSD without it) - elinks (nice text web browser, better than lynx) - fping (useful to ping multiple hosts/nets at once) - joe (my fav. editor, though I can cope with vi, too) - logsurfer (useful tool to watch your logs) - lsof (can't live without it) - lynx-ssl (sometimes useful) - netcat (well-known) - nmap (well-known) - omi (I use this one to mirror stuff via FTP) - par (I use this often for mail / news) - screen (can't live without it) - strace (better than ktrace and truss, IMO) - super (better than sudo, in my opinion) - trafshow (very nice tool to watch network activity) - zsh (my favourite shell, very powerful) Of course, lots of people will probably have different opinions about some of those tools. But that's one of the big advantages of FreeBSD and its ports collection: You have enough things to chose from, so go and try them to find the one which suits you best. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Python is executable pseudocode. Perl is executable line noise. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 20:23:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 398CC16A4CE for ; Mon, 17 Jan 2005 20:23:37 +0000 (GMT) Received: from nuumen.pair.com (nuumen.pair.com [209.68.1.119]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B61443D53 for ; Mon, 17 Jan 2005 20:23:36 +0000 (GMT) (envelope-from thuppi@nuumen.pair.com) Received: (qmail 43023 invoked by uid 55300); 17 Jan 2005 20:23:36 -0000 Date: Mon, 17 Jan 2005 15:23:36 -0500 (EST) From: Tom Huppi X-X-Sender: thuppi@nuumen.pair.com To: Kirill Ponomarew In-Reply-To: <20050117153341.GO93155@voodoo.oberon.net> Message-ID: References: <20050117153341.GO93155@voodoo.oberon.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org cc: "Hamilton, Kent" Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 20:23:37 -0000 On Mon, 17 Jan 2005, Kirill Ponomarew wrote: > On Mon, Jan 17, 2005 at 08:59:58AM -0600, Hamilton, Kent wrote: > > I have two systems that I'm having problems building qt33 on. Both are > > RELENG_5_3 with perl-threaded-5.8.5 on dual processor Dell PowerEdge > > systems. > > > > I'm getting the same error building on both systems. I'm trying to build > > with all the config options turned on (CUPS, NAS, OpenGL, XFt). The uic > > that gets built dies with a thread error so I can't finish the build. > > > > The error is: > > Fatal error 'Spinlock called when not threaded.' at line 83 in file > > /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0) > > Abort (code dumped) > > kernel: pid 14119 (uic), uid 0: existed on signal 6 (core dumped) > > > > I'd really appreciate any suggestions. I believe that it was this that induced me to consider updating XFree86 -> xorg to be an intregal part of a general upgrade from 5.1 -> 5.3. Basically, any time a library references 'libc_r.so*', you can get such a problem. My similar problems went away after rebuilding whatever libraries contained that reference. BTW, 'ldd', and 'pkg_which' are helpful commands to track down offending libraries and their source. > > I don't subscribe to freebsd-ports so if you are answering on that list > > please add me to the message. > > You can rebuild all your ports, or use libmap.conf(5), or even > better, search the archives to understand this problem. > > We should really put it into FAQ, if it's not there. There is a reference to it in the 5.3 Errata (at least): http://www.freebsd.org/releases/5.3R/errata.html ...but I would have had a bit more trouble finding it had I not known to look for the string 'libc_r'. I worked at re-building Qt33 for quite some time, but 'libqt-mt.so' still retains a reference to 'libc_r'. If there are any common reasons why this may be, I'de be interested to know of them. I got rid of all other references (except one other library associated also with Qt33), but couldn't nuke that one so I resorted to the 'libmap.conf' hack which I would have preferred not to do. Thanks, - Tom From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 20:25:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAD6616A4CE for ; Mon, 17 Jan 2005 20:25:11 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DCD543D45 for ; Mon, 17 Jan 2005 20:25:09 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 4A2796A for ; Mon, 17 Jan 2005 22:01:55 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Mon, 17 Jan 2005 20:24:33 +0000 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501172024.33667.imobachgs@banot.net> Subject: System crashes... what now? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 20:25:11 -0000 Hi all, I'm a newbie in the FreeBSD thing, and I'm having some problems that I'd li= ke=20 to track down as far as possible. In four days using FreeBSD, my machine ha= s=20 crashed two times, ugh! a) first time, with 5.3-RELEASE. Nothing changed about the kernel or base=20 system. Just I leave the system alone compiling some stuff (like X.org) all= =20 night and, next day, the system has been crashed: no video output and no=20 response to keyboard nor network. b) the second one, this morning with 5.3-STABLE. It was downloading libxslt= =20 and, at 13 percent, the system went frozen. My question is: after the system has crashed, what can I do? I mean, where = can=20 I look for clues about what happened? Log files shows nothing about the=20 incidents, and I'd like to have a clue about what's wrong with FreeBSD and = my=20 machine. Ideas? Thank you in advance. =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 20:32:45 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3352E16A4CE; Mon, 17 Jan 2005 20:32:45 +0000 (GMT) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id C54B643D31; Mon, 17 Jan 2005 20:32:44 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from vimes.int.athame.co.uk ([192.168.1.3]) by hex.athame.co.uk with esmtp (Exim 4.43 (FreeBSD)) id 1CqdYE-000PZy-GY; Mon, 17 Jan 2005 22:32:38 +0200 From: Andy Fawcett Organization: Being Lazy At Home (BLAH!) To: freebsd-ports@freebsd.org Date: Mon, 17 Jan 2005 22:32:35 +0200 User-Agent: KMail/1.7.2 References: <20050117153341.GO93155@voodoo.oberon.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501172232.39413.andy@athame.co.uk> cc: Tom Huppi cc: freebsd-stable@freebsd.org Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 20:32:45 -0000 On Monday 17 January 2005 22:23, Tom Huppi wrote: > I worked at re-building Qt33 for quite some time, but > 'libqt-mt.so' still retains a reference to 'libc_r'. If there are > any common reasons why this may be, I'de be interested to know of > them. Make sure you rebuild devel/qmake before building qt This is because it is the config defined by qmake (actually /usr/local/share/qt/mkspecs/freebsd-g++/qmake.conf) that defines what thread library to use in building qt. A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 20:55:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF22E16A4CE for ; Mon, 17 Jan 2005 20:55:53 +0000 (GMT) Received: from alpha.VL7.net (CPE00a0242ca70c-CM014090203816.cpe.net.cable.rogers.com [65.50.68.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 040AF43D2F for ; Mon, 17 Jan 2005 20:55:53 +0000 (GMT) (envelope-from m@alpha.VL7.net) Received: from alpha.VL7.net (m@localhost [127.0.0.1]) by alpha.VL7.net (8.12.10/8.12.10) with ESMTP id j0HKtpss031926 for ; Mon, 17 Jan 2005 15:55:51 -0500 (EST) (envelope-from m@alpha.VL7.net) Received: (from m@localhost) by alpha.VL7.net (8.12.10/8.12.10/Submit) id j0HKtp02031925 for freebsd-stable@freebsd.org; Mon, 17 Jan 2005 15:55:51 -0500 (EST) (envelope-from m) Date: Mon, 17 Jan 2005 15:55:51 -0500 (EST) From: Vlad Message-Id: <200501172055.j0HKtp02031925@alpha.VL7.net> To: freebsd-stable@freebsd.org Subject: out of swap space X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 20:55:54 -0000 Hi! VERSION: I've got a problem with FreeBSD 5.3-STABLE cvsup'ed at Dec 20 2004: It has customized kernel - just a cleaned up GENERIC. DESCRIPTION: I have some programmers on php on my testing server. There are no classes in /etc/login.conf except "default". PROBLEM: When system running out of memory, it's just hang, no more ssh, no ping responds - only "reset" button. I've fixed it by customizing "daemon" class, but on 4.10-Stable, system killed processes like this without any classes, with message like this: "out of swap space: killed SOME_PID (httpd)" This feature was added after about 4.5-release. Do you have any ideas what's up with this great part of the system? Thanks in advance. Vlad. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 21:07:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C174616A4CE; Mon, 17 Jan 2005 21:07:15 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D22A43D45; Mon, 17 Jan 2005 21:07:15 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1Cqe5B-0000lt-T0; Mon, 17 Jan 2005 22:06:41 +0100 Date: Mon, 17 Jan 2005 22:06:41 +0100 From: Kirill Ponomarew To: Tom Huppi Message-ID: <20050117210641.GB2505@voodoo.oberon.net> References: <20050117153341.GO93155@voodoo.oberon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE cc: freebsd-stable@freebsd.org cc: "Hamilton, Kent" cc: freebsd-ports@freebsd.org Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 21:07:15 -0000 On Mon, Jan 17, 2005 at 03:23:36PM -0500, Tom Huppi wrote: > There is a reference to it in the 5.3 Errata (at least): > > http://www.freebsd.org/releases/5.3R/errata.html > > ...but I would have had a bit more trouble finding it had I not > known to look for the string 'libc_r'. > > I worked at re-building Qt33 for quite some time, but > 'libqt-mt.so' still retains a reference to 'libc_r'. If there are > any common reasons why this may be, I'de be interested to know of > them. I got rid of all other references (except one other library > associated also with Qt33), but couldn't nuke that one so I > resorted to the 'libmap.conf' hack which I would have preferred > not to do. In most cases there are dependencies which are still linked to libc_r, so check them first. -Kirill From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 21:15:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64C7B16A4F0; Mon, 17 Jan 2005 21:15:24 +0000 (GMT) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68F9243D5C; Mon, 17 Jan 2005 21:15:22 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j0HLRo5B016380; Mon, 17 Jan 2005 22:27:51 +0100 (MET) Message-ID: <41EC2ADD.5080006@fer.hr> Date: Mon, 17 Jan 2005 22:15:09 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: cannot su? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 21:15:24 -0000 Robert Watson wrote: > I've modified the su(1) source in HEAD to print a message if su(1) is > executed without an effective uid of 0 (i.e., as root, or setuid as > another user). Hopefully this error message will be more suggestive than > "sorry": > > paprika:~/freebsd/commit/src/usr.bin/su> ./su > su: not running setuid > > Assuming I didn't shoot any feet, I'll MFC this to RELENG_5 in a couple of > weeks. Thanks! :) From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:11:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E817416A4CE for ; Mon, 17 Jan 2005 22:11:23 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D39D643D39 for ; Mon, 17 Jan 2005 22:11:22 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: (qmail invoked by alias); 17 Jan 2005 22:11:21 -0000 Received: from p5487CD85.dip.t-dialin.net (EHLO localhost.localdomain) (84.135.205.133) by mail.gmx.net (mp007) with SMTP; 17 Jan 2005 23:11:21 +0100 X-Authenticated: #989277 From: Martin To: stable@freebsd.org In-Reply-To: <1103832537.770.28.camel@klotz.local> References: <1103832537.770.28.camel@klotz.local> Content-Type: text/plain Date: Mon, 17 Jan 2005 23:11:18 +0100 Message-Id: <1105999878.68178.16.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: Update to -STABLE breaks re(4) [CONT'D] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 22:11:24 -0000 Here a followup: > After reboot, re(4) "Realtek RTL8110S" could not be detected > automatically. It is statically compiled into the kernel. > The dmesg said something like "Could not send TCP packet in > loopback mode" or similar. This has been fixed for me, some time in January. > Next, I added if_re_load="YES" to /boot/loader.conf (tried > a workaround). The PC always rebooted before reaching the > "beastie menu". This problem still remains. I know it's weird to load a module while it has been compiled in statically, but it's still a bug, IMO. Steps to reproduce: 1) On FreeBSD/amd64, compile re(4) support into a STABLE kernel. 2) Add if_re_load="YES" to /boot/loader.conf. 3) Reboot. What happens? After loading the kernel image, re(4) module is about to be loaded and the machine does a a hard reset instantly. I hope it helps to find the problem. Martin From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:25:22 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F25316A4CE for ; Mon, 17 Jan 2005 22:25:22 +0000 (GMT) Received: from seed.net.tw (sn16.seed.net.tw [139.175.54.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id D449143D1F for ; Mon, 17 Jan 2005 22:25:21 +0000 (GMT) (envelope-from guitar@jazzcafe.no-ip.org) Received: from [221.169.112.158] (port=57091 helo=[192.168.0.222]) by seed.net.tw with esmtp (Seednet 4.23:1) id 1CqfJI-000MCo-Ko for freebsd-stable@freebsd.org; Tue, 18 Jan 2005 06:25:20 +0800 Date: Tue, 18 Jan 2005 06:25:31 +0800 From: CryBaby To: freebsd-stable@freebsd.org Message-Id: <20050118061637.E87D.GUITAR@jazzcafe.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12.01 [en] Subject: I can't receive any mail from mailing list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 22:25:22 -0000 my mail server: jazzcafe.no-ip.org I can receive mailing-list @ freebsd.org recently, but I can't receive mail now Some debug message below: % less /var/log/maillog ... Jan 18 06:17:15 jazzcafe sm-mta[10027]: j0HMFSaV010027: mx2.freebsd.org [216.136.204.119] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4 Jan 18 06:17:20 jazzcafe sm-mta[10028]: j0HMFXRj010028: mx2.freebsd.org [216.136.204.119] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4 Jan 18 06:17:23 jazzcafe sm-mta[10029]: j0HMFaHG010029: mx2.freebsd.org [216.136.204.119] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4 ... --- CryBaby From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:32:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2346816A4CE for ; Mon, 17 Jan 2005 22:32:08 +0000 (GMT) Received: from seed.net.tw (sn13.seed.net.tw [139.175.54.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9F1543D2D for ; Mon, 17 Jan 2005 22:32:07 +0000 (GMT) (envelope-from guitar@jazzcafe.no-ip.org) Received: from [221.169.112.158] (port=57005 helo=[192.168.0.222]) by seed.net.tw with esmtp (Seednet 4.23:1) id 1CqfPq-000Noq-Tu; Tue, 18 Jan 2005 06:32:07 +0800 Date: Tue, 18 Jan 2005 06:32:17 +0800 From: CryBaby To: CryBaby Message-Id: <20050118062920.E883.GUITAR@jazzcafe.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12.01 [en] cc: freebsd-stable@freebsd.org Subject: Re: I can't receive any mail from mailing list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 22:32:08 -0000 PS: I can get mail from other mail server (ex: my school, yahoo, ...) --- CryBaby From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:46:36 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA61B16A4CF for ; Mon, 17 Jan 2005 22:46:36 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DB1743D41 for ; Mon, 17 Jan 2005 22:46:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F1AA55145A; Mon, 17 Jan 2005 14:46:35 -0800 (PST) Date: Mon, 17 Jan 2005 14:46:35 -0800 From: Kris Kennaway To: Imobach Gonz?lez Sosa Message-ID: <20050117224635.GB31463@xor.obsecurity.org> References: <200501172024.33667.imobachgs@banot.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QKdGvSO+nmPlgiQ/" Content-Disposition: inline In-Reply-To: <200501172024.33667.imobachgs@banot.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: System crashes... what now? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 22:46:37 -0000 --QKdGvSO+nmPlgiQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 08:24:33PM +0000, Imobach Gonz?lez Sosa wrote: >=20 > Hi all, >=20 > I'm a newbie in the FreeBSD thing, and I'm having some problems that I'd = like=20 > to track down as far as possible. In four days using FreeBSD, my machine = has=20 > crashed two times, ugh! >=20 > a) first time, with 5.3-RELEASE. Nothing changed about the kernel or base= =20 > system. Just I leave the system alone compiling some stuff (like X.org) a= ll=20 > night and, next day, the system has been crashed: no video output and no= =20 > response to keyboard nor network. >=20 > b) the second one, this morning with 5.3-STABLE. It was downloading libxs= lt=20 > and, at 13 percent, the system went frozen. >=20 > My question is: after the system has crashed, what can I do? I mean, wher= e can=20 > I look for clues about what happened? Log files shows nothing about the= =20 > incidents, and I'd like to have a clue about what's wrong with FreeBSD an= d my=20 > machine. >=20 > Ideas? See the chapter on kernel debugging in the developers' handbook. Kris --QKdGvSO+nmPlgiQ/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7EBLWry0BWjoQKURAv5EAJ4lhiZ1NMiFjNoBossjlMMOvc3bzwCeNQxo VRs/NG709E8DhXyPcibhShs= =IG1h -----END PGP SIGNATURE----- --QKdGvSO+nmPlgiQ/-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:48:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B81916A4CE for ; Mon, 17 Jan 2005 22:48:11 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D6943D2D for ; Mon, 17 Jan 2005 22:48:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E87D35213F; Mon, 17 Jan 2005 14:48:09 -0800 (PST) Date: Mon, 17 Jan 2005 14:48:09 -0800 From: Kris Kennaway To: Mike Tancsa , freebsd-stable@freebsd.org Message-ID: <20050117224809.GC31463@xor.obsecurity.org> References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IpbVkmxF4tDyP/Kb" Content-Disposition: inline In-Reply-To: <20050117193844.GB1110@galgenberg.net> User-Agent: Mutt/1.4.2.1i Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 22:48:11 -0000 --IpbVkmxF4tDyP/Kb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 08:38:44PM +0100, Ulrich Spoerlein wrote: > On Thu, 13.01.2005 at 19:38:27 -0500, Mike Tancsa wrote: > > >I'm using -Os -pipe ever since installing 5.x after the gcc update. > > >Haven't encountered any problem so far.. > > There are some differences between O2 and Os according to the man=20 > > page. Are you using that on your kernel and for buildworld ? >=20 > Both, that is everything. Kernel, World, Ports. (Guess I'm lucky) Yes, it's certainly not supported to build ports with -O2 and many are known to have broken code exposed by this setting. > > I let the box run over night building world 8 times with -j2 through -j= 5=20 > > and all worked just fine. >=20 > Ok, that should put hardware out of the question. >=20 > Sorry, no more ideas, besides getting rid of CPUTYPE as that is know to > cause problems. Well, not in general, but in certain isolated cases. Kris --IpbVkmxF4tDyP/Kb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7ECpWry0BWjoQKURAhAMAKCLdpGY7e5WyPwWOtL6Ec/H6al2+wCfQ3EA f8lcdny5T8khHM8UHiMStg8= =jcJi -----END PGP SIGNATURE----- --IpbVkmxF4tDyP/Kb-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 22:55:32 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA4B916A4D0; Mon, 17 Jan 2005 22:55:32 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1575043D41; Mon, 17 Jan 2005 22:55:32 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])5E03F4E146; Mon, 17 Jan 2005 23:55:31 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05082-05-3; Mon, 17 Jan 2005 23:55:26 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFBEDD.dip.t-dialin.net [217.255.190.221]) 43F4C4E398; Mon, 17 Jan 2005 23:55:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 9A7BA79CA5; Mon, 17 Jan 2005 23:55:24 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05610-05-2; Mon, 17 Jan 2005 23:55:23 +0100 (CET) Received: from libertas.emma.line.org (libertas.emma.line.org [192.168.0.2]) by merlin.emma.line.org (Postfix) with ESMTP id B9F8D79CA4; Mon, 17 Jan 2005 23:55:23 +0100 (CET) Received: from emma by libertas.emma.line.org with local (Exim 4.43 (FreeBSD)) id 1CqfmW-0006CS-9D; Mon, 17 Jan 2005 23:55:32 +0100 To: FreeBSD-gnats-submit@freebsd.org From: Matthias Andree X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: Date: Mon, 17 Jan 2005 23:55:32 +0100 X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: stable@freebsd.org cc: re@freebsd.org Subject: FreeBSD 4.11-RC3 GCC preprocessor failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matthias Andree List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 22:55:33 -0000 >Submitter-Id: current-users >Originator: Matthias Andree >Organization: >Confidential: no >Synopsis: FreeBSD 4.11-RC3 GCC preprocessor failure >Severity: critical >Priority: high >Category: gnu >Class: sw-bug >Release: FreeBSD 4.11-RC3 i386 >Environment: System: FreeBSD libertas.emma.line.org 4.11-RC3 FreeBSD 4.11-RC3 #17: Mon Jan 17 21:44:19 CET 2005 root@libertas.emma.line.org:/usr/src/sys/compile/LIBERTAS i386 >Description: GCC 2.95.4 cannot compile e2fsprogs development version while GCC 3.3 is fine. The preprocessor fails to expand a macro with a longish name, error message: making all in lib/e2p gmake[2]: Entering directory `/tmp/e2fsprogs/build/lib/e2p' CC ../../../lib/e2p/feature.c ../../../lib/e2p/feature.c:50: `EXT3_FEATURE_INCOMPAT_EXTENTS' undeclared here (not in a function) ../../../lib/e2p/feature.c:50: initializer element is not constant ../../../lib/e2p/feature.c:50: (near initialization for `feature_list[12].mask') gmake[2]: *** [feature.o] Error 1 type: less lib/e2p/feature.i and type /EXT3 and press the enter key to see the problem area: { 1 , 0x0008 , "journal_dev" }, { 1 , EXT3_FEATURE_INCOMPAT_EXTENTS, "extents" }, { 1 , 0x0010 , "meta_bg" }, GCC 3.3 will properly replace EXT3_FEATURE_INCOMPAT_EXTENTS with 0x0040 (install lang/gcc33, then gmake CC=gcc33) >How-To-Repeat: - install devel/gmake port - install devel/bibktkeeper port (see PR #76208 if it's uncommitted) - cd to a writable directory with some 30 MB room - type these commands to check out, configure and build the code: # # the next three commands will clone the repository and check it out # bk clone -qr'tytso@think.thunk.org|ChangeSet|20050117193220|14963' \ bk://thunk.org:5000/ e2fsprogs/ cd e2fsprogs bk -Ur get -Sq # # now do the build # mkdir build cd build ../configure -C CFLAGS="-O -save-temps" gmake >Fix: From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 23:07:50 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC3C216A4CE; Mon, 17 Jan 2005 23:07:50 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FACC43D3F; Mon, 17 Jan 2005 23:07:50 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])5654C4E3AC; Tue, 18 Jan 2005 00:07:49 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09446-03; Tue, 18 Jan 2005 00:07:44 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFBEDD.dip.t-dialin.net [217.255.190.221]) 6B5E44E2DB; Tue, 18 Jan 2005 00:07:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id CE79A79791; Tue, 18 Jan 2005 00:07:42 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07510-03; Tue, 18 Jan 2005 00:07:42 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 09FB67979E; Tue, 18 Jan 2005 00:07:41 +0100 (CET) Date: Tue, 18 Jan 2005 00:07:41 +0100 From: Matthias Andree To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org Message-ID: <20050117230741.GA6632@merlin.emma.line.org> Mail-Followup-To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org, stable@freebsd.org, re@freebsd.org References: <200501172300.j0HN0hNx064864@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501172300.j0HN0hNx064864@freefall.freebsd.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: stable@freebsd.org cc: re@freebsd.org Subject: Re: gnu/76381: FreeBSD 4.11-RC3 GCC preprocessor failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 23:07:50 -0000 Oops. The port is devel/bitkeeper. As this requires registration, I made a tarball, which will not lie around forever though. http://home.pages.de/~mandree/tmp/e2fsprogs-1.36rc2.tar.gz (3.3 MB) MD5 (e2fsprogs-1.36rc2.tar.gz) = 441c54b116d3426f7c16eb3bb3657648 After downloading, unpack the tarball, cd e2fsprogs-1.36rc2, then proceed with mkdir build ; cd build ... as shown above. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 23:30:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA65416A4CE for ; Mon, 17 Jan 2005 23:30:58 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62A9243D4C for ; Mon, 17 Jan 2005 23:30:57 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id D9FA4746F for ; Tue, 18 Jan 2005 01:07:43 +0000 (WET) From: Imobach =?iso-8859-15?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Mon, 17 Jan 2005 23:30:22 +0000 User-Agent: KMail/1.7.2 References: <200501172024.33667.imobachgs@banot.net> <20050117224635.GB31463@xor.obsecurity.org> In-Reply-To: <20050117224635.GB31463@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501172330.22273.imobachgs@banot.net> Subject: Re: System crashes... what now? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 23:30:58 -0000 On Monday 17 January 2005 22:46, you wrote: > See the chapter on kernel debugging in the developers' handbook. Thank you. I'll take a look on it. > Kris =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 23:32:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94F1C16A4CE for ; Mon, 17 Jan 2005 23:32:42 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DBC843D45 for ; Mon, 17 Jan 2005 23:32:42 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IAHIQM00.OSF; Mon, 17 Jan 2005 15:32:46 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005011715360911310 ; Mon, 17 Jan 2005 15:36:09 -0800 From: "Vinod Kashyap" To: boris karlov , stable@freebsd.org Date: Mon, 17 Jan 2005 15:32:38 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: Subject: RE: twa module - make kernel (modules) failure RELENG_5 i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Jan 2005 23:32:42 -0000 Make sure you have the updated /sys/dev/twa/twa_reg.h. The struct twa_command_header has the field err_desc defined in it. > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of boris karlov > Sent: Sunday, January 16, 2005 11:03 PM > To: stable@freebsd.org > Subject: twa module - make kernel (modules) failure RELENG_5 i386 > = > = > Hello All, > I have make kernel failure during compiling twa module (see below). > cvsupped RELENG_5 Fri Jan 14. > have no any twa devices in the system. > (please Cc: me in reply - not subscribed to stable@) > thanks. > = > =3D=3D=3D> twa > cc -O -pipe -march=3Dpentium2 -D_KERNEL -DKLD_MODULE -nostdinc = > -I- -include > /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ = > -I@/contrib/altq > -I@/../include -finline-limit=3D8000 -fno-common > -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings > -mpreferred-stack-boundary=3D2 -ffreestanding -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes = > -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -c > /usr/src/sys/modules/twa/../../dev/twa/twa_freebsd.c > cc -O -pipe -march=3Dpentium2 -D_KERNEL -DKLD_MODULE -nostdinc = > -I- -include > /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ = > -I@/contrib/altq > -I@/../include -finline-limit=3D8000 -fno-common > -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings > -mpreferred-stack-boundary=3D2 -ffreestanding -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes = > -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -c > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c: In function > `twa_scsi_complete': > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: = > structure has > no member named `err_desc' > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: = > structure has > no member named `err_desc' > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:636: error: = > structure has > no member named `err_desc' > *** Error code 1 > = > Stop in /usr/src/sys/modules/twa. > *** Error code 1 > = > = > /etc/make.conf: > CPUTYPE=3Dp2 > NO_CVS=3Dtrue > NO_BIND=3Dtrue > NO_BLUETOOTH=3Dtrue > NO_FORTRAN=3Dtrue > NO_GDB=3Dtrue > NO_I4B=3Dtrue > NO_IPFILTER=3Dtrue > NO_PF=3Dtrue > NO_AUTHPF=3Dtrue > NO_KERBEROS=3Dtrue > NO_NIS=3Dtrue > NO_TCSH=3Dtrue > NO_USB=3Dtrue > NO_VINUM=3Dtrue > NOATM=3Dtrue > NOGAMES=3Dtrue > NOINET6=3Dtrue > NOINFO=3Dtrue > NOPROFILE=3Dtrue > = > _______________________________________________ > 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 Jan 18 02:11:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A5FF16A4CE for ; Tue, 18 Jan 2005 02:11:42 +0000 (GMT) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8D2C43D53 for ; Tue, 18 Jan 2005 02:11:41 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id j0I2Be0C026309; Mon, 17 Jan 2005 21:11:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca ([127.0.0.1]) by localhost (avscan1.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25937-05; Mon, 17 Jan 2005 21:11:40 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id j0I2BePg026286; Mon, 17 Jan 2005 21:11:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id j0I2BXQB036224; Mon, 17 Jan 2005 21:11:34 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 17 Jan 2005 21:12:26 -0500 To: Kris Kennaway , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050117224809.GC31463@xor.obsecurity.org> References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> <20050117224809.GC31463@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan1b Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 02:11:42 -0000 At 05:48 PM 17/01/2005, Kris Kennaway wrote: > > > I let the box run over night building world 8 times with -j2 through -j5 > > > and all worked just fine. > > > > Ok, that should put hardware out of the question. > > > > Sorry, no more ideas, besides getting rid of CPUTYPE as that is know to > > cause problems. > >Well, not in general, but in certain isolated cases. Like I said before, switching back to -O makes the system stable once again. I let it run continuous buildworlds without issue for 24hrs along with burnP6, and memtest running in the background. No problem. The machine is still on the bench so if anyone wants me to try and debug it somehow I am happy to test. ---Mike ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 03:15:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30CE416A4CE for ; Tue, 18 Jan 2005 03:15:01 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1259943D49 for ; Tue, 18 Jan 2005 03:15:01 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E4EFF72DD4; Mon, 17 Jan 2005 19:15:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id DF66672DCB; Mon, 17 Jan 2005 19:15:00 -0800 (PST) Date: Mon, 17 Jan 2005 19:15:00 -0800 (PST) From: Doug White To: CryBaby In-Reply-To: <20050118061637.E87D.GUITAR@jazzcafe.no-ip.org> Message-ID: <20050117191412.H57355@carver.gumbysoft.com> References: <20050118061637.E87D.GUITAR@jazzcafe.no-ip.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: I can't receive any mail from mailing list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 03:15:01 -0000 On Tue, 18 Jan 2005, CryBaby wrote: > my mail server: jazzcafe.no-ip.org > > I can receive mailing-list @ freebsd.org recently, but I can't receive mail now > Some debug message below: > > % less /var/log/maillog > ... > Jan 18 06:17:15 jazzcafe sm-mta[10027]: j0HMFSaV010027: mx2.freebsd.org [216.136.204.119] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4 > Jan 18 06:17:20 jazzcafe sm-mta[10028]: j0HMFXRj010028: mx2.freebsd.org [216.136.204.119] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4 Can you tcpdump this? mx2 runs Postfix and it has some client-side timeouts. If your system is taking too long to respond it might drop the connection. tcpdump would help give us some timings. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 04:06:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FFF016A4CE for ; Tue, 18 Jan 2005 04:06:29 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CC7243D2D for ; Tue, 18 Jan 2005 04:06:29 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.3] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 0D457B875 for ; Mon, 17 Jan 2005 23:06:29 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20050113094624.GD79646@cirb503493.alcatel.com.au> References: <41E36760.2090609@updegrove.net> <44fz18m5k4.fsf@be-well.ilk.org> <41E59844.6000805@updegrove.net> <20050113094624.GD79646@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <557348B4-6906-11D9-B522-000A95D14982@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 17 Jan 2005 23:06:30 -0500 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: 5.3-RELEASE crashes during make buildworld (and other problems) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 04:06:29 -0000 On Jan 13, 2005, at 4:46 AM, Peter Jeremy wrote: > That doesn't totally rule out hardware. Pattern-sensitive memory > problems may not show up on different operating systems (or even > different kernels). That said, based on the trap information, I'd > look at a software cause first. Indeed. I once had a box that would run Linux 100% stable under any load for months on end, but with BSD/OS it would crap out (random processes fail) after a max of 3 weeks requiring a reboot. Never rule out bad hardware, especially with PC crap. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 04:46:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A2D316A4CE; Tue, 18 Jan 2005 04:46:57 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5CA243D46; Tue, 18 Jan 2005 04:46:56 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) j0I4kuIo018631; Mon, 17 Jan 2005 23:46:56 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id j0I4ktcv018630; Mon, 17 Jan 2005 23:46:55 -0500 (EST) Date: Mon, 17 Jan 2005 23:46:55 -0500 From: Ken Smith To: Matthias Andree Message-ID: <20050118044655.GB16322@electra.cse.Buffalo.EDU> References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: re@freebsd.org cc: freebsd-stable@freebsd.org cc: kensmith@freebsd.org Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 04:46:57 -0000 On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote: > critical: > kern/60313 (silent data corruption on block devices) > still open, may be FreeBSD 4 specific after the GEOM flurry > in FreeBSD 5 and 6. I took a look at that one. The patch provided doesn't map exactly into RELENG_4 but I gave this a try: Index: subr_diskslice.c =================================================================== RCS file: /home/ncvs/src/sys/kern/Attic/subr_diskslice.c,v retrieving revision 1.82.2.6 diff -u -r1.82.2.6 subr_diskslice.c --- subr_diskslice.c 24 Jul 2001 09:49:41 -0000 1.82.2.6 +++ subr_diskslice.c 17 Jan 2005 23:40:42 -0000 @@ -147,6 +147,7 @@ daddr_t slicerel_secno; struct diskslice *sp; int s; + off_t offset; blkno = bp->b_blkno; if (blkno < 0) { @@ -155,6 +156,14 @@ bp->b_error = EINVAL; goto bad; } + offset = bp->b_offset; + if (offset % (off_t)DEV_BSIZE) { + printf( + "dscheck(%s): b_offset %ld is not on a DEV_BSIZE boundary\n", + devtoname(bp->b_dev), (long)offset); + bp->b_error = EINVAL; + goto bad; + } sp = &ssp->dss_slices[dkslice(bp->b_dev)]; lp = sp->ds_label; if (ssp->dss_secmult == 1) { With that in place the kernel won't boot because the stuff dealing with disk labels in at least two places on my machine didn't set the offset properly in the buf structures it used. Once I fixed that the machine booted but *some* executables wouldn't start because spec_getpages() was doing reads with an offset of 256 (DEV_BSIZE is 512). I'll see if I can follow up on this and eventually get RELENG_4 fixed (and perhaps even an Errata) but there is no way I'd be comfortable with a fix for this going into 4.11 unless an expert worked on it and we did an RC4. > serious: > bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open It looks like the right way to fix this is with a fresh vendor import if I'm understanding things correctly. Again something that would require more time than we have and might be best handled as an Errata item after the release. > bin/46866 (false data from getpwent, easy to fix) still open There has been ongoing disagreements about how best to handle this one, as far as I can tell the disagreements are still ongoing. > non-critical: > kern/44260 (missing device in LINT configuration) > is long-standing although trivial to fix (patch included) Scott fixed that earlier today (MFS pending). -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 06:24:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D03E616A4CF for ; Tue, 18 Jan 2005 06:24:52 +0000 (GMT) Received: from nuumen.pair.com (nuumen.pair.com [209.68.1.119]) by mx1.FreeBSD.org (Postfix) with SMTP id 41CB343D4C for ; Tue, 18 Jan 2005 06:24:52 +0000 (GMT) (envelope-from thuppi@nuumen.pair.com) Received: (qmail 92379 invoked by uid 55300); 18 Jan 2005 06:24:51 -0000 Date: Tue, 18 Jan 2005 01:24:51 -0500 (EST) From: Tom Huppi X-X-Sender: thuppi@nuumen.pair.com To: Andy Fawcett In-Reply-To: <200501172232.39413.andy@athame.co.uk> Message-ID: References: <200501172232.39413.andy@athame.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 06:24:53 -0000 On Mon, 17 Jan 2005, Andy Fawcett wrote: > On Monday 17 January 2005 22:23, Tom Huppi wrote: > > I worked at re-building Qt33 for quite some time, but > > 'libqt-mt.so' still retains a reference to 'libc_r'. If there are > > any common reasons why this may be, I'de be interested to know of > > them. > > Make sure you rebuild devel/qmake before building qt > > This is because it is the config defined by qmake > (actually /usr/local/share/qt/mkspecs/freebsd-g++/qmake.conf) that defines > what thread library to use in building qt. That was it. Thanks much for your enlightenment! - Tom > A. > -- > Andy Fawcett | andy@athame.co.uk > | tap@kde.org > "In an open world without walls and fences, | tap@lspace.org > we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 07:46:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D133216A4CE for ; Tue, 18 Jan 2005 07:46:29 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DD4243D48 for ; Tue, 18 Jan 2005 07:46:27 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from [192.168.2.10] (pD9542622.dip.t-dialin.net [217.84.38.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 8F5CC2FADB; Tue, 18 Jan 2005 08:46:23 +0100 (CET) Message-ID: <41ECBED0.8000704@incubus.de> Date: Tue, 18 Jan 2005 08:46:24 +0100 From: Matthias Buelow User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Tancsa References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> <20050117224809.GC31463@xor.obsecurity.org> <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> In-Reply-To: <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 07:46:29 -0000 Mike Tancsa wrote: > At 05:48 PM 17/01/2005, Kris Kennaway wrote: > > Like I said before, switching back to -O makes the system stable once > again. I let it run continuous buildworlds without issue for 24hrs > along with burnP6, and memtest running in the background. No problem. Then I'd leave it at that. The difference between gcc -O2 and -O is marginal at best. Think of it as -O being the large axe that chops off a huge slab, and -O2 being the large axe, followed by some scratching with a nail-file. Most of the time it isn't worth the effort. mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 08:08:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07A6616A4CE for ; Tue, 18 Jan 2005 08:08:18 +0000 (GMT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD3CB43D5A for ; Tue, 18 Jan 2005 08:08:17 +0000 (GMT) (envelope-from kokje@ISI.EDU) Received: from [192.168.0.2] (c-24-126-88-201.we.client2.attbi.com [24.126.88.201]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0I87CQ10820 for ; Tue, 18 Jan 2005 00:07:14 -0800 (PST) Message-ID: <41ECC3A7.8040300@ISI.EDU> Date: Tue, 18 Jan 2005 00:07:03 -0800 From: Tejas Kokje Organization: Information Sciences Institute User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: kokje@isi.edu Subject: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 08:08:18 -0000 Hi folks, I recently installed FreeBSD 5.3 stable. I got my sound blaster live 5.1 sound card working with FreeBSD by adding device sound device emu10k1 in the kernel configuration file. However the quality of sound produced is of poor quality (not very clear) as compared to that produced under Linux 2.6 series kernel. I remember having similar quality sound when OSS was used with Linux Kernel. Is this poor quality because of OSS ? Is ALSA ported to FreeBSD ? Or am I just using wrong driver ? Tejas Kokje University of Southern California From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 09:23:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31B4316A4CE for ; Tue, 18 Jan 2005 09:23:39 +0000 (GMT) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CDCF43D39 for ; Tue, 18 Jan 2005 09:23:38 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (smtp-1a.paradise.net.nz [202.0.32.194]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IAI00JLCA3DQR@linda-1.paradise.net.nz> for freebsd-stable@freebsd.org; Tue, 18 Jan 2005 22:23:37 +1300 (NZDT) Received: from [192.168.1.11] (218-101-12-245.paradise.net.nz [218.101.12.245]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 01FDD827BF; Tue, 18 Jan 2005 22:23:37 +1300 (NZDT) Date: Tue, 18 Jan 2005 22:27:33 +1300 From: Mark Kirkwood In-reply-to: <41ECC3A7.8040300@ISI.EDU> To: Tejas Kokje Message-id: <41ECD685.3090904@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 References: <41ECC3A7.8040300@ISI.EDU> cc: freebsd-stable@freebsd.org Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 09:23:39 -0000 Tejas Kokje wrote: > Hi folks, > > I recently installed FreeBSD 5.3 stable. I got my sound > blaster live 5.1 sound card working with FreeBSD by adding > > device sound > device emu10k1 > > > hmmm... the 5.3 handbook has : device "snd_emu10k1" or /boot/loader.conf : snd_emu10k1_load="YES" regards Mark From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 11:01:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3265F16A4D8 for ; Tue, 18 Jan 2005 11:01:23 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9C2043D6B for ; Tue, 18 Jan 2005 11:00:11 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0IB06pY029329; Tue, 18 Jan 2005 06:00:06 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0IAxqaT029309; Tue, 18 Jan 2005 11:00:06 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 18 Jan 2005 10:59:52 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Vivek Khera In-Reply-To: <557348B4-6906-11D9-B522-000A95D14982@khera.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: 5.3-RELEASE crashes during make buildworld (and other problems) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 11:01:23 -0000 On Mon, 17 Jan 2005, Vivek Khera wrote: > On Jan 13, 2005, at 4:46 AM, Peter Jeremy wrote: > > > That doesn't totally rule out hardware. Pattern-sensitive memory > > problems may not show up on different operating systems (or even > > different kernels). That said, based on the trap information, I'd > > look at a software cause first. > > Indeed. I once had a box that would run Linux 100% stable under any > load for months on end, but with BSD/OS it would crap out (random > processes fail) after a max of 3 weeks requiring a reboot. > > Never rule out bad hardware, especially with PC crap. Even minor OS revisions can reveal or hide memory problems. For example, for quite a while one of my Pentium (1!) server boxes had a single bit error (a stuck on bit) that fell into a section of memory that always held pinned kernel pages, and in particular, ended up holding a fairly obscure kernel code branch in a module that was loaded. Then one day kernel memory layout got chaged a bit, and the page ended up being paged into user memory, resulting in frequent application segfaults and data corruption. I was sure it was the OS upgrade, since backing out to the previous kernel/modules fixed it reliably ... until I ran a memory test and figured out what was actually happening. It was pretty frustrating to try to debug, and reinforces the conclusion that doing a bit of legwork on a badly behaving system to confirm it's not a hardware fault that can be easily ruled out can go a long way. Which isn't to say that the problem in this thread is hardware, but you don't want to spend two weeks tracking a kernel bug to find out that swapping out the memory with a seemingly identical DIMM fixes it. Checking ethernet cabling and link negotiation, a decent memory test run, checking SCSI termination, checking ATA cable type, etc, as first steps to debugging a problem that would have similar symptoms is a good strt. Oh, and if it's your parents calling on the phone at 6:30am with a printer problem, the first thing to ask is whether their printer is plugged in. :-) Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 11:16:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C335516A4CE for ; Tue, 18 Jan 2005 11:16:31 +0000 (GMT) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30E2D43D60 for ; Tue, 18 Jan 2005 11:16:31 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0IBGTeZ025697 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Jan 2005 22:16:30 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0IBGSxP064296 for ; Tue, 18 Jan 2005 22:16:28 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j0IBGSZE064295 for freebsd-stable@freebsd.org; Tue, 18 Jan 2005 22:16:28 +1100 (EST) (envelope-from pjeremy) Date: Tue, 18 Jan 2005 22:16:28 +1100 From: Peter Jeremy To: freebsd-stable@freebsd.org Message-ID: <20050118111628.GH79646@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Subject: Purpose of CD9660_ROOT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 11:16:31 -0000 RELENG_4 documents a config option: options CD9660_ROOT #ISO 9660 Filesystem usable as root but I am unable to find any other reference to this option. I can confirm that CD9660_ROOT is _not_ necessary for 4.10 (at least) boot off a CD-ROM and use it as root. The last reference I can find is in ARCH/ARCH/autoconf.c from whence it was deleted well before RELENG_4_BP. Have I missed something or is this option a total no-op? -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 11:22:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F3116A4CE for ; Tue, 18 Jan 2005 11:22:01 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BD6B43D5A for ; Tue, 18 Jan 2005 11:22:00 +0000 (GMT) (envelope-from davidelsing@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so845770wri for ; Tue, 18 Jan 2005 03:22:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=rreZBib68y8sF5T/hedDQ8mjmO80uawujPD0tbny5+ITb7k3FDX0vrs5Cmd0+aA6YoihSmjQlNPfgR7fp0m8zNK1o5XRaO77vmRO8KB0f/YbBMYWpuRou8NmEKryIXz2CjWqgR0X/iu8597O3m8rTRtuuPGPVBJJuoQODiNBtRQ= Received: by 10.54.52.40 with SMTP id z40mr113713wrz; Tue, 18 Jan 2005 03:21:59 -0800 (PST) Received: by 10.54.5.6 with HTTP; Tue, 18 Jan 2005 03:21:59 -0800 (PST) Message-ID: Date: Tue, 18 Jan 2005 12:21:59 +0100 From: David Elsing To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Vinum Raid5 Init question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Elsing List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 11:22:01 -0000 I've installed Vinum RAID5 on a 4-disk setup. Since I don't have much experience I installed my plex through the example in the Vinum manual. I used 'setupstate' to put the disks into 'up'-status. Quote from the manual of the 4th example of the chapter "HOW TO SET UP VINUM": "In addition, the volume specification includes the keyword setupstate, which ensures that all plexes are up after creation." But a couple of weeks later I read the following in the manual: "Note that you must use the init command with RAID-5 plexes: otherwise extreme data corruption will result if one subdisk fails." I read this to my horror after I filled the volume with data. You'll probably noticed I didn't init my volume. The disks are in good condition. The volume is almost filled to the maximum capacity. So a backup is a bit difficult due to the size of it. Are there any other options? If one disks fails, do I still get corrupted data? I don't know if any manual maintainer is reading this, but is it possible to add this warning to the RAID5 example at the end of vinum(8)? Regards, David Elsing Vinum create file: drive d1 device /dev/ad4s1e drive d2 device /dev/ad5s1e drive d3 device /dev/ad6s1e drive d4 device /dev/ad7s1e volume raid setupstate plex org raid5 1024k sd length 0 drive d1 sd length 0 drive d2 sd length 0 drive d3 sd length 0 drive d4 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 11:35:19 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4F0216A4DF for ; Tue, 18 Jan 2005 11:35:19 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D62AC43D1F for ; Tue, 18 Jan 2005 11:35:18 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])F15FE4EBA2 for ; Tue, 18 Jan 2005 12:35:17 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20082-03-3 for ; Tue, 18 Jan 2005 12:35:13 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFBDA5.dip.t-dialin.net [217.255.189.165]) AEB634EB80 for ; Tue, 18 Jan 2005 12:35:12 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id B2CC378092 for ; Tue, 18 Jan 2005 12:35:11 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13967-02 for ; Tue, 18 Jan 2005 12:35:10 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id EF84B7808F; Tue, 18 Jan 2005 12:35:09 +0100 (CET) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <20050118044655.GB16322@electra.cse.Buffalo.EDU> (Ken Smith's message of "Mon, 17 Jan 2005 23:46:55 -0500") References: <20050117020739.GA2736@bobbi.cse.buffalo.edu> <20050118044655.GB16322@electra.cse.Buffalo.EDU> Date: Tue, 18 Jan 2005 12:35:09 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: Re: remaining FreeBSD 4.11-RC3 bugs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 11:35:19 -0000 Ken Smith writes: > On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote: > >> critical: >> kern/60313 (silent data corruption on block devices) >> still open, may be FreeBSD 4 specific after the GEOM flurry >> in FreeBSD 5 and 6. > > I took a look at that one. The patch provided doesn't map exactly into > RELENG_4 but I gave this a try: Some (similar) attempts are in the mailing list archives, but none ended as a complete fix and stopped halfway for various reasons, usually lack of time or interest. I know too little about kernel internals as to be of any help here, besides testing. > With that in place the kernel won't boot because the stuff dealing with > disk labels in at least two places on my machine didn't set the offset > properly in the buf structures it used. Once I fixed that the machine > booted but *some* executables wouldn't start because spec_getpages() > was doing reads with an offset of 256 (DEV_BSIZE is 512). These some executables may well have been reading the wrong data since the block devices have become unbuffered... if unaligned, the seek offset is silently rounded down to the previous block margin. > I'll see if I can follow up on this and eventually get RELENG_4 fixed > (and perhaps even an Errata) but there is no way I'd be comfortable > with a fix for this going into 4.11 unless an expert worked on it > and we did an RC4. I can understand that. >> serious: >> bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open > > It looks like the right way to fix this is with a fresh vendor import > if I'm understanding things correctly. Again something that would > require more time than we have and might be best handled as an Errata > item after the release. If the FreeBSD 4.11-RC tcpdump is essentially the same as the FreeBSD tcpdump around 5.3, the import of a single fix may be sufficient. It's only that the tcpdump executable does The Wrong Thing when encountering PPP packets to negotiate IPv6 - it faults, rather than reporting an unknown packet and moving on. The patch quoted in the PR fixes only that bogus abort. >> bin/46866 (false data from getpwent, easy to fix) still open > > There has been ongoing disagreements about how best to handle this one, > as far as I can tell the disagreements are still ongoing. If FreeBSD prefers non-deterministic results with all non-repeatable and hard to debug consequences such as mail bouncing, users denied login and so on, well. The only reason brought forth in support of the current behavior was the measly "we've always done it this way" and perhaps "we don't know what will break if". Neither is a valid justification to keep the bug in. Note this change need only happen for functions with insufficient interfaces, i. e. those that cannot report a difference between temporary and permanent error, such as getpwent(), and AFAICT the lookups happen in user-space, so SIGINT would work. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 12:07:00 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE62916A4CF for ; Tue, 18 Jan 2005 12:07:00 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D8AE343D49 for ; Tue, 18 Jan 2005 12:06:59 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 18 Jan 2005 12:06:58 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp013) with SMTP; 18 Jan 2005 13:06:58 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 13:06:43 +0100 User-Agent: KMail/1.7.2 X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart23613036.DmIMnPQQud"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501181306.49120.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 12:07:00 -0000 --nextPart23613036.DmIMnPQQud Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the= =20 other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have=20 ucom0, also I can receive signal but not transmit. When I connect the (more expensive) adopter to a serial console (FreeBSD=20 comconsole) I can see all kernel messages but I can't type any charecter wh= en=20 I see the login. If I change to the cheaper adopter everything is working=20 fine. I compared 'stty -a -f /dev/ucom0' and both adaptors show the same=20 settings. I'm using tip (ucom0:dv=3D/dev/ucom0:br#115200:pa=3Dnone:) on RELENG_5 (fro= m this=20 weekend) Here is usbdevfs output and the corresponding dmesg line for both adapters,= =20 the 2nd (ATEN) is the working one (cheaper one), the first the more expensi= ve=20 not working one! port 1 addr 2: full speed, power 100 mA, config 1, USB-Serial=20 Controller(0x2303), Prolific Technology Inc.(0x067b), rev 3.00 __dmesg: ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 port 1 addr 2: full speed, power 100 mA, config 1, PL2303 Serial adapter=20 (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 __dmesg: ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev= =20 1.10/2.02, addr 2 Any help highly appreciated! =2DHarry --nextPart23613036.DmIMnPQQud Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7PvZBylq0S4AzzwRAjCkAKCCri7KwY8+7JAn7aTt5UP9+hVX6QCfcZxh gRhSQuXa99ombtpDErz3mSA= =AcCK -----END PGP SIGNATURE----- --nextPart23613036.DmIMnPQQud-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 10:59:14 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CD8216A4CF; Tue, 18 Jan 2005 10:59:14 +0000 (GMT) Received: from vampextream.com (vampextream.com [65.102.125.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1284E43D5C; Tue, 18 Jan 2005 10:59:14 +0000 (GMT) (envelope-from whitevamp@vampextream.com) Received: from localhost (localhost.vampextream [127.0.0.1]) by vampextream.com (Postfix) with ESMTP id 81A5E54BB; Tue, 18 Jan 2005 03:03:09 -0800 (PST) Received: from vampextream.com ([127.0.0.1]) by localhost (vampextream.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06312-03; Tue, 18 Jan 2005 03:02:06 -0800 (PST) Received: from vampextream.com (localhost.vampextream [127.0.0.1]) by vampextream.com (Postfix) with ESMTP id BD71F54BA; Tue, 18 Jan 2005 03:01:47 -0800 (PST) From: "whitevamp" To: freebsd-ports@freebsd.org;, freebsd-stable@freebsd.org Date: Tue, 18 Jan 2005 03:01:46 -0800 Message-Id: <20050118105945.M12726@vampextream.com> X-Mailer: Open WebMail 2.41 20040926 X-OriginatingIP: 65.102.125.195 (whitevamp@vampextream.com) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Tue, 18 Jan 2005 14:11:04 +0000 Subject: ruby and portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 10:59:14 -0000 i am trying to do a portupgrade and after it running for 7 hrs and not doing anything it quits with this error message. black-buity# portupgrade -aRrcCv ---> Reading default options: -v -D -l /var/tmp/portupgrade.results -L /var/tmp/portupgrade-%s::%s.log ---> Session started at: Sat, 15 Jan 2005 12:07:25 -0800 [Updating the pkgdb in /var/db/pkg ... - 110 packages found (-0 +23) ....................... done] ---> Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 black-buity# black-buity# ruby --version ruby 1.8.2 (2004-07-29) [i386-freebsd5] black-buity# uname -a FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Dec 10 14:50:33 PST 2004 root@black-buity.vampextream.com:/usr/src/sys/i386/compile/VAMPEXTREAM i386 black-buity# i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby from 1.6 to 1.8 .. so my quistions are 1. what would be causeing this?? 2. how do i fix this? and thanks inadvance for any help on this issue/ error message If you play the WindowsXP CD backwards, you get a Satanic message . That's nothing. If you play it forwards, it installs WindowsXP! From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 11:57:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 638E016A4CE; Tue, 18 Jan 2005 11:57:59 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15CB943D2D; Tue, 18 Jan 2005 11:57:59 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1CqrzH-000BsR-7W; Tue, 18 Jan 2005 12:57:31 +0100 Date: Tue, 18 Jan 2005 12:57:31 +0100 From: Kirill Ponomarew To: whitevamp Message-ID: <20050118115731.GC44541@voodoo.oberon.net> References: <20050118105945.M12726@vampextream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050118105945.M12726@vampextream.com> X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE X-Mailman-Approved-At: Tue, 18 Jan 2005 14:10:57 +0000 cc: freebsd-ports@freebsd.org Subject: Re: ruby and portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 11:57:59 -0000 On Tue, Jan 18, 2005 at 03:01:46AM -0800, whitevamp wrote: > i am trying to do a portupgrade and after it running for 7 hrs and not doing > anything it quits with this error message. > > black-buity# portupgrade -aRrcCv > > ---> Reading default options: -v -D -l /var/tmp/portupgrade.results -L > /var/tmp/portupgrade-%s::%s.log > ---> Session started at: Sat, 15 Jan 2005 12:07:25 -0800 > [Updating the pkgdb in /var/db/pkg ... - 110 packages > found (-0 +23) ....................... done] > ---> Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert > nil into String (PkgDB::DBError) > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' > from /usr/local/sbin/portupgrade:674:in `main' > from /usr/local/sbin/portupgrade:207:in `initialize' > from /usr/local/sbin/portupgrade:207:in `new' > from /usr/local/sbin/portupgrade:207:in `main' > from /usr/local/sbin/portupgrade:1845 > black-buity# > > black-buity# ruby --version > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > black-buity# uname -a > FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri > Dec 10 14:50:33 PST 2004 > root@black-buity.vampextream.com:/usr/src/sys/i386/compile/VAMPEXTREAM i386 > black-buity# > > i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby > from 1.6 to 1.8 .. > so my quistions are > > 1. what would be causeing this?? > 2. how do i fix this? > > and thanks inadvance for any help on this issue/ error message Database seems to be corrupted, rebuild it with 'pkgdb -fu' -Kirill From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 14:33:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9555416A4CE for ; Tue, 18 Jan 2005 14:33:06 +0000 (GMT) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F1C143D41 for ; Tue, 18 Jan 2005 14:33:06 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (mail, from userid 1001) id E1D9A2A98B; Tue, 18 Jan 2005 08:33:05 -0600 (CST) Date: Tue, 18 Jan 2005 08:33:03 -0600 From: Craig Boston To: David Elsing Message-ID: <20050118143302.GA99345@nowhere> Mail-Followup-To: Craig Boston , David Elsing , freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: Vinum Raid5 Init question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 14:33:06 -0000 On Tue, Jan 18, 2005 at 12:21:59PM +0100, David Elsing wrote: > Quote from the manual of the 4th example of the chapter "HOW TO SET UP VINUM": > "In addition, the volume specification includes the keyword > setupstate, which ensures that all plexes are up after creation." > > But a couple of weeks later I read the following in the manual: > > "Note that you must use the init command with RAID-5 plexes: otherwise > extreme data corruption will result if one subdisk fails." Yes, this particular gotcha bit me a while back and I lost quite a bit of data (my fault for not having good backups) due to it. IMO, I still consider it a documentation bug though. That particular bit is buried in a command reference section rather than being in bold in the "HOW TO" guide. > I read this to my horror after I filled the volume with data. You'll > probably noticed I didn't init my volume. The disks are in good > condition. The volume is almost filled to the maximum capacity. So a > backup is a bit difficult due to the size of it. Are there any other > options? If one disks fails, do I still get corrupted data? Yes, if one disk fails for any reason, every third sector will be garbage and it's unlikely you'll be able to recover anything useful from it. I would highly recommend backing up whatever is critically important to you asap. If you like living dangerously and all the drives are in good health, the parity data can be (theoretically) repaired with the "vinum rebuildparity" command, but do so at your own risk... That did allow me to recover a couple of my partitions that hadn't been trashed yet. Also, if a good disk gets marked as "down" somehow before you can correct this, whatever you do, do NOT issue a "vinum start" command on it. In the current state of the array, that would be destructive and irreversible. That's what happened to me: ATA timeout caused one of the drives to temporarily detach, corrupt filesystems caused a panic. If this happens, you're better off using setstate to force it to up, as wrong as that would normally be. I've also noticed that sometimes the parity gets out of sync on its own, but I don't know the cause. I used to have a cron job that ran vinum checkparity once a month in the background and occasionally it would find sectors that needed to be rebuilt. Unfortunately this doesn't seem to be implemented with gvinum (5.3) yet. > ...know if any manual maintainer is reading this, but is it possible > to add this warning to the RAID5 example at the end of vinum(8)? I'll second this idea, at least for 4.x. I'm not sure how gvinum handles things as I haven't built any RAID5 volumes from scratch using it. Craig From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 14:36:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21AC016A4CE for ; Tue, 18 Jan 2005 14:36:57 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C296543D1F for ; Tue, 18 Jan 2005 14:36:56 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 211DB677EF for ; Tue, 18 Jan 2005 14:36:55 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.1/8.13.1) with ESMTP id j0IEaZQ3019211; Wed, 19 Jan 2005 01:36:35 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200501181436.j0IEaZQ3019211@drugs.dv.isc.org> To: "whitevamp" From: Mark Andrews In-reply-to: Your message of "Tue, 18 Jan 2005 03:01:46 -0800." <20050118105945.M12726@vampextream.com> Date: Wed, 19 Jan 2005 01:36:35 +1100 Sender: Mark_Andrews@isc.org cc: freebsd-stable@freebsd.org Subject: Re: ruby and portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 14:36:57 -0000 > i am trying to do a portupgrade and after it running for 7 hrs and not doing > anything it quits with this error message. > > black-buity# portupgrade -aRrcCv > > ---> Reading default options: -v -D -l /var/tmp/portupgrade.results -L > /var/tmp/portupgrade-%s::%s.log > ---> Session started at: Sat, 15 Jan 2005 12:07:25 -0800 > [Updating the pkgdb in /var/db/pkg ... - 110 packages > found (-0 +23) ....................... done] > ---> Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert > nil into String (PkgDB::DBError) > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' > from /usr/local/sbin/portupgrade:674:in `main' > from /usr/local/sbin/portupgrade:207:in `initialize' > from /usr/local/sbin/portupgrade:207:in `new' > from /usr/local/sbin/portupgrade:207:in `main' > from /usr/local/sbin/portupgrade:1845 > black-buity# > > black-buity# ruby --version > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > black-buity# uname -a > FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri > Dec 10 14:50:33 PST 2004 > root@black-buity.vampextream.com:/usr/src/sys/i386/compile/VAMPEXTREAM i386 > black-buity# > > i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby > from 1.6 to 1.8 .. > so my quistions are > > 1. what would be causeing this?? The 7 hours were taken up by rebuilding the INDEX. The failure will be because your portupgrade is too old. 20041113: AUTHOR: portmgr@FreeBSD.org Since INDEX version in CVS is always too old, portmgr decided to remove it. You will still be able to build your own INDEX or use 'fetchindex' target in /usr/ports/. > 2. how do i fix this? pkg_delete portupgrade-\* (cd /usr/ports/sysutils/portupgrade; make install clean) > and thanks inadvance for any help on this issue/ error message > If you play the WindowsXP CD backwards, you get a Satanic message . That's > nothing. If you play it forwards, it installs WindowsXP! > > _______________________________________________ > 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" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 15:12:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D045416A4CE; Tue, 18 Jan 2005 15:12:20 +0000 (GMT) Received: from dgap-gw.mipt.ru (dgap-gw.mipt.ru [194.85.81.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 485C743D41; Tue, 18 Jan 2005 15:12:20 +0000 (GMT) (envelope-from nepal@nas.dgap.mipt.ru) Received: from localhost (unknown [127.0.0.1]) by dgap-gw.mipt.ru (Postfix) with ESMTP id 7DC9A60D9A06; Tue, 18 Jan 2005 18:08:16 +0300 (MSK) Received: from dgap-gw.mipt.ru ([127.0.0.1]) by localhost (dgap-gw.mipt.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16331-09; Tue, 18 Jan 2005 18:08:07 +0300 (MSK) Received: from nas.dgap.mipt.ru (nas.dgap.mipt.ru [194.85.81.203]) by dgap-gw.mipt.ru (Postfix) with ESMTP id E80CA60D9A01; Tue, 18 Jan 2005 18:08:07 +0300 (MSK) Received: from nas.dgap.mipt.ru (localhost [127.0.0.1]) by nas.dgap.mipt.ru (8.12.9p2/8.12.9) with ESMTP id j0IFH8f3026727; Tue, 18 Jan 2005 18:17:08 +0300 (MSK) (envelope-from nepal@nas.dgap.mipt.ru) Received: (from nepal@localhost) by nas.dgap.mipt.ru (8.12.9p2/8.12.9/Submit) id j0IFH8vL026726; Tue, 18 Jan 2005 18:17:08 +0300 (MSK) (envelope-from nepal) Date: Tue, 18 Jan 2005 18:17:07 +0300 From: "Andrew L. Neporada" To: Emanuel Strobl Message-ID: <20050118151707.GA26651@nas.dgap.mipt.ru> References: <200501181306.49120.emanuel.strobl@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501181306.49120.emanuel.strobl@gmx.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new-20030616-p8 (Gentoo) at dgap.mipt.ru X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=7.5 tests= X-Spam-Level: cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 15:12:21 -0000 On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > Dear experts, > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the > other one not (I hate to say it but both are working under win). > > The not working (more expensive) one gets recognized as ucom0 and I have > ucom0, also I can receive signal but not transmit. > [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer revision chip (tested under 4.10). > > -Harry Andrew. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 17:14:54 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF7F16A4CE for ; Tue, 18 Jan 2005 17:14:54 +0000 (GMT) Received: from sferics.mongueurs.net (sferics.mongueurs.net [81.80.147.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29F7843D2F for ; Tue, 18 Jan 2005 17:14:54 +0000 (GMT) (envelope-from david@landgren.net) Received: from [127.0.0.1] (exo.bpinet.com [81.80.147.206]) by sferics.mongueurs.net (Postfix) with ESMTP id CCD89AA09 for ; Tue, 18 Jan 2005 18:14:52 +0100 (CET) Message-ID: <41ED440C.9090401@landgren.net> Date: Tue, 18 Jan 2005 18:14:52 +0100 From: David Landgren Organization: The Lusty Decadent Delights of Imperial Pompeii User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Building your own FreeBSD installation CD-ROM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 17:14:55 -0000 List, (I asked this question last week on -questions but received zero answers. My apologies if this is the second time you are seeing this question). how does one go about creating a FreeBSD install CD-ROM? I'd like to be able to build my own CD-ROM with as much as possible of the install process done automatically. For instance, what parts of FreeBSD to install: X or not, games or not, etc. etc. And which ports to install straight away. I could also set up cfengine so that as soon as the machine came to life it could go and connect to my cfengine repository and download all the latest configurations to move into operational status. E.g., I'd like to just have to specify the partition layout, the name and IP of the machine, and its role(s): (web, dns, squid, mta, samba...) This would make rebuilding so much faster if a machine was catastrophically trashed. I could just hand someone a CD and a sheet of paper and they should be able to work it out by themselves without knowing too much about the ins and outs of FreeBSD. I could go on holidays without being stressed out. Thanks for any pointers to documentation on the subject, I'm sure people have done this before, but I can't coax the results out from my web searches. Thanks, David From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 17:27:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3C8E16A524 for ; Tue, 18 Jan 2005 17:27:03 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC5643D64 for ; Tue, 18 Jan 2005 17:26:58 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0IHQuPV029686; Tue, 18 Jan 2005 18:26:56 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0IHR5sU054859; Tue, 18 Jan 2005 18:27:05 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id j0IHR5xX054858; Tue, 18 Jan 2005 18:27:05 +0100 (CET) (envelope-from ftigeot) Date: Tue, 18 Jan 2005 18:27:05 +0100 From: Francois Tigeot To: David Landgren Message-ID: <20050118172705.GB54509@aoi.wolfpond.org> References: <41ED440C.9090401@landgren.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41ED440C.9090401@landgren.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: Building your own FreeBSD installation CD-ROM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 17:27:07 -0000 On Tue, Jan 18, 2005 at 06:14:52PM +0100, David Landgren wrote: > > how does one go about creating a FreeBSD install CD-ROM? I'd like to be > able to build my own CD-ROM with as much as possible of the install > process done automatically. For instance, what parts of FreeBSD to > install: X or not, games or not, etc. etc. And which ports to install > straight away. I could also set up cfengine so that as soon as the > machine came to life it could go and connect to my cfengine repository > and download all the latest configurations to move into operational status. There is some documentation in /usr/src/release on how to build a custom release (I did it successfully around 4.4 time). It is also possible to script the installer via a configuration file. Look at sysinstall(8) manpage for details. -- Francois Tigeot From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 17:44:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 064B216A4CE for ; Tue, 18 Jan 2005 17:44:37 +0000 (GMT) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB21643D48 for ; Tue, 18 Jan 2005 17:44:36 +0000 (GMT) (envelope-from buff@pobox.com) Received: by as2.dm.egate.net (Postfix, from userid 5562) id CA8064C23; Tue, 18 Jan 2005 12:44:35 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id C23794C1D; Tue, 18 Jan 2005 12:44:35 -0500 (EST) Date: Tue, 18 Jan 2005 12:44:35 -0500 (EST) From: William Denton X-X-Sender: buff@as2.dm.egate.net To: David Landgren In-Reply-To: <41ED440C.9090401@landgren.net> Message-ID: <20050118123935.R53021-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Building your own FreeBSD installation CD-ROM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 17:44:37 -0000 On 18 January 2005, David Landgren wrote: : how does one go about creating a FreeBSD install CD-ROM? I'd like to be : able to build my own CD-ROM with as much as possible of the install : process done automatically. The latter question I can't answer, but I made my own generic install CDs for 4.8-PRERELEASE in 2003 and got some help from the list. I wrote up what I did here, in the 18 April 2003 entry: http://www.miskatonic.org/freebsd.html (Sorry, no direct link to that entry.) I don't know how different things are for 5, and what I did was basic, but perhaps it'll be of use. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 19:09:26 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00C1C16A4CE for ; Tue, 18 Jan 2005 19:09:26 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id B14A443D46 for ; Tue, 18 Jan 2005 19:09:25 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from dialup84109-158.ip.peterstar.net ([84.204.109.158] helo=doom.homeunix.org) by voodoo.oberon.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43 (FreeBSD)) id 1Cqyis-000Du1-8V for freebsd-stable@freebsd.org; Tue, 18 Jan 2005 20:09:04 +0100 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.1/8.13.1) with ESMTP id j0IIuWb5002388; Tue, 18 Jan 2005 21:56:33 +0300 (MSK) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.1/8.13.1/Submit) id j0IIUBJY000893; Tue, 18 Jan 2005 21:30:11 +0300 (MSK) (envelope-from igor) Date: Tue, 18 Jan 2005 21:30:11 +0300 From: Igor Pokrovsky To: Tejas Kokje Message-ID: <20050118183011.GA867@doom.homeunix.org> Mail-Followup-To: Tejas Kokje , freebsd-stable@freebsd.org References: <41ECC3A7.8040300@ISI.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41ECC3A7.8040300@ISI.EDU> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 19:09:26 -0000 On Tue, Jan 18, 2005 at 12:07:03AM -0800, Tejas Kokje wrote: > Hi folks, > > I recently installed FreeBSD 5.3 stable. I got my sound > blaster live 5.1 sound card working with FreeBSD by adding > > device sound > device emu10k1 > > in the kernel configuration file. However the quality of > sound produced is of poor quality (not very clear) as compared to that > produced under Linux 2.6 series kernel. > > I remember having similar quality sound when OSS was used > with Linux Kernel. Is this poor quality because of OSS ? > Is ALSA ported to FreeBSD ? Or am I just using wrong driver ? I'm using latest OSS from opensound.org and the sound quality is perfect. -ip -- He who laughs last -- probably didn't get the joke. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 20:08:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D502016A4CE; Tue, 18 Jan 2005 20:08:47 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43BB543D1D; Tue, 18 Jan 2005 20:08:45 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0IK8gt16746; Wed, 19 Jan 2005 07:08:42 +1100 (EST) Date: Wed, 19 Jan 2005 07:08:41 +1100 (EST) From: Dave Horsfall To: FreeBSD STABLE list , freebsd-current@freebsd.org In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru> Message-ID: References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 20:08:48 -0000 On Tue, 18 Jan 2005, Andrew L. Neporada wrote: > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer > revision chip (tested under 4.10). Hmmm... That could explain something I saw. I've got two cables, bought from different vendors (same chipset). Both worked under 4.10, only one under 5.3 (different platforms). I'll try it when I get a moment. -- Dave From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 20:30:32 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A6BF16A565 for ; Tue, 18 Jan 2005 20:30:32 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE10243D39 for ; Tue, 18 Jan 2005 20:30:19 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Tue, 18 Jan 2005 12:30:19 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 08BE95D07 for ; Tue, 18 Jan 2005 12:30:19 -0800 (PST) To: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jan 2005 21:19:05 +0100." <200501172019.j0HKJ5gv033789@lurza.secnetix.de> Date: Tue, 18 Jan 2005 12:30:19 -0800 From: "Kevin Oberman" Message-Id: <20050118203019.08BE95D07@ptavv.es.net> Subject: Re: backporting tail from HEAD to RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 20:30:32 -0000 > Date: Mon, 17 Jan 2005 21:19:05 +0100 (CET) > From: Oliver Fromme > Sender: owner-freebsd-stable@freebsd.org > > Xin LI wrote: > > On Thu, Jan 13, 2005 at 01:01:44PM -0600, Doug Poland wrote: > > > Cool, I currently get this functionality from misc/xtail. xtail was on > > > my short list of "must-have" ports. > > > > Would you please share the list with us? I think it would be helpful > > if we know the needs :-) > > I'm surprised that nobody else replied. This is a list of > small non-X11 ports that I install on most machines (even > non-FreeBSD if applicable). This list is certainly not > complete, and everyone probably has his/her own favourite > tools. > > - cpdup (great to copy/sync directory trees) > - cvsup-without-gui (cannot use FreeBSD without it) > - elinks (nice text web browser, better than lynx) > - fping (useful to ping multiple hosts/nets at once) > - joe (my fav. editor, though I can cope with vi, too) > - logsurfer (useful tool to watch your logs) > - lsof (can't live without it) > - lynx-ssl (sometimes useful) > - netcat (well-known) > - nmap (well-known) > - omi (I use this one to mirror stuff via FTP) > - par (I use this often for mail / news) > - screen (can't live without it) > - strace (better than ktrace and truss, IMO) > - super (better than sudo, in my opinion) > - trafshow (very nice tool to watch network activity) > - zsh (my favourite shell, very powerful) > > Of course, lots of people will probably have different > opinions about some of those tools. But that's one of > the big advantages of FreeBSD and its ports collection: > You have enough things to chose from, so go and try them > to find the one which suits you best. :-) Excellent. I've used swatch for a long time, but I had missed logsurfer. I'll see how it does. One absolute requirement for me is most(1) which is more(1) than less(1). It handles binary files and has a number of very nice capabilities that less lacks, but wraps lines with a '\' at the wrap point which I find very annoying. But I still prefer it and, even when I try to type "more", my fingers insist on "most" at least once. Guess it's because I've been using most(1) for at least 15 years and probably closer to 20. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 21:37:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E52216A4CF for ; Tue, 18 Jan 2005 21:37:06 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F75043D67 for ; Tue, 18 Jan 2005 21:37:05 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 18 Jan 2005 21:37:04 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp027) with SMTP; 18 Jan 2005 22:37:04 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org, akiyama@jp.FreeBSD.org Date: Tue, 18 Jan 2005 22:36:48 +0100 User-Agent: KMail/1.7.2 References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru> In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1855474.mkKBfakOLZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501182236.54005.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: freebsd-stable@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 21:37:06 -0000 --nextPart1855474.mkKBfakOLZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > Dear experts, > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > the other one not (I hate to say it but both are working under win). > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately= =20 also breakes the 2.02 version :( Perhaps there's a goog guy out there who can refurbish the uplcom driver wi= th=20 this information (akiyama?)? Thanks a lot, =2DHarry > revision chip (tested under 4.10). > > > -Harry > > Andrew. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --nextPart1855474.mkKBfakOLZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7YF1Bylq0S4AzzwRAtrNAJ9OsLjuDIEayzEDk/l7JavN57NaXwCgg0dK IAZzcVHZEq3kHRaKohgwnGQ= =VwDM -----END PGP SIGNATURE----- --nextPart1855474.mkKBfakOLZ-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 22:02:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78A9616A4CE for ; Tue, 18 Jan 2005 22:02:51 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E63043D45 for ; Tue, 18 Jan 2005 22:02:51 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465 for ; Tue, 18 Jan 2005 14:02:51 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 39BB15D08 for ; Tue, 18 Jan 2005 14:02:50 -0800 (PST) To: stable@freebsd.org Date: Tue, 18 Jan 2005 14:02:50 -0800 From: "Kevin Oberman" Message-Id: <20050118220250.39BB15D08@ptavv.es.net> Subject: Fatal trap 12 on 5.3-Stable system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 22:02:51 -0000 On the command: ping6 -m -s 1460 node I get a panic with the following (hand transcribed): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present inruction pointer = 0x8:0xc052dc52 stack pointer = 0x10:0xdb31cc08 frame pointer = 0x10:-xdb31c44 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 = 1043 (ping6) [thread pid 1043 tid 100095 ] Stopped at soreceive+0x556: movl 0x4(%eax),%eax db> trace Tracing pid 1043 tid 100095 td 0xc21a47d0 soreceive(c2151b64,db31cc6c,db31cc78,0,c1c38500) at soreceive+0x556 recvit(c21a47d0,3,db31ccc0,0,c1b3d930) at recvit+0x1c7 recvmsg(c21a47d0,db31cd14,3,1,292) at recvmsg+0x5f syscall(bfbf002f,2f,bfbf002f,bfbfe82c,8077800,) at syscall+0x27b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (27, FreeBSD ELF32, recvmsg), eip = 0x280fb3d3, esp = 0xbfbfe76c,ebp = 0xbfbfecf4 --- Looks a lot like the large size might be over-writing something. Reproducable at will. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 22:57:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8CCE16A4CE for ; Tue, 18 Jan 2005 22:57:04 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3382F43D39 for ; Tue, 18 Jan 2005 22:57:04 +0000 (GMT) (envelope-from nomadlogic@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so44647rnf for ; Tue, 18 Jan 2005 14:57:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ehX5W+TdRl4GDIj/j5aVdO6a4ugTWhz3fyT4AOiyg6ujBGU6vkuE8p5IoKTsa6MyOTnvvtZR0f/94L9vwcTHxJv3ws5tSp+96PWF84iXRrQxob6QUEjXSxmAAwxGy83xc8DlQ6Q2IgeXw20SQ3z6LElvVtb9PEyp0A4Ie9pIDso= Received: by 10.38.83.58 with SMTP id g58mr261964rnb; Tue, 18 Jan 2005 14:57:01 -0800 (PST) Received: by 10.38.14.22 with HTTP; Tue, 18 Jan 2005 14:57:00 -0800 (PST) Message-ID: <57d71000050118145754c2182b@mail.gmail.com> Date: Tue, 18 Jan 2005 14:57:00 -0800 From: pete wright To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: make -jN test X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pete wright List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 22:57:04 -0000 (warning long post) Hi all, A recent thread on a I subscribe to in regard to the usefullness of using the -j flag on a make world led me to run a test over the weekend just to see it's effectiveness. This is the section of the handbook that started it all for me: (from: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html) "It is now possible to specify a -j option to make which will cause it to spawn several simultaneous processes. This is most useful on multi-CPU machines. However, since much of the compiling process is IO bound rather than CPU bound it is also useful on single CPU machines. On a typical single-CPU machine you would run: # make -j4 buildworld make(1) will then have up to 4 processes running at any one time. Empirical evidence posted to the mailing lists shows this generally gives the best performance benefit. If you have a multi-CPU machine and you are using an SMP configured kernel try values between 6 and 10 and see how they speed things up." So to test this out I wrote a shell script to time a make -jN buildworld where N = a number from 1-8. The idea is to see if there is any speedup between running make -j1 and make -j8 on a dual proc box. Now this is not scientific, altho maybe the findings are typical for a low system load box. I also had the box sleep for 60 secs between each build. Here are my timings: building world with 1 jobs... real 95m20.543s user 83m18.550s sys 13m20.120s cleaning /usr/src.... building world with 2 jobs... real 54m15.856s user 84m42.337s sys 16m39.216s cleaning /usr/src.... building world with 3 jobs... real 53m53.239s user 85m12.189s sys 17m13.039s cleaning /usr/src.... building world with 4 jobs... real 53m56.539s user 85m22.767s sys 17m22.433s cleaning /usr/src.... building world with 5 jobs... real 54m10.993s user 85m30.995s sys 17m14.160s cleaning /usr/src.... building world with 6 jobs... real 54m10.814s user 85m24.063s sys 17m27.437s cleaning /usr/src.... building world with 7 jobs... real 54m15.289s user 85m25.479s sys 17m27.751s cleaning /usr/src.... building world with 8 jobs... real 54m23.526s user 85m27.173s sys 17m28.891s As you can tell there does not seem to be a rampup after a make -j2 buildworld. This is a SMP system, with stripped scisi disks (altho the controller is GIANT locked....maybe this is preventing additional gains?). For completness here is my dmesg: Copyright (c) 1992-2005 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 5.3-STABLE #1: Tue Jan 4 19:06:52 EST 2005 root@host.mydomain.org:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU - S 1266MHz (1263.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Stepping = 4 Features=0x383fbff real memory = 1610530816 (1535 MB) avail memory = 1568518144 (1495 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 1.0 (no driver attached) fxp0: port 0x2200-0x223f mem 0xfea00000-0xfeafffff,0xfeb7f000-0xfeb7ffff irq 27 at device 2.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:09:6b:9a:12:13 fxp1: port 0x2240-0x227f mem 0xfe900000-0xfe9fffff,0xfeb7e000-0xfeb7efff irq 25 at device 10.0 on pci0 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:09:6b:9a:12:14 isab0: port 0x440-0x44f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x700-0x70f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xfeb7d000-0xfeb7dfff irq 7 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: pcibus 1 on motherboard pci1: on pcib1 pci1: at device 3.0 (no driver attached) ips0: mem 0xedffe000-0xedffffff irq 20 at device 5.0 on pci1 ips0: [GIANT-LOCKED] cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xcc800-0xd47ff,0xcb000-0xcc7ff,0xc0000-0xcafff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A 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 unknown: can't assign resources (port) ppc1: parallel port not found. unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec acd0: CDROM at ata0-master UDMA33 ips0: adapter type: ServeRAID 4Lx (neo lite) ips0: logical drives: 1 ips0: Logical Drive 0: RAID1 sectors: 71096320, state OK ipsd0: on ips0 ipsd0: Logical Drive (34715MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a So, unless I misread the section of the handbook, I should be seeing a decrease in time for these buldworlds but am not. Any idea why this is not happening. Cheers, Pete Wright -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:04:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A14016A4CE for ; Tue, 18 Jan 2005 23:04:07 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id C368543D41 for ; Tue, 18 Jan 2005 23:04:06 +0000 (GMT) (envelope-from olivier.certner@free.fr) Received: from lon92-2-82-226-188-149.fbx.proxad.net (unknown [82.226.188.149]) by postfix3-2.free.fr (Postfix) with ESMTP id 33C38C113 for ; Wed, 19 Jan 2005 00:04:06 +0100 (CET) From: Olivier Certner To: freebsd-stable@freebsd.org Date: Wed, 19 Jan 2005 00:03:20 +0100 User-Agent: KMail/1.7 References: <41ECC3A7.8040300@ISI.EDU> In-Reply-To: <41ECC3A7.8040300@ISI.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501190003.20614.olivier.certner@free.fr> Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 23:04:07 -0000 Hi, Do you mean that the sound seems unclear all the time? I've also had some problems with sound on my FreeBSD 5.3-STABLE, but a different kind of. Sometimes I hear crakings while playing mp3 files with XMMS, although my computer's load is very low. I use "snd_emu10k1" sound module as you do with a Creative Sound Blaster Live! 5.1. There is another driver that may be worth trying here: http://chibis.persons.gfk.ru/audigy/. I'll give it a pick when I get more time. Cheers, Olivier From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:17:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F4F516A4CE for ; Tue, 18 Jan 2005 23:17:07 +0000 (GMT) Received: from eskimo.tundraware.com (eskimo.tundraware.com [64.2.229.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B05343D46 for ; Tue, 18 Jan 2005 23:17:04 +0000 (GMT) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by eskimo.tundraware.com (8.13.1/8.13.1) with ESMTP id j0INGvGI098072 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 18 Jan 2005 17:16:58 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <41ED98E9.10401@tundraware.com> Date: Tue, 18 Jan 2005 17:16:57 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner: Found to be clean X-MailScanner-From: tundra@tundraware.com Subject: Possible Problem w/4.10-stable And SMBFS? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: tundra@tundraware.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 23:17:07 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am seeing a number of intermittent problems with SMBFS-mounted partitions and am wondering if these are know FBSD problems or problems with the Win32 servers: 1) After running for a very long time (weeks), SMBFS-connected directories ~ become very slow/sluggish for read/write. A reboot of the FBSD machine ~ fixes this. Error log shows: ~ Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15734 ~ Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15736 ~ This machine is running 4.11-PRERELEASE as of 12/14/2004 2) Again, after running for a long time (several weeks), attempts to ~ to long running I/O against an SBMFS-mounted partition, I get ~ a bus error and the following entries in /var/log/messages: ~ Jan 18 16:45:49 xyz /kernel: smb_iod_recvall: drop resp with mid 34907 ~ Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 39329 ~ Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 42496 ~ This seems to be a problem primarily with very large files (100s of ~ megs to several gigs) - at least I've not seen this problem w/small ~ files. ~ This machine is running 4.10-STABLE as of 11/30/2004 Ideas would be appreciated... - -- - ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFB7ZjpyjgA+Mact+YRAgmVAJ9V90kdxogkmixMGGL259Phz75tuQCdEmu+ hdSY/kUNVsvpBiGlil/kiko= =psGE -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:19:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9D5A16A4CE for ; Tue, 18 Jan 2005 23:19:47 +0000 (GMT) Received: from smtp13.wxs.nl (smtp13.wxs.nl [195.121.6.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 438AA43D5A for ; Tue, 18 Jan 2005 23:19:47 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-stable@freebsd.org; Wed, 19 Jan 2005 00:19:46 +0100 (CET) Received: (qmail 22826 invoked from network); Tue, 18 Jan 2005 23:19:44 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Tue, 18 Jan 2005 23:19:44 +0000 Received: (qmail 948 invoked from network); Tue, 18 Jan 2005 23:19:25 +0000 Received: from localhost (HELO smtp.local) (127.0.0.1) by localhost with SMTP; Tue, 18 Jan 2005 23:19:25 +0000 Date: Wed, 19 Jan 2005 00:19:23 +0100 From: Ronald Klop In-reply-to: <200501190003.20614.olivier.certner@free.fr> To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41ECC3A7.8040300@ISI.EDU> <200501190003.20614.olivier.certner@free.fr> Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 23:19:47 -0000 On Wed, 19 Jan 2005 00:03:20 +0100, Olivier Certner wrote: > Hi, > > Do you mean that the sound seems unclear all the time? > > I've also had some problems with sound on my FreeBSD 5.3-STABLE, but a > different kind of. Sometimes I hear crakings while playing mp3 files with > XMMS, although my computer's load is very low. I use "snd_emu10k1" sound > module as you do with a Creative Sound Blaster Live! 5.1. > > There is another driver that may be worth trying here: > http://chibis.persons.gfk.ru/audigy/. I'll give it a pick when I get more > time. I have problems also with sb live. There was discussion before that increasing some buffer in the driver made the problem less. And enabling PREEMPTION would help also. But since the last discussion I got my onboard audio (ESS) working, which is ok for me. I also wondered that the snd_emu10k1 is marked as MPSAFE, while other sound drivers aren't, but the others perform better. But I don't know if it has anything to do with it. Search the archives for more discussion about this. Ronald. -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:23:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A189316A4CE for ; Tue, 18 Jan 2005 23:23:46 +0000 (GMT) Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A33C43D2D for ; Tue, 18 Jan 2005 23:23:46 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-stable@freebsd.org; Wed, 19 Jan 2005 00:23:45 +0100 (CET) Received: (qmail 22854 invoked from network); Tue, 18 Jan 2005 23:23:43 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Tue, 18 Jan 2005 23:23:43 +0000 Received: (qmail 968 invoked from network); Tue, 18 Jan 2005 23:23:24 +0000 Received: from localhost (HELO smtp.local) (127.0.0.1) by localhost with SMTP; Tue, 18 Jan 2005 23:23:24 +0000 Date: Wed, 19 Jan 2005 00:23:23 +0100 From: Ronald Klop In-reply-to: <41ED98E9.10401@tundraware.com> To: tundra@tundraware.com, freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41ED98E9.10401@tundraware.com> Subject: Re: Possible Problem w/4.10-stable And SMBFS? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 23:23:46 -0000 On Tue, 18 Jan 2005 17:16:57 -0600, Tim Daneliuk wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am seeing a number of intermittent problems with SMBFS-mounted > partitions > and am wondering if these are know FBSD problems or problems with the > Win32 servers: > > 1) After running for a very long time (weeks), SMBFS-connected > directories > ~ become very slow/sluggish for read/write. A reboot of the FBSD > machine > ~ fixes this. Error log shows: > > ~ Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid > 15734 > ~ Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid > 15736 > > ~ This machine is running 4.11-PRERELEASE as of 12/14/2004 > > > 2) Again, after running for a long time (several weeks), attempts to > ~ to long running I/O against an SBMFS-mounted partition, I get > ~ a bus error and the following entries in /var/log/messages: > > ~ Jan 18 16:45:49 xyz /kernel: smb_iod_recvall: drop resp with mid > 34907 > ~ Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid > 39329 > ~ Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid > 42496 > > ~ This seems to be a problem primarily with very large files (100s of > ~ megs to several gigs) - at least I've not seen this problem w/small > ~ files. > > ~ This machine is running 4.10-STABLE as of 11/30/2004 > > > Ideas would be appreciated... Do you have any statistics about memory consumption/swapping? top/vmstat/netstat -m What is the cpu usage? What is the number of open files in your system? -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:25:30 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0415416A4CE for ; Tue, 18 Jan 2005 23:25:30 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71E5F43D3F for ; Tue, 18 Jan 2005 23:25:27 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 66B278566C; Wed, 19 Jan 2005 09:55:25 +1030 (CST) Date: Wed, 19 Jan 2005 09:55:25 +1030 From: Greg 'groggy' Lehey To: Craig Boston , David Elsing , freebsd-stable@freebsd.org Message-ID: <20050118232525.GW79181@wantadilla.lemis.com> References: <20050118143302.GA99345@nowhere> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YwTTlJgQ7QoYB9ta" Content-Disposition: inline In-Reply-To: <20050118143302.GA99345@nowhere> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Subject: Re: Vinum Raid5 Init question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Jan 2005 23:25:30 -0000 --YwTTlJgQ7QoYB9ta Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 18 January 2005 at 8:33:03 -0600, Craig Boston wrote: > On Tue, Jan 18, 2005 at 12:21:59PM +0100, David Elsing wrote: >> Quote from the manual of the 4th example of the chapter "HOW TO SET UP VINUM": >> "In addition, the volume specification includes the keyword >> setupstate, which ensures that all plexes are up after creation." Where does it tell you to do that? From the man page: setstate state [volume | plex | subdisk | drive] setstate sets the state of the specified objects to the specified state. This bypasses the usual consistency mechanism of vinum and should be used only for recovery purposes. It is possible to crash the system by incorrect use of this command. >> But a couple of weeks later I read the following in the manual: >> >> "Note that you must use the init command with RAID-5 plexes: otherwise >> extreme data corruption will result if one subdisk fails." > > Yes, this particular gotcha bit me a while back and I lost quite a bit > of data (my fault for not having good backups) due to it. IMO, I still > consider it a documentation bug though. That particular bit is buried > in a command reference section rather than being in bold in the "HOW TO" > guide. Yes, it could be clearer. Put in a PR. >> I read this to my horror after I filled the volume with data. You'll >> probably noticed I didn't init my volume. The disks are in good >> condition. The volume is almost filled to the maximum capacity. So a >> backup is a bit difficult due to the size of it. Are there any other >> options? If one disks fails, do I still get corrupted data? > > Yes, if one disk fails for any reason, every third sector will be > garbage and it's unlikely you'll be able to recover anything useful from > it. > > I would highly recommend backing up whatever is critically important to > you asap. If you like living dangerously and all the drives are in good > health, the parity data can be (theoretically) repaired with the "vinum > rebuildparity" command, but do so at your own risk... That did allow me > to recover a couple of my partitions that hadn't been trashed yet. This should work. Make sure the volume is not be mounted when you do so. > Also, if a good disk gets marked as "down" somehow before you can > correct this, whatever you do, do NOT issue a "vinum start" command > on it. In the current state of the array, that would be destructive > and irreversible. No, that's the correct way to do it. > That's what happened to me: ATA timeout caused one of the drives to > temporarily detach, corrupt filesystems caused a panic. If this > happens, you're better off using setstate to force it to up, as > wrong as that would normally be. I can't recall seeing a problem report. Greg -- See complete headers for address and phone numbers. --YwTTlJgQ7QoYB9ta Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB7ZrlIubykFB6QiMRAr9iAJ9kS0NrFM6JIAp19HC9cfntYo86AwCaA7HO Gm3vYbGKJrVdqLgeWrrAFlM= =Lj0q -----END PGP SIGNATURE----- --YwTTlJgQ7QoYB9ta-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 23:30:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1BFF16A4CE for ; Tue, 18 Jan 2005 23:30:20 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32CDF43D31 for ; Tue, 18 Jan 2005 23:30:20 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so45286rne for ; Tue, 18 Jan 2005 15:30:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=XFvoCMRGoVffOzLIIBAUHLSthgfzQZz0cD8adAWXzqEvVy1a3l1qJxmolCn7O2FTh7r9eFnNa4YX0hVgGzrD3QpqC/9azrZRI3NgKaJQmUbKM5J6PglUUDHkJompp4pX7+moXZT3J8wrHNSAAMK47TwQnnZJUdDomN0Fqj3+zhg= Received: by 10.38.72.28 with SMTP id u28mr1443rna; Tue, 18 Jan 2005 15:30:19 -0800 (PST) Received: by 10.39.1.45 with HTTP; Tue, 18 Jan 2005 15:30:19 -0800 (PST) Message-ID: <3aaaa3a0501181530975fecf@mail.gmail.com> Date: Tue, 18 Jan 2005 23:30:19 +0000 From: Chris To: Matthias Buelow In-Reply-To: <41ECBED0.8000704@incubus.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> <20050117224809.GC31463@xor.obsecurity.org> <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> <41ECBED0.8000704@incubus.de> cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 23:30:20 -0000 I have been compiling ports using -O2 since I started using FreeBSD back in 2003 and only port that has had issues with this is lang/ezm3 in FreeBSD 5.2.1 it needed -O. Chris On Tue, 18 Jan 2005 08:46:24 +0100, Matthias Buelow wrote: > Mike Tancsa wrote: > > At 05:48 PM 17/01/2005, Kris Kennaway wrote: > > > > Like I said before, switching back to -O makes the system stable once > > again. I let it run continuous buildworlds without issue for 24hrs > > along with burnP6, and memtest running in the background. No problem. > > Then I'd leave it at that. The difference between gcc -O2 and -O is > marginal at best. Think of it as -O being the large axe that chops off > a huge slab, and -O2 being the large axe, followed by some scratching > with a nail-file. Most of the time it isn't worth the effort. > > mkb. > _______________________________________________ > 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 Wed Jan 19 00:17:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E0AF16A4DD for ; Wed, 19 Jan 2005 00:17:04 +0000 (GMT) Received: from nabi1.snu.ac.kr (nabi1.snu.ac.kr [147.46.100.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id B370843D1D for ; Wed, 19 Jan 2005 00:17:03 +0000 (GMT) (envelope-from lahaye@snu.ac.kr) Received: from [147.46.100.31] ([147.46.100.31]) by nabi1.snu.ac.kr ([147.46.100.51]) with ESMTP id 2005011909:18:16:087436.29014.3051944880 for ; Wed, 19 Jan 2005 09:18:16 +0900 (KST) Received: from [147.46.44.181] (lahaye@snu.ac.kr) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2005011909:16:53:441464.21525.1386216368 for ; Wed, 19 Jan 2005 09:16:53 +0900 (KST) Message-ID: <41EDA6FB.6000706@snu.ac.kr> Date: Wed, 19 Jan 2005 09:16:59 +0900 From: Rob Lahaye User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: spamrefuse@yahoo.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:18.08) (by Terrace) cc: freebsd-stable@freebsd.org Subject: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 00:17:04 -0000 Hi, As a regular user, I have a cron job; 'crontab -l' says: ----------------------------------------- SHELL=/bin/sh MAILTO="" # run at bootup and then every 5 minutes @reboot $HOME/bin/ssh_tunnel */5 * * * * $HOME/bin/ssh_tunnel ----------------------------------------- The ssh_tunnel is an sh-script, which checks whether a particular ssh-tunnel still exists, and if not regenerates it, as follows: #!/bin/sh #---------------- ssh_tunnel script --------- tunnel="-L 55110:localhost:110 pop3.univ.net" tunnel_up=`pgrep -f -- "${tunnel}"` [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} It works beautifully, but why does this also generate one zombie process: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 The "STARTED" time, is when the PC rebooted last time. When I remove the cronjob and reboot, the zombie process is not created anymore. Any idea what's the problem here? Thanks, Rob. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 00:21:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5330516A4CE; Wed, 19 Jan 2005 00:21:51 +0000 (GMT) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E64A43D46; Wed, 19 Jan 2005 00:21:51 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (mail, from userid 1001) id C878A2A98B; Tue, 18 Jan 2005 18:21:50 -0600 (CST) Date: Tue, 18 Jan 2005 18:21:48 -0600 From: Craig Boston To: Greg 'groggy' Lehey Message-ID: <20050119002148.GA1328@nowhere> Mail-Followup-To: Craig Boston , Greg 'groggy' Lehey , David Elsing , freebsd-stable@freebsd.org References: <20050118143302.GA99345@nowhere> <20050118232525.GW79181@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050118232525.GW79181@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: David Elsing Subject: Re: Vinum Raid5 Init question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 00:21:51 -0000 On Wed, Jan 19, 2005 at 09:55:25AM +1030, Greg 'groggy' Lehey wrote: > Yes, it could be clearer. Put in a PR. I'm more than willing to submit a patch if it will help, but will it do any good this late in the release cycle? Especially if there will be no 4.12 release. > > Also, if a good disk gets marked as "down" somehow before you can > > correct this, whatever you do, do NOT issue a "vinum start" command > > on it. In the current state of the array, that would be destructive > > and irreversible. > > No, that's the correct way to do it. Normally it would be, yes. However in this case (at least it was for me), all of the normal blocks are fine, but the parity blocks are random garbage since init was never run. If a drive goes into the "down" state for some reason but is physically fine, starting the subdisk will begin "reconstructing" the data from the bogus parity, wiping out any hope of recovering the good data. If a drive does get detached somehow, it's likely that the system won't stay up very long -- from its point of view at least one filesystem has suddenly become very corrupt. The setstate is dangerous and will probably result in a somewhat inconsistent filesystem, but it's still preferable to a total loss... > I can't recall seeing a problem report. There wasn't one. I had encountered the problem on several machines in a short timespan (fortunately only one had anything important) so I asked you about in in private mail. I didn't think the problem was with FreeBSD or vinum itself -- it was more of a "what am I doing wrong?" question. After a couple rounds you determined that it was likely I hadn't run vinum init, and sure enough that's what it was. Sorry, I can't provide a time reference. At the time of the exchange my mail archive was down (that's what was on the doomed filesystem :). Craig From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 00:49:00 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D36D16A4CF for ; Wed, 19 Jan 2005 00:49:00 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA1C643D41 for ; Wed, 19 Jan 2005 00:48:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 00C86513CE; Tue, 18 Jan 2005 16:48:58 -0800 (PST) Date: Tue, 18 Jan 2005 16:48:58 -0800 From: Kris Kennaway To: Chris Message-ID: <20050119004858.GA46389@xor.obsecurity.org> References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> <20050117224809.GC31463@xor.obsecurity.org> <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> <41ECBED0.8000704@incubus.de> <3aaaa3a0501181530975fecf@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <3aaaa3a0501181530975fecf@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: Matthias Buelow Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 00:49:00 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jan 18, 2005 at 11:30:19PM +0000, Chris wrote: > I have been compiling ports using -O2 since I started using FreeBSD > back in 2003 and only port that has had issues with this is lang/ezm3 > in FreeBSD 5.2.1 it needed -O. Do yourself a favour and use -O2 -fno-strict-alias instead, because some ports *are broken* with plain -O2. Kris --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7a56Wry0BWjoQKURAoH+AJ98++/Mi6wVxd/x3ozt49yrpjOl5gCgr7RY udUSlTukcILJEk3c25RlTyI= =rpNX -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 01:31:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 904E416A4CE for ; Wed, 19 Jan 2005 01:31:07 +0000 (GMT) Received: from nabi1.snu.ac.kr (nabi1.snu.ac.kr [147.46.100.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23E3C43D2D for ; Wed, 19 Jan 2005 01:31:07 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.100.31] ([147.46.100.31]) by nabi1.snu.ac.kr ([147.46.100.51]) with ESMTP id 2005011910:32:19:562802.29014.3038763952 for ; Wed, 19 Jan 2005 10:32:19 +0900 (KST) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2005011910:30:55:721301.21525.2656234416 for ; Wed, 19 Jan 2005 10:30:55 +0900 (KST) Message-ID: <41EDB857.6020009@yahoo.com> Date: Wed, 19 Jan 2005 10:31:03 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: spamrefuse@yahoo.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:4.33) (by Terrace) cc: freebsd-stable@freebsd.org Subject: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 01:31:07 -0000 Hi, As a regular user, I have a cron job; 'crontab -l' says: ----------------------------------------- SHELL=/bin/sh MAILTO="" # run at bootup and then every 5 minutes @reboot $HOME/bin/ssh_tunnel */5 * * * * $HOME/bin/ssh_tunnel ----------------------------------------- The ssh_tunnel is an sh-script, which checks whether a particular ssh-tunnel still exists, and if not regenerates it, as follows: #!/bin/sh #---------------- ssh_tunnel script --------- tunnel="-L 55110:localhost:110 pop3.univ.net" tunnel_up=`pgrep -f -- "${tunnel}"` [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} It works beautifully, but why does this also generate one zombie process: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 The "STARTED" time, is when the PC rebooted last time. When I remove the cronjob and reboot, the zombie process is not created anymore. Any idea what's the problem here? Thanks, Rob. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 03:09:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4369816A4CE for ; Wed, 19 Jan 2005 03:09:34 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5418543D48 for ; Wed, 19 Jan 2005 03:09:33 +0000 (GMT) (envelope-from admin@intercorner.net) Received: from mail.intercorner.net ([85.224.73.80] [85.224.73.80]) by mxfep02.bredband.com with ESMTP <20050119030931.UEPR12890.mxfep02.bredband.com@mail.intercorner.net> for ; Wed, 19 Jan 2005 04:09:31 +0100 X-Spam-Status: No, hits=0.5 required=5.0 tests=PRIORITY_NO_NAME X-Spam-Level: Received: from localhost by mail.intercorner.net; Wed, 19 Jan 2005 04:11:40 +0100 Date: Wed, 19 Jan 2005 04:11:40 +0100 Message-ID: MIME-Version: 1.0 From: "Admin @ InterCorner" To: freebsd-stable@freebsd.org X-Priority: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: FreeBSD 5.3-STABLE kernel panic at boot-time X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 03:09:34 -0000 Hi there! I have gladly installed FreeBSD5 on my laptop to be free from M$ !! :D And soon I will install it on my worksation aswell. Here is (In my eyes) an unusual bootup error. When I start my laptop everything is fine untill I have to choose how I w= ant to boot FreeBSD. As a first try I choosed the default option just to = see everything is working with the new kernel. It didn't.. I then tryed to boot with ACPI (choise nr 2 at the bootmenu), and everyth= ing started upp nicely. I normally only want to run with ACPI enabled, so it's not a large proble= m for me.. but maby for someone else? I have two questions.. 1: Is there something wrong with my kernelconfig or is it a bug? 2: How do I change the default boot procedure from "menu nr 1 (w/o ACPI)"= to "menu nr 2 (w/ ACPI)"? I left some useful information at the bottom of this message. And here are a webpage that shows some information about my harware: http://support.packardbell.com/se/mypc/index.php?sernr=3D105601500123# Thanks! Anders --- START OF Boot without ACPI (default) --- Jan 19 03:05:38 laptop syslogd: kernel boot file is /boot/kernel/kernel Jan 19 03:05:38 laptop kernel: Copyright (c) 1992-2005 The FreeBSD Projec= t. Jan 19 03:05:38 laptop kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988= , 1989, 1991, 1992, 1993, 1994 Jan 19 03:05:38 laptop kernel: The Regents of the University of Californi= a. All rights reserved. Jan 19 03:05:38 laptop kernel: FreeBSD 5.3-STABLE #0: Sat Jan 15 21:23:58= CET 2005 Jan 19 03:05:38 laptop kernel: root@laptop.intercorner.net:/usr/obj/usr/s= rc/sys/HAGGE Jan 19 03:05:38 laptop kernel: Timecounter "i8254" frequency 1193182 Hz q= uality 0 Jan 19 03:05:38 laptop kernel: CPU: mobile AMD Athlon(tm) XP 1600+ Proces= sor (1400.06-MHz 686-class CPU) Jan 19 03:05:38 laptop kernel: Origin =3D "AuthenticAMD" Id =3D 0x680 S= tepping =3D 0 Jan 19 03:05:38 laptop kernel: Features=3D0x383f9ff Jan 19 03:05:38 laptop kernel: AMD Features=3D0xc0480000 Jan 19 03:05:38 laptop kernel: real memory =3D 234815488 (223 MB) Jan 19 03:05:38 laptop kernel: avail memory =3D 224317440 (213 MB) Jan 19 03:05:38 laptop kernel: npx0: [FAST] Jan 19 03:05:38 laptop kernel: npx0: on motherboard Jan 19 03:05:38 laptop kernel: npx0: INT 16 interface Jan 19 03:05:38 laptop kernel: pcib0: pcibus 0 on mo= therboard Jan 19 03:05:38 laptop kernel: pir0: on motherboard Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 5 for 0.17.INTC is not vali= d for link 0x3 Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 11 for 0.11.INTA is not val= id for link 0x3 Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 10 for 0.18.INTA is not val= id for link 0x3 Jan 19 03:05:38 laptop kernel: pci0: on pcib0 Jan 19 03:05:38 laptop kernel: agp0: mem 0xa0000000-0xa3ffffff at device 0.0 on pci0 Jan 19 03:05:38 laptop kernel: pcib1: at device 1.0 on p= ci0 Jan 19 03:05:38 laptop kernel: pci1: on pcib1 Jan 19 03:05:38 laptop kernel: pci1: at device 0.0 (no dri= ver attached) Jan 19 03:05:38 laptop kernel: cbb0: at devic= e 8.0 on pci0 Jan 19 03:05:38 laptop kernel: cardbus0: on cbb0 Jan 19 03:05:38 laptop kernel: pccard0: <16-bit PCCard bus> on cbb0 Jan 19 03:05:38 laptop kernel: Jan 19 03:05:38 laptop kernel: Jan 19 03:05:38 laptop kernel: Fatal trap 12: page fault while in kernel = mode Jan 19 03:05:38 laptop kernel: fault virtual address =3D 0xe7fe6 Jan 19 03:05:38 laptop kernel: fault code =3D supervisor re= ad, page not present Jan 19 03:05:38 laptop kernel: instruction pointer =3D 0x8:0xc00e9eb= 5 Jan 19 03:05:38 laptop kernel: stack pointer =3D 0x10:0xc08219= 3c Jan 19 03:05:38 laptop kernel: frame pointer =3D 0x10:0xc08219= 3c Jan 19 03:05:38 laptop kernel: code segment =3D base 0x0, lim= it 0xfffff, type 0x1b Jan 19 03:05:38 laptop kernel: =3D DPL 0, pres 1, def32 1, gran 1 Jan 19 03:05:38 laptop kernel: processor eflags =3D interrupt enabled, re= sume, IOPL =3D 0 Jan 19 03:05:38 laptop kernel: current process =3D 0 (swapper) Jan 19 03:05:38 laptop kernel: trap number =3D 12 Jan 19 03:05:38 laptop kernel: panic: page fault Jan 19 03:05:38 laptop kernel: Uptime: 1s Jan 19 03:05:38 laptop kernel: Automatic reboot in 15 seconds - press a k= ey on the console to abort Jan 19 03:05:38 laptop kernel: Rebooting... --- END OF Boot without ACPI (default) --- --- START OF Boot with ACPI (Choise nr 2) --- Jan 19 03:05:38 laptop kernel: Copyright (c) 1992-2005 The FreeBSD Projec= t. Jan 19 03:05:38 laptop kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988= , 1989, 1991, 1992, 1993, 1994 Jan 19 03:05:38 laptop kernel: The Regents of the University of Californi= a. All rights reserved. Jan 19 03:05:38 laptop kernel: FreeBSD 5.3-STABLE #0: Sat Jan 15 21:23:58= CET 2005 Jan 19 03:05:38 laptop kernel: root@laptop.intercorner.net:/usr/obj/usr/s= rc/sys/HAGGE Jan 19 03:05:38 laptop kernel: Timecounter "i8254" frequency 1193182 Hz q= uality 0 Jan 19 03:05:38 laptop kernel: CPU: mobile AMD Athlon(tm) XP 1600+ Proces= sor (1400.06-MHz 686-class CPU) Jan 19 03:05:38 laptop kernel: Origin =3D "AuthenticAMD" Id =3D 0x680 S= tepping =3D 0 Jan 19 03:05:38 laptop kernel: Features=3D0x383f9ff Jan 19 03:05:38 laptop kernel: AMD Features=3D0xc0480000 Jan 19 03:05:38 laptop kernel: real memory =3D 234815488 (223 MB) Jan 19 03:05:38 laptop kernel: avail memory =3D 220123136 (209 MB) Jan 19 03:05:38 laptop kernel: npx0: [FAST] Jan 19 03:05:38 laptop kernel: npx0: on motherboard Jan 19 03:05:38 laptop kernel: npx0: INT 16 interface Jan 19 03:05:38 laptop kernel: acpi0: on motherboard Jan 19 03:05:38 laptop kernel: acpi0: Power Button (fixed) Jan 19 03:05:38 laptop kernel: acpi_ec0: p= ort 0x66,0x62 on acpi0 Jan 19 03:05:38 laptop kernel: Timecounter "ACPI-fast" frequency 3579545 = Hz quality 1000 Jan 19 03:05:38 laptop kernel: acpi_timer0: <24-bit timer at 3.579545MHz>= port 0x1008-0x100b on acpi0 Jan 19 03:05:38 laptop kernel: cpu0: on acpi0 Jan 19 03:05:38 laptop kernel: acpi_button0: on acpi0 Jan 19 03:05:38 laptop kernel: acpi_lid0: on = acpi0 Jan 19 03:05:38 laptop kernel: acpi_acad0: on acpi0 Jan 19 03:05:38 laptop kernel: acpi_cmbat0: on a= cpi0 Jan 19 03:05:38 laptop kernel: pcib0: port 0xcf8-0= xcff on acpi0 Jan 19 03:05:38 laptop kernel: pci0: on pcib0 Jan 19 03:05:38 laptop kernel: agp0: mem 0xa0000000-0xa3ffffff at device 0.0 on pci0 Jan 19 03:05:38 laptop kernel: pcib1: at device 1.0= on pci0 Jan 19 03:05:38 laptop kernel: pci1: on pcib1 Jan 19 03:05:38 laptop kernel: pci1: at device 0.0 (no dri= ver attached) Jan 19 03:05:38 laptop kernel: cbb0: at devic= e 8.0 on pci0 Jan 19 03:05:38 laptop kernel: cardbus0: on cbb0 Jan 19 03:05:38 laptop kernel: pccard0: <16-bit PCCard bus> on cbb0 Jan 19 03:05:38 laptop kernel: fwohci0: mem 0xf0001000-0= xf0001fff irq 5 at device 11.0 on pci0 Jan 19 03:05:38 laptop kernel: fwohci0: OHCI version 1.0 (ROM=3D1) Jan 19 03:05:38 laptop kernel: fwohci0: No. of Isochronous channels is 4.= Jan 19 03:05:38 laptop kernel: fwohci0: EUI64 00:40:d0:01:00:0b:8c:fc Jan 19 03:05:38 laptop kernel: fwohci0: Phy 1394a available S400, 2 ports= . Jan 19 03:05:38 laptop kernel: fwohci0: Link S400, max_rec 1024 bytes. Jan 19 03:05:38 laptop kernel: fwohci0: max_rec 1024 -> 2048 Jan 19 03:05:38 laptop kernel: firewire0: on fwo= hci0 Jan 19 03:05:38 laptop kernel: fwe0: on firewire= 0 Jan 19 03:05:38 laptop kernel: if_fwe0: Fake Ethernet address: 02:40:d0:0= b:8c:fc Jan 19 03:05:38 laptop kernel: fwe0: Ethernet address: 02:40:d0:0b:8c:fc Jan 19 03:05:38 laptop kernel: fwe0: if_start running deferred for Giant Jan 19 03:05:38 laptop kernel: fwohci0: Initiate bus reset Jan 19 03:05:38 laptop kernel: fwohci0: node_id=3D0xc000ffc0, gen=3D1, CY= CLEMASTER mode Jan 19 03:05:38 laptop kernel: firewire0: 1 nodes, maxhop <=3D 0, cable I= RM =3D 0 (me) Jan 19 03:05:38 laptop kernel: firewire0: bus manager 0 (me) Jan 19 03:05:38 laptop kernel: isab0: at device 17.0 on = pci0 Jan 19 03:05:38 laptop kernel: isa0: on isab0 Jan 19 03:05:38 laptop kernel: atapci0: por= t 0x1100-0x110f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 Jan 19 03:05:38 laptop kernel: atapci0: Correcting VIA config for southbr= idge data corruption bug Jan 19 03:05:38 laptop kernel: ata0: channel #0 on atapci0 Jan 19 03:05:38 laptop kernel: ata1: channel #1 on atapci0 Jan 19 03:05:38 laptop kernel: uhci0: port 0x= 1200-0x121f irq 10 at device 17.2 on pci0 Jan 19 03:05:38 laptop kernel: uhci0: [GIANT-LOCKED] Jan 19 03:05:38 laptop kernel: usb0: on uhci0= Jan 19 03:05:38 laptop kernel: usb0: USB revision 1.0 Jan 19 03:05:38 laptop kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1= .00/1.00, addr 1 Jan 19 03:05:38 laptop kernel: uhub0: 2 ports with 2 removable, self powe= red Jan 19 03:05:38 laptop kernel: uhci1: port 0x= 1300-0x131f irq 10 at device 17.3 on pci0 Jan 19 03:05:38 laptop kernel: uhci1: [GIANT-LOCKED] Jan 19 03:05:38 laptop kernel: usb1: on uhci1= Jan 19 03:05:38 laptop kernel: usb1: USB revision 1.0 Jan 19 03:05:38 laptop kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1= .00/1.00, addr 1 Jan 19 03:05:38 laptop kernel: uhub1: 2 ports with 2 removable, self powe= red Jan 19 03:05:38 laptop kernel: pci0: at device 17.4= (no driver attached) Jan 19 03:05:38 laptop kernel: pci0: at device 17.5 (= no driver attached) Jan 19 03:05:38 laptop kernel: pci0: at device 17.6 (no dr= iver attached) Jan 19 03:05:38 laptop kernel: vr0: po= rt 0xe800-0xe8ff mem 0xf0000000-0xf00000ff irq 10 at device 18.0 on p ci0 Jan 19 03:05:38 laptop kernel: miibus0: on vr0 Jan 19 03:05:38 laptop kernel: ukphy0: on miibus0 Jan 19 03:05:38 laptop kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, = 100baseTX-FDX, auto Jan 19 03:05:38 laptop kernel: vr0: Ethernet address: 00:40:d0:32:79:a4 Jan 19 03:05:38 laptop kernel: atkbdc0: por= t 0x64,0x60 irq 1 on acpi0 Jan 19 03:05:38 laptop kernel: atkbd0: irq 1 on atkbdc0 Jan 19 03:05:38 laptop kernel: kbd0 at atkbd0 Jan 19 03:05:38 laptop kernel: atkbd0: [GIANT-LOCKED] Jan 19 03:05:38 laptop kernel: psm0: irq 12 on atkbdc0 Jan 19 03:05:38 laptop kernel: psm0: [GIANT-LOCKED] Jan 19 03:05:38 laptop kernel: psm0: model Generic PS/2 mouse, device ID = 0 Jan 19 03:05:38 laptop kernel: ppc0: por= t 0x378-0x37f irq 7 on acpi0 Jan 19 03:05:38 laptop kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMP= ATIBLE mode Jan 19 03:05:38 laptop kernel: ppbus0: on ppc0 Jan 19 03:05:38 laptop kernel: ppi0: on ppbus0 Jan 19 03:05:38 laptop kernel: lpt0: on ppbus0 Jan 19 03:05:38 laptop kernel: lpt0: Interrupt-driven port Jan 19 03:05:38 laptop kernel: pmtimer0 on isa0 Jan 19 03:05:38 laptop kernel: orm0: at iomem 0xeb000-0= xeffff,0xe6000-0xe6fff,0xe0000-0xe0fff,0xc0000-0xcbfff on isa0 Jan 19 03:05:38 laptop kernel: sc0: at flags 0x100 on is= a0 Jan 19 03:05:38 laptop kernel: sc0: VGA <16 virtual consoles, flags=3D0x3= 00> Jan 19 03:05:38 laptop kernel: vga0: at port 0x3c0-0x3d= f iomem 0xa0000-0xbffff on isa0 Jan 19 03:05:38 laptop kernel: sio0: configured irq 4 not in bitmap of pr= obed irqs 0 Jan 19 03:05:38 laptop kernel: sio0: port may not be enabled Jan 19 03:05:38 laptop kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 = on isa0 Jan 19 03:05:38 laptop kernel: sio0: type 8250 or not responding Jan 19 03:05:38 laptop kernel: sio1: configured irq 3 not in bitmap of pr= obed irqs 0 Jan 19 03:05:38 laptop kernel: sio1: port may not be enabled Jan 19 03:05:38 laptop kernel: Timecounter "TSC" frequency 1400056730 Hz = quality 800 Jan 19 03:05:38 laptop kernel: Timecounters tick every 10.000 msec Jan 19 03:05:38 laptop kernel: ipfw2 initialized, divert disabled, rule-b= ased forwarding disabled, default to deny, logging limited to 200 pac kets/entry by default Jan 19 03:05:38 laptop kernel: acpi_cpu: throttling enabled, 4 steps (100= % to 25.0%), currently 100.0% Jan 19 03:05:38 laptop kernel: ad0: 19077MB [387= 60/16/63] at ata0-master UDMA100 Jan 19 03:05:38 laptop kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed= out Jan 19 03:05:38 laptop last message repeated 2 times Jan 19 03:05:38 laptop kernel: acd0: CDRW at ata1= -master UDMA33 Jan 19 03:05:38 laptop kernel: Mounting root from ufs:/dev/ad0s1a --- END OF Boot with ACPI (Choise nr 2) --- --- START OF kernelconfig-file --- # # HAGGE -- Specific kernel configuration file for FreeBSD/i386(HAGGE) # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconf= ig-config.html # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.8 2004/10/24 17:42:08 sco= ttl Exp $ machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident HAGGE # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devi= ces. options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support= options UFS_ACL # Support for access control list= s options UFS_DIRHASH # Improve performance on big dire= ctories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCL= IENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PS= EUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP T= HIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=3D15000 # Delay (in ms) before probing = SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time ex= tensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 03:41:16 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96E0416A4CE for ; Wed, 19 Jan 2005 03:41:16 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 191EE43D54 for ; Wed, 19 Jan 2005 03:41:16 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 3DA0621C8FC for ; Tue, 18 Jan 2005 21:03:16 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59560-13 for ; Tue, 18 Jan 2005 21:03:15 -0600 (CST) Received: from kanga.honeypot.net (unknown [IPv6:2001:470:1f01:224:1::2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id A50AF21C8D9 for ; Tue, 18 Jan 2005 21:03:15 -0600 (CST) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 18 Jan 2005 21:03:09 -0600 User-Agent: KMail/1.7.2 References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> <41ECBED0.8000704@incubus.de> In-Reply-To: <41ECBED0.8000704@incubus.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1849349.R8dCxOYFfQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501182103.14385.kirk@strauser.com> X-Virus-Scanned: amavisd-new at honeypot.net Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 03:41:16 -0000 --nextPart1849349.R8dCxOYFfQ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 18 January 2005 01:46 am, Matthias Buelow wrote: > Then I'd leave it at that. The difference between gcc -O2 and -O is > marginal at best. Sometimes. I recently switched to -O2 -fno-strict-alias on my small Alpha machine and = got=20 an increase of well over 100% in the OpenSSL benchmarks. =2D-=20 Kirk Strauser --nextPart1849349.R8dCxOYFfQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7c3y5sRg+Y0CpvERAukjAKCNBDW13Lb4kaHbAtrHTG2nQRfeEACgm8qG 3FcgFNVJdHsSNua0Vu6Sh/0= =DCgH -----END PGP SIGNATURE----- --nextPart1849349.R8dCxOYFfQ-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 04:03:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF6F016A4CE; Wed, 19 Jan 2005 04:03:39 +0000 (GMT) Received: from web4.thecenturiongroup.com (104-238-234-66.cosmoweb.net [66.234.238.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCFF443D58; Wed, 19 Jan 2005 04:03:36 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id 2E98F7C007; Tue, 18 Jan 2005 23:03:36 -0500 (EST) Message-ID: <41EDDB38.1000107@michaelmeltzer.com> Date: Tue, 18 Jan 2005 22:59:52 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 04:03:40 -0000 straight boot, no patches or extra debug. -mjm Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #14: Thu Jan 13 23:55:20 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963796480 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: [GIANT-LOCKED] pci0: at device 11.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> 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 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled acd0: DVDROM at ata0-master UDMA33 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> Vinod Kashyap wrote: >I tried reproducing the problem on both i386 and amd64, >but could not. I installed 5.3 RELEASE, cvsuped to the >tip of RELENG_5, re-built the kernel with twa integrated, >and rebooted. The test systems booted just fine (off of >3ware controlled da0). I even tried replacing just the >twa sources of 5.3 RELEASE with the twa sources from the >tip of RELENG_5, and that worked fine too. All this, >without even upgrading the firmware from 2.02.00.008 (which >is bundled into 5.3 RELEASE sources). So, I am confused as >to what might be happening. > >Could you give the attached patch a try? Just a hunch... > > > > > >>-----Original Message----- >>From: owner-freebsd-stable@freebsd.org >>[mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer >>Sent: Friday, January 14, 2005 6:03 AM >>To: Vinod Kashyap >>Cc: freebsd stable >>Subject: Re: twa breakage on AMD64 with 9.1.5.2 >>3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit >> >> >> >> >> >>>Could you see if the driver is getting loaded? The driver prints >>>the message: "3ware device driver for 9000 series storage >>> >>> >>controllers...". >> >> >>>Did the new firmware get flashed? You can download the firmware >>> >>> >>>from the 3ware website and flash it on the card using a DOS floppy. >> >> >>>Alternatively, you can add 'options TWA_FLASH_FIRMWARE' to your >>>kernel configuration file and rebuild the kernel. This should build >>>the kernel/driver with the firmware bundled, and the firmware should >>>automatically get downloaded the next time you reboot. >>> >>> >>> >>> >>> >>> >>> >>> >>I reloaded the new driver and rebuilt the kernel last night with the >>TWA_FLASH_FIRMWARE, Did not see the -D on the command line for the >>rebuild, the new firmware was not requested to load. I got the new >>firmware from 3ware and flashed it in, Still does not work. I >>also build >>a straight GENERIC Kernel, still no luck. Their is no error >>message that >>I saw and the versions number for the pieces did change so it >>the "new" >>stuff. I need to setup a serial console to capture the full messages, >>should have that on monday night. Thank You -mjm >> >> >>_______________________________________________ >>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 Wed Jan 19 05:09:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 183B816A4CF; Wed, 19 Jan 2005 05:09:08 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4469A43D2D; Wed, 19 Jan 2005 05:09:07 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id B05F37C007; Wed, 19 Jan 2005 00:09:06 -0500 (EST) Message-ID: <41EDEA93.5060305@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:05:23 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 05:09:08 -0000 boot with twa_r5.diff patch and options TWA_DEBUG=10 -mjm Copyright (c) 1992-2005 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 5.3-STABLE #15: Tue Jan 18 23:58:45 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> 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 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 05:37:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20F9316A4CE; Wed, 19 Jan 2005 05:37:28 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51C4543D55; Wed, 19 Jan 2005 05:37:25 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id C17D87C007; Wed, 19 Jan 2005 00:37:24 -0500 (EST) Message-ID: <41EDF135.6010404@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:33:41 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 05:37:28 -0000 using twa_patch1.diff: needed to add "int error" to twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 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 5.3-STABLE #16: Wed Jan 19 00:29:26 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 40000 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> 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 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 05:46:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDEAA16A4CE for ; Wed, 19 Jan 2005 05:46:07 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5815943D45 for ; Wed, 19 Jan 2005 05:46:07 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0J5k6Kd011551 for ; Tue, 18 Jan 2005 23:46:06 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Tue Jan 18 23:46:06 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0J5k6nr011549 for freebsd-stable@freebsd.org; Tue, 18 Jan 2005 23:46:06 -0600 (CST) Message-ID: <20050118234606.C11398@Denninger.Net> Date: Tue, 18 Jan 2005 23:46:06 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Trials and tribulations on mirroring.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 05:46:08 -0000 Hi folks; I've been running 4.x quite happily for some time, and am trying to set up a box with 5.3 that hopefully will end up being a viable platform to move over to. Tried on both 5.3-RELEASE and 5.3-STABLE (built this evening) Having some problems here... First, I discovered that vinum isn't "quite right" with 5.3. Ok, so I moved to "gvinum", but ran into some really bizarre behavior there too, where it was detaching subdisks apparently at random and on a rebuild would occasionally crash with some really wild results. It also doesn't load-balance reads (barf). All this was discovered after I spent an afternoon getting it set up properly with the "shadow" root and all. Bummer.... The instability is a real deal-breaker - this is supposed to (eventually) be a production server, so it can't be "squirrelly". So, my next attempt (with a new, fresh load) was to give gmirror a shot instead, since I only need Raid 1, and this looks like a "better" option from that perspective given gvinum's squirrely and not-all-there status at the moment. Weeeeellll.. the manual page (and the archives on the list here) implies that I can do the following: 1. Set up the system on one of the two mirror disks. 2. In single user mode, use "gmirror label -v -b round-robin disk ad4" to set up the pre-existing disk (with data on it), which I booted from, as the "primary". 3. Then use "gmirror insert disk ad6" to add the secondary (mirrored) disk, which will automatically sync it and bring them into a consistent state. Only one small problem - the first command (in #2) fails, with: "Can't store metadata on ad4: Operation not permitted" This is true if the system is mounted read-only (in single user mode) or read-write (in multiuser, with all filesystems mounted) Attempting to label the SECOND (bare) disk works, but of course that's backwards and an "insert" would immediately destroy the running system (I assume it would also fail with the same permission error, but I've not tried it) - so that's not an option. I also tried it from the fixit disk, but the KLD cannot be loaded from the fixit disk, and none of the commands work - so that appears to not be an option either. How do you get this thing set up? The archives here (and man pages) strongly imply that this works for a root filesystem and boot drive - what am I missing? Need a Raid 1 solution that works to move over to the 5.x world out here... -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 05:50:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A11C616A4CE; Wed, 19 Jan 2005 05:50:44 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA98243D46; Wed, 19 Jan 2005 05:50:43 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id BABFC7C00C; Wed, 19 Jan 2005 00:50:42 -0500 (EST) Message-ID: <41EDF452.1070305@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:46:58 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 05:50:44 -0000 twa_patch2.diff, had to add the "int error; in twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 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 5.3-STABLE #17: Wed Jan 19 00:44:33 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 40000 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> 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 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroo From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 05:58:45 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBA9A16A4CE for ; Wed, 19 Jan 2005 05:58:44 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 692DD43D3F for ; Wed, 19 Jan 2005 05:58:44 +0000 (GMT) (envelope-from ringworm@inbox.lv) Received: from ringworm.mechee.com ([4.26.84.7]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050119055843.RZHJ12052.out002.verizon.net@ringworm.mechee.com> for ; Tue, 18 Jan 2005 23:58:43 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id B32CA2CE747; Tue, 18 Jan 2005 21:55:11 -0800 (PST) From: "Michael C. Shultz" To: freebsd-stable@freebsd.org Date: Tue, 18 Jan 2005 21:55:09 -0800 User-Agent: KMail/1.7.2 References: <20050118234606.C11398@Denninger.Net> In-Reply-To: <20050118234606.C11398@Denninger.Net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501182155.10782.ringworm@inbox.lv> X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [4.26.84.7] at Tue, 18 Jan 2005 23:58:43 -0600 Subject: Re: Trials and tribulations on mirroring.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 05:58:45 -0000 On Tuesday 18 January 2005 09:46 pm, Karl Denninger wrote: > Hi folks; > > I've been running 4.x quite happily for some time, and am trying to > set up a box with 5.3 that hopefully will end up being a viable > platform to move over to. > > Tried on both 5.3-RELEASE and 5.3-STABLE (built this evening) > > Having some problems here... > > First, I discovered that vinum isn't "quite right" with 5.3. Ok, so > I moved to "gvinum", but ran into some really bizarre behavior there > too, where it was detaching subdisks apparently at random and on a > rebuild would occasionally crash with some really wild results. It > also doesn't load-balance reads (barf). All this was discovered > after I spent an afternoon getting it set up properly with the > "shadow" root and all. Bummer.... > > The instability is a real deal-breaker - this is supposed to > (eventually) be a production server, so it can't be "squirrelly". > > So, my next attempt (with a new, fresh load) was to give gmirror a > shot instead, since I only need Raid 1, and this looks like a > "better" option from that perspective given gvinum's squirrely and > not-all-there status at the moment. > > Weeeeellll.. the manual page (and the archives on the list here) > implies that I can do the following: > > 1. Set up the system on one of the two mirror disks. > > 2. In single user mode, use "gmirror label -v -b round-robin disk > ad4" to set up the pre-existing disk (with data on it), which I > booted from, as the "primary". > > 3. Then use "gmirror insert disk ad6" to add the secondary (mirrored) > disk, which will automatically sync it and bring them into a > consistent state. > > Only one small problem - the first command (in #2) fails, with: > > "Can't store metadata on ad4: Operation not permitted" > > This is true if the system is mounted read-only (in single user mode) > or read-write (in multiuser, with all filesystems mounted) > > Attempting to label the SECOND (bare) disk works, but of course > that's backwards and an "insert" would immediately destroy the > running system (I assume it would also fail with the same permission > error, but I've not tried it) - so that's not an option. > > I also tried it from the fixit disk, but the KLD cannot be loaded > from the fixit disk, and none of the commands work - so that appears > to not be an option either. > > How do you get this thing set up? The archives here (and man pages) > strongly imply that this works for a root filesystem and boot drive - > what am I missing? > > Need a Raid 1 solution that works to move over to the 5.x world out > here... I had a pentium 166 with four matched ide drives set up as Striped plexes that had better disk access than my current 1ghz system. I sure miss that! The only time FreeBSD let me down when they let stopped supporting vinum. Guess no OS is perfect -Mike From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 06:11:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F37C116A4CE for ; Wed, 19 Jan 2005 06:11:34 +0000 (GMT) Received: from smtp815.mail.sc5.yahoo.com (smtp815.mail.sc5.yahoo.com [66.163.170.1]) by mx1.FreeBSD.org (Postfix) with SMTP id C9AA943D46 for ; Wed, 19 Jan 2005 06:11:34 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noacks@swbell.net@70.240.249.100 with login) by smtp815.mail.sc5.yahoo.com with SMTP; 19 Jan 2005 06:11:34 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id D027E629E; Wed, 19 Jan 2005 00:11:33 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 72289-02; Wed, 19 Jan 2005 00:10:15 -0600 (CST) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id B688261EC; Wed, 19 Jan 2005 00:10:15 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.1/8.13.1) with ESMTP id j0J6AExu051632; Wed, 19 Jan 2005 00:10:15 -0600 (CST) (envelope-from noackjr@alumni.rice.edu) Message-ID: <41EDF9C6.4040709@alumni.rice.edu> Date: Wed, 19 Jan 2005 00:10:14 -0600 From: Jon Noack User-Agent: Mozilla Thunderbird 1.0 (X11/20050103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karl Denninger References: <20050118234606.C11398@Denninger.Net> In-Reply-To: <20050118234606.C11398@Denninger.Net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org cc: freebsd-stable@freebsd.org Subject: Re: Trials and tribulations on mirroring.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 06:11:35 -0000 On 01/18/05 23:46, Karl Denninger wrote: > > > So, my next attempt (with a new, fresh load) was to give gmirror a shot > instead, since I only need Raid 1, and this looks like a "better" option > from that perspective given gvinum's squirrely and not-all-there status at > the moment. > > Weeeeellll.. the manual page (and the archives on the list here) implies that > I can do the following: > > 1. Set up the system on one of the two mirror disks. > > 2. In single user mode, use "gmirror label -v -b round-robin disk ad4" > to set up the pre-existing disk (with data on it), which I booted from, > as the "primary". > > 3. Then use "gmirror insert disk ad6" to add the secondary (mirrored) disk, > which will automatically sync it and bring them into a consistent state. > > Only one small problem - the first command (in #2) fails, with: > > "Can't store metadata on ad4: Operation not permitted" > > This is true if the system is mounted read-only (in single user mode) or > read-write (in multiuser, with all filesystems mounted) > > Attempting to label the SECOND (bare) disk works, but of course that's > backwards and an "insert" would immediately destroy the running system (I > assume it would also fail with the same permission error, but I've not tried > it) - so that's not an option. > > I also tried it from the fixit disk, but the KLD cannot be loaded from the > fixit disk, and none of the commands work - so that appears to not be an > option either. > > How do you get this thing set up? The archives here (and man pages) > strongly imply that this works for a root filesystem and boot drive - > what am I missing? > > Need a Raid 1 solution that works to move over to the 5.x world out here... If any filesystem is mounted then GEOM will not allow metadata updates for the drive. Here's a solution given over on the geom@ list: http://lists.freebsd.org/pipermail/freebsd-geom/2004-November/000379.html I converted to gmirror from ataraid, so I already had 2 disks with identical contents. I worked around this problem as outlined here (the instructions have errors that are corrected later in the thread): http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039907.html I wish we handled this in the installer, but as I can't produce the code to do it I'll shut up now... Jon From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 06:26:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C00416A4CE for ; Wed, 19 Jan 2005 06:26:53 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0289543D60 for ; Wed, 19 Jan 2005 06:26:53 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j0J6QqVF039098 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 00:26:52 -0600 (CST) (envelope-from dan) Date: Wed, 19 Jan 2005 00:26:51 -0600 From: Dan Nelson To: freebsd-stable@freebsd.org Message-ID: <20050119062651.GA5122@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: panic: Assertion besttd != NULL failed at ../../../kern/subr_sleepqueue.c:676 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 06:26:53 -0000 Got this while running a Java proxy server under libthr: FreeBSD dan.emsphone.com 5.3-STABLE FreeBSD 5.3-STABLE #387: Thu Jan 13 14:43:03 CST 2005 zsh@dan.emsphone.com:/usr/src/sys/i386/compile/DANSMP i386 panic: Assertion besttd != NULL failed at ../../../kern/subr_sleepqueue.c:676 cpuid = 1 KDB: stack backtrace: panic(c07822b6,c078843f,c078825f,2a4,ffffffff) at panic+0x1cf sleepq_signal(c3a9b4b0,0,ffffffff,e7461ce0,c05a74eb) at sleepq_signal+0xf0 wakeup_one(c3a9b4b0,0,c07863e3,12e,be3173f0) at wakeup_one+0x20 thr_wake(c2bb84b0,e7461d14,4,16,1) at thr_wake+0xdb syscall(3123002f,2f,4c98002f,811bfc0,83f4400) at syscall+0x137 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (443, FreeBSD ELF32, thr_wake), eip = 0x280e658f, esp = 0xbe3173ec, ebp = 0xbe317418 --- panic: mi_switch: switch in a critical section cpuid = 1 The last two lines repeated forever until I reset the box, so no coredump, but the stack is almost identical to a panic I got back in November and did get a trace on (the crashdump is long gone though). #0 doadump () at pcpu.h:159 #1 0xc059aa86 in boot (howto=260) at ../../../kern/kern_shutdown.c:397 #2 0xc059a55b in panic (fmt=0xc077e446 "Assertion %s failed at %s:%d") at ../../../kern/kern_shutdown.c:553 #3 0xc05bcb5c in sleepq_remove_thread (sq=0xc3394dc0, td=0x0) at ../../../kern/subr_sleepqueue.c:594 #4 0xc05bd47d in sleepq_signal (wchan=0xc2c5d7d0, flags=0, pri=-1) at ../../../kern/subr_sleepqueue.c:675 #5 0xc05a1d80 in wakeup_one (ident=0x0) at ../../../kern/kern_synch.c:266 #6 0xc05a5dab in thr_wake (td=0xc38abaf0, uap=0x0) at ../../../kern/kern_thr.c:303 #7 0xc072a797 in syscall (frame={tf_fs = 819527727, tf_es = 1285816367, tf_ds = -1078001617, tf_edi = 135378944, tf_esi = 137891840, tf_ebp = -1173986296, tf_isp = -419791500, tf_ebx = 671700552, tf_edx = 138204160, tf_ecx = 0, tf_eax = 443, tf_trapno = 22, tf_err = 2, tf_eip = 672032143, tf_cs = 31, tf_eflags = 582, tf_esp = -1173986340, tf_ss = 47}) at ../../../i386/i386/trap.c:1001 #8 0xc07168af in Xint0x80_syscall () at ../../../i386/i386/exception.s:201 -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 06:48:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58E9716A4CE for ; Wed, 19 Jan 2005 06:48:27 +0000 (GMT) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id C120B43D45 for ; Wed, 19 Jan 2005 06:48:26 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0J6mOnM012289 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Jan 2005 17:48:25 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0J6mNxP065555; Wed, 19 Jan 2005 17:48:24 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0J6mN4e065554; Wed, 19 Jan 2005 17:48:23 +1100 (EST) (envelope-from pjeremy) Date: Wed, 19 Jan 2005 17:48:23 +1100 From: Peter Jeremy To: Rob Lahaye Message-ID: <20050119064822.GA65506@cirb503493.alcatel.com.au> References: <41EDA6FB.6000706@snu.ac.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EDA6FB.6000706@snu.ac.kr> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 06:48:27 -0000 On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > tunnel="-L 55110:localhost:110 pop3.univ.net" > tunnel_up=`pgrep -f -- "${tunnel}"` > [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} >It works beautifully, but why does this also generate one zombie process: > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 You get a zombie when a process has exited and the parent hasn't issued a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process is and that might give you an idea as to what is going wrong. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 06:52:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7623216A4E5 for ; Wed, 19 Jan 2005 06:52:31 +0000 (GMT) Received: from nabi1.snu.ac.kr (nabi1.snu.ac.kr [147.46.100.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B44243D49 for ; Wed, 19 Jan 2005 06:52:31 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.100.32] ([147.46.100.32]) by nabi1.snu.ac.kr ([147.46.100.51]) with ESMTP id 2005011915:53:38:979842.29014.3039816624 for ; Wed, 19 Jan 2005 15:53:38 +0900 (KST) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk2.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2005011915:52:10:292294.12589.3027430320 for ; Wed, 19 Jan 2005 15:52:10 +0900 (KST) Message-ID: <41EE03A6.7080404@yahoo.com> Date: Wed, 19 Jan 2005 15:52:22 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050105 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-stable@freebsd.org References: <41EDA6FB.6000706@snu.ac.kr> <20050119064822.GA65506@cirb503493.alcatel.com.au> In-Reply-To: <20050119064822.GA65506@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:1.35) (by Terrace) Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 06:52:32 -0000 Peter Jeremy wrote: > On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > >> tunnel="-L 55110:localhost:110 pop3.univ.net" >> tunnel_up=`pgrep -f -- "${tunnel}"` >> [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} > > >>It works beautifully, but why does this also generate one zombie process: >>USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND >>rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 > > You get a zombie when a process has exited and the parent hasn't issued > a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process > is and that might give you an idea as to what is going wrong. Sorry, can you tell me how to do this? How can I find out what's the parent process of a Zombie process? I have a user crontab, which calls a sh-shell script; so I have no clue where to start investigating.... Thanks, Rob. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 06:57:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5194A16A4CE for ; Wed, 19 Jan 2005 06:57:58 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC26943D39 for ; Wed, 19 Jan 2005 06:57:57 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0J6vvxE012368 for ; Wed, 19 Jan 2005 00:57:57 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 00:57:57 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0J6vvqJ012366; Wed, 19 Jan 2005 00:57:57 -0600 (CST) Message-ID: <20050119005757.A12360@Denninger.Net> Date: Wed, 19 Jan 2005 00:57:57 -0600 From: Karl Denninger To: noackjr@alumni.rice.edu References: <20050118234606.C11398@Denninger.Net> <41EDF9C6.4040709@alumni.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <41EDF9C6.4040709@alumni.rice.edu>; from Jon Noack on Wed, Jan 19, 2005 at 12:10:14AM -0600 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! cc: freebsd-stable@freebsd.org Subject: Re: Trials and tribulations on mirroring.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 06:57:58 -0000 Thanks.... that should do the trick (and explains why it fails....) -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind On Wed, Jan 19, 2005 at 12:10:14AM -0600, Jon Noack wrote: > On 01/18/05 23:46, Karl Denninger wrote: > > > > > > So, my next attempt (with a new, fresh load) was to give gmirror a shot > > instead, since I only need Raid 1, and this looks like a "better" option > > from that perspective given gvinum's squirrely and not-all-there status at > > the moment. > > > > Weeeeellll.. the manual page (and the archives on the list here) implies that > > I can do the following: > > > > 1. Set up the system on one of the two mirror disks. > > > > 2. In single user mode, use "gmirror label -v -b round-robin disk ad4" > > to set up the pre-existing disk (with data on it), which I booted from, > > as the "primary". > > > > 3. Then use "gmirror insert disk ad6" to add the secondary (mirrored) disk, > > which will automatically sync it and bring them into a consistent state. > > > > Only one small problem - the first command (in #2) fails, with: > > > > "Can't store metadata on ad4: Operation not permitted" > > > > This is true if the system is mounted read-only (in single user mode) or > > read-write (in multiuser, with all filesystems mounted) > > > > Attempting to label the SECOND (bare) disk works, but of course that's > > backwards and an "insert" would immediately destroy the running system (I > > assume it would also fail with the same permission error, but I've not tried > > it) - so that's not an option. > > > > I also tried it from the fixit disk, but the KLD cannot be loaded from the > > fixit disk, and none of the commands work - so that appears to not be an > > option either. > > > > How do you get this thing set up? The archives here (and man pages) > > strongly imply that this works for a root filesystem and boot drive - > > what am I missing? > > > > Need a Raid 1 solution that works to move over to the 5.x world out here... > > If any filesystem is mounted then GEOM will not allow metadata updates > for the drive. Here's a solution given over on the geom@ list: > http://lists.freebsd.org/pipermail/freebsd-geom/2004-November/000379.html > > I converted to gmirror from ataraid, so I already had 2 disks with > identical contents. I worked around this problem as outlined here (the > instructions have errors that are corrected later in the thread): > http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039907.html > > I wish we handled this in the installer, but as I can't produce the code > to do it I'll shut up now... > > Jon > _______________________________________________ > 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" > > > %SPAMBLOCK-SYS: Matched [freebsd], message ok From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 07:40:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 983B116A4CE for ; Wed, 19 Jan 2005 07:40:29 +0000 (GMT) Received: from oslex.fast.no (pat-gw.osl.fast.no [217.144.235.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80DEF43D41 for ; Wed, 19 Jan 2005 07:40:28 +0000 (GMT) (envelope-from Raymond.Wiker@fast.no) Received: from raw.grenland.fast.no.fast.no ([192.168.48.104] RDNS failed) by oslex.fast.no with Microsoft SMTPSVC(6.0.3790.211); Wed, 19 Jan 2005 08:40:26 +0100 From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16878.3817.600151.965257@raw.grenland.fast.no> Date: Wed, 19 Jan 2005 08:40:25 +0100 To: freebsd-stable@freebsd.org In-Reply-To: <20050119064822.GA65506@cirb503493.alcatel.com.au> References: <41EDA6FB.6000706@snu.ac.kr> <20050119064822.GA65506@cirb503493.alcatel.com.au> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid X-OriginalArrivalTime: 19 Jan 2005 07:40:26.0666 (UTC) FILETIME=[2458B0A0:01C4FDFA] Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 07:40:29 -0000 Peter Jeremy writes: > On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > > tunnel="-L 55110:localhost:110 pop3.univ.net" > > tunnel_up=`pgrep -f -- "${tunnel}"` > > [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} > > >It works beautifully, but why does this also generate one zombie process: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 > > You get a zombie when a process has exited and the parent hasn't issued > a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process > is and that might give you an idea as to what is going wrong. Ancient Perl did not collect for children started via the backtick operator - is this a possible issue for /bin/sh as well? It should be harmless to call wait just after the use of the backtick operator above; does that change anything? I.e: tunnel_up=`pgrep -f -- "${tunnel}"`; wait To see the parent pid, add "-O ppid" to the arguments to ps; e.g, ps axww -O ppid -- Raymond Wiker Mail: Raymond.Wiker@fast.no Senior Software Engineer Web: http://www.fast.no/ Fast Search & Transfer ASA Phone: +47 23 01 11 60 P.O. Box 1677 Vika Fax: +47 35 54 87 99 NO-0120 Oslo, NORWAY Mob: +47 48 01 11 60 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 10:32:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAF0816A4CE; Wed, 19 Jan 2005 10:32:20 +0000 (GMT) Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D91A43D46; Wed, 19 Jan 2005 10:32:19 +0000 (GMT) (envelope-from michal.mertl@i.cz) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 5E5291527D; Wed, 19 Jan 2005 11:32:18 +0100 (CET) Received: from localhost (localhost.i.cz [127.0.0.1]) by ns.i.cz (Postfix) with SMTP id 36D76F4B03; Wed, 19 Jan 2005 11:32:18 +0100 (CET) X-AV-Checked: Wed Jan 19 11:32:18 2005 ns.i.cz Received: from localhost.localdomain (brana.i.cz [192.168.1.10]) by ns.i.cz (Postfix) with ESMTP id F02C3F4B01; Wed, 19 Jan 2005 11:32:17 +0100 (CET) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <200501182236.54005.emanuel.strobl@gmx.net> References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru> <200501182236.54005.emanuel.strobl@gmx.net> Content-Type: multipart/mixed; boundary="=-ngKAzEcYDbfRht4+QWkN" Date: Wed, 19 Jan 2005 11:30:06 +0100 Message-Id: <1106130606.1132.9.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 10:32:21 -0000 --=-ngKAzEcYDbfRht4+QWkN Content-Type: text/plain Content-Transfer-Encoding: 7bit Emanuel Strobl wrote: > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > Dear experts, > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > the other one not (I hate to say it but both are working under win). > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > ucom0, also I can receive signal but not transmit. > > > > [skip] > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > It can break old (working) PL2303 chip, but it works for me with newer > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > also breakes the 2.02 version :( > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > this information (akiyama?)? > > Thanks a lot, I've just recently been looking into this too. I used the mentioned patch and also linux driver source and have come with the attached patch. It contains one more change but I don't know if it's correct. It works for both chips on CURRENT for serial console. The author of the patch mentions it isn't binary safe - sometimes the chip stops working. I planned to test it with binary transfers (ppp) today, check if it's working and submit it (with some cleanup) for inclusion in FreeBSD. Michal Mertl --=-ngKAzEcYDbfRht4+QWkN Content-Disposition: attachment; filename=uplcom.c.pl2303x.diff Content-Type: text/x-patch; name=uplcom.c.pl2303x.diff; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 15 Jan 2005 00:44:20 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -113,30 +116,33 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_CTS 0x80 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,14 +162,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -299,6 +306,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -374,7 +382,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -617,7 +632,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, 0x61); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -713,6 +731,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -743,7 +798,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --=-ngKAzEcYDbfRht4+QWkN-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 11:19:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36F1A16A4E0 for ; Wed, 19 Jan 2005 11:19:39 +0000 (GMT) Received: from ns.adis.at (ns.adis.at [195.64.0.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25CA243D55 for ; Wed, 19 Jan 2005 11:19:38 +0000 (GMT) (envelope-from freebsd-ml@petermair.at) Received: from [195.64.29.62] (gw.anecon.com [195.64.29.62]) by ns.adis.at (8.13.1/8.13.1) with SMTP id j0JBJZOX015732 for ; Wed, 19 Jan 2005 11:19:36 GMT X-Abuse-Info: Please report abuse to abuse@eunet.co.at, see http://www.eunet.at/support/service Message-ID: <41EE4246.5050707@petermair.at> Received: from no.name.available by [195.64.29.62] via smtpd (for [195.64.0.34]) with SMTP; 19 Jan 2005 11:21:32 UT Date: Wed, 19 Jan 2005 12:19:34 +0100 From: Patrick Petermair User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41ECC3A7.8040300@ISI.EDU> In-Reply-To: <41ECC3A7.8040300@ISI.EDU> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-ml@petermair.at List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 11:19:39 -0000 Tejas Kokje wrote: > in the kernel configuration file. However the quality of > sound produced is of poor quality (not very clear) as compared to that > produced under Linux 2.6 series kernel. Maybe check your mixer settings ("mixer" at the console)... Patrick From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 11:26:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F312C16A4CE; Wed, 19 Jan 2005 11:26:55 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D6443D5A; Wed, 19 Jan 2005 11:26:55 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0JBR8MJ035149; Wed, 19 Jan 2005 12:27:08 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl Content-Type: text/plain Date: Wed, 19 Jan 2005 12:26:46 +0100 Message-Id: <1106134006.1132.12.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: [Fwd: Re: strange ucom (uplcom) error] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 11:26:56 -0000 Emanuel Strobl wrote: > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > Dear experts, > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > the other one not (I hate to say it but both are working under win). > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > ucom0, also I can receive signal but not transmit. > > > > [skip] > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > It can break old (working) PL2303 chip, but it works for me with newer > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > also breakes the 2.02 version :( > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > this information (akiyama?)? > > Thanks a lot, I've just recently been looking into this too. I used the mentioned patch and also linux driver source and have come with the attached patch. It contains one more change but I don't know if it's correct. It works for both chips on CURRENT for serial console. It detects if the chip is rev 3.00 and aplies the patch only for it. The author of the patch mentions it isn't binary safe - sometimes the chip stops working. I planned to test it with binary transfers (ppp) today, check if it's working and submit it (with some cleanup) for inclusion in FreeBSD. Michal Mertl From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 12:11:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCB4A16A4CE for ; Wed, 19 Jan 2005 12:11:35 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3899543D49 for ; Wed, 19 Jan 2005 12:11:34 +0000 (GMT) (envelope-from mime@secservers.com) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0JCBrsU041731; Wed, 19 Jan 2005 13:11:53 +0100 (CET) (envelope-from mime@secservers.com) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <1106134006.1132.12.camel@genius2.i.cz> References: <1106134006.1132.12.camel@genius2.i.cz> Content-Type: multipart/mixed; boundary="=-LuMBlHTdF+ceeQIQ9Ebh" Date: Wed, 19 Jan 2005 13:11:31 +0100 Message-Id: <1106136691.1132.17.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 12:11:35 -0000 --=-LuMBlHTdF+ceeQIQ9Ebh Content-Type: text/plain Content-Transfer-Encoding: 7bit Sorry to reply to myself but I would better really attach the patch. I wrote: > Emanuel Strobl wrote: > > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > > Dear experts, > > > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > > the other one not (I hate to say it but both are working under win). > > > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > > ucom0, also I can receive signal but not transmit. > > > > > > [skip] > > > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > > > It can break old (working) PL2303 chip, but it works for me with newer > > > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > > also breakes the 2.02 version :( > > > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > > this information (akiyama?)? > > > > Thanks a lot, > > I've just recently been looking into this too. I used the mentioned > patch and also linux driver source and have come with the attached > patch. It contains one more change but I don't know if it's correct. It > works for both chips on CURRENT for serial console. It detects if the > chip is rev 3.00 and aplies the patch only for it. > > The author of the patch mentions it isn't binary safe - sometimes the > chip stops working. I planned to test it with binary transfers (ppp) > today, check if it's working and submit it (with some cleanup) for > inclusion in FreeBSD. > > Michal Mertl --=-LuMBlHTdF+ceeQIQ9Ebh Content-Disposition: attachment; filename=uplcom.c.pl2303x.diff Content-Type: text/x-patch; name=uplcom.c.pl2303x.diff; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 15 Jan 2005 00:44:20 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -113,30 +116,33 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_CTS 0x80 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,14 +162,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -299,6 +306,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -374,7 +382,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -617,7 +632,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, 0x61); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -713,6 +731,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -743,7 +798,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --=-LuMBlHTdF+ceeQIQ9Ebh-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 12:26:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8247D16A4CE for ; Wed, 19 Jan 2005 12:26:49 +0000 (GMT) Received: from cgp.sovintel.ru (cgp.sovintel.ru [212.44.130.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB25643D4C for ; Wed, 19 Jan 2005 12:26:47 +0000 (GMT) (envelope-from borman@blank.spb.ru) Received: from [212.44.130.15] (HELO xy.blank.spb.ru) by cgp.sovintel.ru (CommuniGate Pro SMTP 4.2.1) with ESMTP-TLS id 130976396 for stable@freebsd.org; Wed, 19 Jan 2005 15:26:46 +0300 Received: from xy.blank.spb.ru (localhost.blank.spb.ru [127.0.0.1]) by xy.blank.spb.ru (8.13.1/8.13.1/blank) with ESMTP id j0JCQjmf000931; Wed, 19 Jan 2005 15:26:45 +0300 (MSK) (envelope-from borman@xy.blank.spb.ru) Received: (from borman@localhost) by xy.blank.spb.ru (8.13.1/8.13.1/Submit) id j0JCQihL000930; Wed, 19 Jan 2005 15:26:44 +0300 (MSK) (envelope-from borman) Date: Wed, 19 Jan 2005 15:26:44 +0300 From: boris karlov To: Vinod Kashyap Message-ID: <20050119122644.GB878@xy.blank.spb.ru> Mail-Followup-To: Vinod Kashyap , stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: stable@freebsd.org Subject: Re: twa module - make kernel (modules) failure RELENG_5 i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 12:26:49 -0000 thanks a lot. strange cvsup Jan 14, but file was: # ident /usr/src/sys/dev/twa/twa_reg.h /usr/src/sys/dev/twa/twa_reg.h: $FreeBSD: src/sys/dev/twa/twa_reg.h,v 1.1.4.1 2004/08/25 17:15:26 vkashyap Exp $ cvsupped again via another mirror, now it's OK. On Mon, 17 Jan 2005 15:32:38 -0800, Vinod Kashyap wrote: > > Make sure you have the updated /sys/dev/twa/twa_reg.h. > The struct twa_command_header has the field err_desc > defined in it. > > > > -----Original Message----- > > From: owner-freebsd-stable@freebsd.org > > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of boris karlov > > Sent: Sunday, January 16, 2005 11:03 PM > > To: stable@freebsd.org > > Subject: twa module - make kernel (modules) failure RELENG_5 i386 > > > > > > Hello All, > > I have make kernel failure during compiling twa module (see below). > > cvsupped RELENG_5 Fri Jan 14. > > have no any twa devices in the system. > > (please Cc: me in reply - not subscribed to stable@) > > thanks. > > > > ===> twa > > cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc > > -I- -include > > /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ > > -I@/contrib/altq > > -I@/../include -finline-limit=8000 -fno-common > > -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings > > -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Winline -Wcast-qual -fformat-extensions -std=c99 -c > > /usr/src/sys/modules/twa/../../dev/twa/twa_freebsd.c > > cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc > > -I- -include > > /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ > > -I@/contrib/altq > > -I@/../include -finline-limit=8000 -fno-common > > -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings > > -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Winline -Wcast-qual -fformat-extensions -std=c99 -c > > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c > > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c: In function > > `twa_scsi_complete': > > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: > > structure has > > no member named `err_desc' > > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: > > structure has > > no member named `err_desc' > > /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:636: error: > > structure has > > no member named `err_desc' > > *** Error code 1 > > > > Stop in /usr/src/sys/modules/twa. > > *** Error code 1 > > > > > > /etc/make.conf: > > CPUTYPE=p2 > > NO_CVS=true > > NO_BIND=true > > NO_BLUETOOTH=true > > NO_FORTRAN=true > > NO_GDB=true > > NO_I4B=true > > NO_IPFILTER=true > > NO_PF=true > > NO_AUTHPF=true > > NO_KERBEROS=true > > NO_NIS=true > > NO_TCSH=true > > NO_USB=true > > NO_VINUM=true > > NOATM=true > > NOGAMES=true > > NOINET6=true > > NOINFO=true > > NOPROFILE=true > > > > _______________________________________________ > > 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 Wed Jan 19 13:49:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8D1416A4CE; Wed, 19 Jan 2005 13:49:44 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCC2243D41; Wed, 19 Jan 2005 13:49:43 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])0301F4F842; Wed, 19 Jan 2005 14:49:43 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18933-01-2; Wed, 19 Jan 2005 14:49:42 +0100 (CET) Received: from m2a2.dyndns.org (p54854A51.dip.t-dialin.net [84.133.74.81]) B65744E45A; Wed, 19 Jan 2005 14:49:41 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 2DA1877736; Wed, 19 Jan 2005 14:49:41 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01853-06; Wed, 19 Jan 2005 14:49:40 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 25519777C6; Wed, 19 Jan 2005 14:49:40 +0100 (CET) From: Matthias Andree To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Date: Wed, 19 Jan 2005 14:49:40 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: re@freebsd.org Subject: 4.11-RC3: SCSI+UFS+softupdates corruption (write cache DISABLED!) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 13:49:44 -0000 Hi, I had a FreeBSD 4.11-RC3 machine reboot without advance notice, the last logging the network syslogd captured was attempted aic0 (Adaptec 2940 UW Pro) recovery. Syslog excerpt as captured by the remote machine, with date and "hostname /kernel:" and card state dumps removed (can be provided if necessary). I wonder if the SCSI error recovery attempts caused the reboot, I have no hints either way, but this machine is otherwise stable. 13:28:35 ahc0: Recovery Initiated 13:28:53 (da0:ahc0:0:0:0): SCB 0x16 - timed out 13:28:53 sg[0] - Addr 0x6da3800 : Length 2048 13:28:53 (da0:ahc0:0:0:0): Other SCB Timeout 13:28:53 ahc0: Timedout SCBs already complete. Interrupts may not be functioning. 13:28:53 ahc0: Recovery Initiated 13:29:02 (da0:ahc0:0:0:0): SCB 0x1b - timed out 13:29:04 (da0:ahc0:0:0:0): BDR message in message buffer 13:29:04 ahc0: Timedout SCBs already complete. Interrupts may not be functioning. 13:29:04 ahc0: Recovery Initiated 13:29:16 Kernel Free SCB list: 9 4 15 20 13:29:17 sg[7] - Addr 0x3bea000 : Length 4096 13:29:18 ahc0: Issued Channel A Bus Reset. 25 SCBs aborted As the machine rebooted up, it remained in single user due to a softupdates inconsistency fsck reported: | # fsck -p /usr | /dev/da0s1g: DIRECTORY CORRUPTED I=175105 OWNER=root MODE=40755 | /dev/da0s1g: SIZE=512 MTIME=Jan 18 15:14 2005 | /dev/da0s1g: DIR=? | | /dev/da0s1g: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. I have not yet run fsck for interactive repair, because I want to know what is going on here and allow debugging this. At the time of the crash, these tasks were running: 1. amanda was running a dump(8) 2. I was installing manpages from /usr/src/share/man/man4 3. a cvsup for the ports tree was running (this is likely related to the problem) | # fsdb -r /dev/da0s1g | fsdb (inum: 2)> inode 175105 | current inode: directory | I=175105 MODE=40755 SIZE=512 | MTIME=Jan 18 15:14:48 2005 [0 nsec] | CTIME=Jan 18 15:14:48 2005 [0 nsec] | ATIME=Jun 19 03:05:43 2003 [0 nsec] | OWNER=root GRP=wheel LINKCNT=2 FLAGS=0 BLKCNT=4 GEN=4e5151f9 | fsdb (inum: 175105)> cd .. | component `..': fsdb: name `..' not found in current inode directory I checked with camcontrol, the write cache is off (see below), but the queue algorithm modifier is on and cannot be switched off. Digging through the old structures, with find, reveals: | 175101 4 drwxr-xr-x 3 root wheel 512 Sep 1 2002 /usr/X11R6/lib/perl5/site_perl/5.005/i386-freebsd | 175102 4 drwxr-xr-x 2 root wheel 512 Sep 1 2002 /usr/X11R6/lib/perl5/site_perl/5.005/i386-freebsd/auto | 175103 4 drwxr-xr-x 5 root wheel 512 Aug 23 2002 /usr/sup | 175104 4 drwxr-xr-x 2 root wheel 512 Jan 19 13:29 /usr/sup/src-all > 175105 4 drwxr-xr-x 2 root wheel 512 Jan 18 15:14 /usr/sup/ports-all | 175106 4 drwxr-xr-x 2 root wheel 512 Jan 18 15:14 /usr/sup/doc-all | 175107 4 drwxr-xr-x 22 root wheel 1024 Sep 28 19:47 /usr/doc | 175108 4 drwxr-xr-x 6 root wheel 512 Dec 19 13:26 /usr/doc/de_DE.ISO8859-1 | 175109 4 drwxr-xr-x 5 root wheel 512 Dec 27 2003 /usr/doc/de_DE.ISO8859-1/books And, as expected: | # ls -la /usr/sup/ports-all/ | # Why can, under such circumstances, a softupdates filesystem become corrupt so that fsck -p cannot fix it, and it loses has directories without . and ..? kernel/softupdates bug? How can this directory become empty? locate has this information recorded: /usr/sup/ports-all /usr/sup/ports-all/#cvs.cvsup-2279.0 /usr/sup/ports-all/checkouts.cvs:. so apparently, three (checkouts.cvs:., . and ..) or four files (perhaps the # file) have disappeared. I'm not sure if fsck will revive them, I want to avoid destroying data useful for debugging. Is the Queue Algorithm Modifier a problem? (see below) I cannot set this to 0 on this drive, "camcontrol: error sending mode select command" with -P0 and -P3. (Micropolis 4345WS) How do I go about providing the file system metadata so someone can take a look at it? The file system is 3.5 G in size, so anything that goes beyond meta data is not feasible. Providing SSH access to the failed machine may work though if I'm sent your OpenSSH v2-format key. # camcontrol inquiry da0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 77HT45XXXX pass0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled # camcontrol modepage da0 -m8 IC: 0 ABPF: 0 CAP: 0 DISC: 0 SIZE: 0 WCE: 0 MF: 0 RCD: 0 ... # camcontrol modepage da0 -m10 RLEC: 0 Queue Algorithm Modifier: 1 QErr: 0 DQue: 0 ... -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 14:23:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62B0616A4CE for ; Wed, 19 Jan 2005 14:23:20 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id D29B443D31 for ; Wed, 19 Jan 2005 14:23:19 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0JENJcM017511 for ; Wed, 19 Jan 2005 08:23:19 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 08:23:19 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0JENJkA017509 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 08:23:19 -0600 (CST) Message-ID: <20050119082319.A17451@Denninger.Net> Date: Wed, 19 Jan 2005 08:23:19 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: OK, it appears to be running, but what's this?! (gmirror) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 14:23:20 -0000 Ok, so I found the "how to get gmirror to play nice" page, and set it up. But, what's this??! Gen2# bsdlabel /dev/mirror/m0s1 # /dev/mirror/m0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 10485760 63 4.2BSD 2048 16384 28552 b: 10485760 10485823 swap c: 490223412 63 unused 0 0 # "raw" part, don't edit d: 41943040 20971583 4.2BSD 2048 16384 28552 e: 125829120 62914623 4.2BSD 2048 16384 28552 f: 83886080 188743743 4.2BSD 2048 16384 28552 g: 167772160 272629823 4.2BSD 2048 16384 28552 h: 48234496 440401983 4.2BSD 2048 16384 28552 partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: An incorrect partition c may cause problems for standard system utilities Uh, no, I didn't do that. The original label was put there during system installation, and I absolutely did not offset "c" Is this still ok, or am I asking for a (bogus) hard error some day when the system attempts access beyond the end of the physical disk? -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 15:08:12 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EB6316A4CE; Wed, 19 Jan 2005 15:08:12 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C552743D53; Wed, 19 Jan 2005 15:08:11 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])AB9A24F8B3; Wed, 19 Jan 2005 16:08:09 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30208-01-6; Wed, 19 Jan 2005 16:08:09 +0100 (CET) Received: from m2a2.dyndns.org (p54854A51.dip.t-dialin.net [84.133.74.81]) B6A974CB53; Wed, 19 Jan 2005 16:08:08 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 7BB11777E3; Wed, 19 Jan 2005 16:08:08 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05127-04; Wed, 19 Jan 2005 16:08:07 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id A1052777E4; Wed, 19 Jan 2005 16:08:07 +0100 (CET) From: Matthias Andree To: Matthias Andree In-Reply-To: (Matthias Andree's message of "Wed, 19 Jan 2005 14:49:40 +0100") References: Date: Wed, 19 Jan 2005 16:08:07 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: freebsd-scsi@freebsd.org cc: freebsd-stable@freebsd.org cc: re@freebsd.org Subject: Re: 4.11-RC3: SCSI+UFS+softupdates corruption (write cache DISABLED!) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 15:08:12 -0000 Matthias Andree writes: > so apparently, three (checkouts.cvs:., . and ..) or four files (perhaps > the # file) have disappeared. I'm not sure if fsck will revive them, I > want to avoid destroying data useful for debugging. OK, I dd'd the whole partition to an SLR tape and ran fsck for interactive repairs. | ** /dev/da0s1g | ** Last Mounted on /usr | ** Phase 1 - Check Blocks and Sizes | ** Phase 2 - Check Pathnames | DIRECTORY CORRUPTED I=175105 OWNER=root MODE=40755 | SIZE=512 MTIME=Jan 18 15:14 2005 | DIR=? | | UNEXPECTED SOFT UPDATE INCONSISTENCY | | SALVAGE? [yn] y | | MISSING '.' I=175105 OWNER=root MODE=40755 | SIZE=512 MTIME=Jan 18 15:14 2005 | DIR=? | | UNEXPECTED SOFT UPDATE INCONSISTENCY | | FIX? [yn] y | | MISSING '..' I=175105 OWNER=root MODE=40755 | SIZE=512 MTIME=Jan 18 15:14 2005 | DIR=/sup/ports-all | | UNEXPECTED SOFT UPDATE INCONSISTENCY | | FIX? [yn] y | | ** Phase 3 - Check Connectivity | ** Phase 4 - Check Reference Counts | UNREF FILE I=176801 OWNER=root MODE=100644 | SIZE=14098161 MTIME=Jan 18 15:14 2005 | RECONNECT? [yn] y | | NO lost+found DIRECTORY | CREATE? [yn] y | | UNREF FILE I=179558 OWNER=root MODE=100644 | SIZE=8327913 MTIME=Mar 20 03:11 2004 | RECONNECT? [yn] y | | ** Phase 5 - Check Cyl groups | FREE BLK COUNT(S) WRONG IN SUPERBLK | SALVAGE? [yn] y | | SUMMARY INFORMATION BAD | SALVAGE? [yn] y | | BLK(S) MISSING IN BIT MAPS | SALVAGE? [yn] y | | 243085 files, 1465923 used, 274252 free (102444 frags, 21476 blocks, 5.9% fragmentation) | | ***** FILE SYSTEM MARKED CLEAN ***** | | ***** FILE SYSTEM WAS MODIFIED ***** Turns out the missing two files ended up in lost+found. Is this a failure mode that is allowed to happen for softupdates? -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 15:27:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B263716A4CE for ; Wed, 19 Jan 2005 15:27:04 +0000 (GMT) Received: from nabi1.snu.ac.kr (nabi1.snu.ac.kr [147.46.100.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3EF743D55 for ; Wed, 19 Jan 2005 15:27:03 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.100.31] ([147.46.100.31]) by nabi1.snu.ac.kr ([147.46.100.51]) with ESMTP id 2005012000:28:17:395844.29014.2999966640 for ; Thu, 20 Jan 2005 00:28:17 +0900 (KST) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2005012000:27:00:173620.4758.2830064560 for ; Thu, 20 Jan 2005 00:27:00 +0900 (KST) Message-ID: <41EE7C44.2010407@yahoo.com> Date: Thu, 20 Jan 2005 00:27:00 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rob Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:4.60) (by Terrace) cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 15:27:04 -0000 Raymond Wiker wrote: > Peter Jeremy writes: > > On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > > > tunnel="-L 55110:localhost:110 pop3.univ.net" > > > tunnel_up=`pgrep -f -- "${tunnel}"` > > > [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} > > > > >It works beautifully, but why does this also generate one zombie process: > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > > rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 > > > > You get a zombie when a process has exited and the parent hasn't issued > > a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process > > is and that might give you an idea as to what is going wrong. > > Ancient Perl did not collect for children started via the > backtick operator - is this a possible issue for /bin/sh as well? It > should be harmless to call wait just after the use of the backtick > operator above; does that change anything? I.e: > > tunnel_up=`pgrep -f -- "${tunnel}"`; wait > > To see the parent pid, add "-O ppid" to the arguments to ps; > e.g, > > ps axww -O ppid Adding the "wait" here does not help at all. When I verify the parent process I have this: PID PPID TT STAT TIME COMMAND USER %CPU %MEM VSZ RSS STARTED 423 417 ?? I 0:00.00 cron: running jo root 0.0 0.2 1360 1148 11:38PM 425 423 ?? Z 0:00.00 lahaye 0.0 0.0 0 0 11:38PM So PID 423 "cron: running job (cron)" is the parent of my zombie. After playing with commenting out lines, I found out that the ssh call is the reason for the zombie: "/usr/bin/ssh -N -f -L 55110:localhost:110 pop3.univ.net" Then I tried exec : "exec /usr/bin/ssh -N -f ..." And I also tried & : "/usr/bin/ssh -N -f ... &" Both to no avail. What else can I try, and why is this ssh command causing a zombie process when called from cron? Rob. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 15:47:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50A8816A4CE for ; Wed, 19 Jan 2005 15:47:15 +0000 (GMT) Received: from oslex.fast.no (pat-gw.osl.fast.no [217.144.235.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24C5C43D1F for ; Wed, 19 Jan 2005 15:47:14 +0000 (GMT) (envelope-from Raymond.Wiker@fast.no) Received: from raw.grenland.fast.no.fast.no ([192.168.48.104] RDNS failed) by oslex.fast.no with Microsoft SMTPSVC(6.0.3790.211); Wed, 19 Jan 2005 16:47:12 +0100 From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16878.33022.866459.717977@raw.grenland.fast.no> Date: Wed, 19 Jan 2005 16:47:10 +0100 To: Rob In-Reply-To: <41EE7C44.2010407@yahoo.com> References: <41EE7C44.2010407@yahoo.com> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid X-OriginalArrivalTime: 19 Jan 2005 15:47:12.0535 (UTC) FILETIME=[2466A270:01C4FE3E] cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 15:47:15 -0000 Rob writes: > Raymond Wiker wrote: > > Peter Jeremy writes: > > > On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > > > > tunnel="-L 55110:localhost:110 pop3.univ.net" > > > > tunnel_up=`pgrep -f -- "${tunnel}"` > > > > [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} > > > > > > >It works beautifully, but why does this also generate one zombie process: > > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > > > rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 > > > > > > You get a zombie when a process has exited and the parent hasn't issued > > > a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process > > > is and that might give you an idea as to what is going wrong. > > > > Ancient Perl did not collect for children started via the > > backtick operator - is this a possible issue for /bin/sh as well? It > > should be harmless to call wait just after the use of the backtick > > operator above; does that change anything? I.e: > > > > tunnel_up=`pgrep -f -- "${tunnel}"`; wait > > > > To see the parent pid, add "-O ppid" to the arguments to ps; > > e.g, > > > > ps axww -O ppid > > Adding the "wait" here does not help at all. > > When I verify the parent process I have this: > > PID PPID TT STAT TIME COMMAND USER %CPU %MEM VSZ RSS STARTED > 423 417 ?? I 0:00.00 cron: running jo root 0.0 0.2 1360 1148 11:38PM > 425 423 ?? Z 0:00.00 lahaye 0.0 0.0 0 0 11:38PM > > > So PID 423 "cron: running job (cron)" is the parent of my zombie. > > After playing with commenting out lines, I found out that the ssh call is the > reason for the zombie: "/usr/bin/ssh -N -f -L 55110:localhost:110 pop3.univ.net" > > Then I tried exec : "exec /usr/bin/ssh -N -f ..." > And I also tried & : "/usr/bin/ssh -N -f ... &" > Both to no avail. > > What else can I try, and why is this ssh command causing a zombie process when > called from cron? Hmm... Maybe this will work? /bin/sh -c "/usr/bin/ssh -n -f ${tunnel} &" --- the effect of this should (hopefully) be that init becomes the parent of the zombie process. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 16:10:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 419A416A4CE for ; Wed, 19 Jan 2005 16:10:09 +0000 (GMT) Received: from freedombi.com (thedalesgroup.com [207.179.98.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id A40AA43D1F for ; Wed, 19 Jan 2005 16:10:08 +0000 (GMT) (envelope-from charles@idealso.com) Received: by freedombi.com (Postfix, from userid 1000) id E5428728F9; Wed, 19 Jan 2005 11:10:07 -0500 (EST) Received: from freedombi.com (localhost [192.168.10.108]) by freedombi.com (Postfix) with ESMTP id 31A9E727F9; Wed, 19 Jan 2005 11:10:06 -0500 (EST) Received: from 207.179.91.96 (proxying for unknown) (SquirrelMail authenticated user charles); by freedombi.com with HTTP; Wed, 19 Jan 2005 11:10:06 -0500 (EST) Message-ID: <1737.207.179.91.96.1106151006.squirrel@207.179.91.96> In-Reply-To: <200501190003.20614.olivier.certner@free.fr> References: <41ECC3A7.8040300@ISI.EDU> <200501190003.20614.olivier.certner@free.fr> Date: Wed, 19 Jan 2005 11:10:06 -0500 (EST) From: "Charles Ulrich" To: "Olivier Certner" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on freedombi.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.63 cc: freebsd-stable@freebsd.org Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 16:10:09 -0000 Olivier Certner said: > Hi, > > Do you mean that the sound seems unclear all the time? > > I've also had some problems with sound on my FreeBSD 5.3-STABLE, but a > different kind of. Sometimes I hear crakings while playing mp3 files with > XMMS, although my computer's load is very low. I use "snd_emu10k1" sound > module as you do with a Creative Sound Blaster Live! 5.1. > > There is another driver that may be worth trying here: > http://chibis.persons.gfk.ru/audigy/. I'll give it a pick when I get more > time. > > Cheers, I too had problems with a SoundBlaster Live card on a workstation running 5.2.1. Sometimes the sound was nice and clean, but most of the time it was just horrible. Nothing I did had any noticable effect and the mailing lists unusually quiet on the issue, so I gave up. The emu10k1 cards are the best you can buy in their price range, and I didn't want to replace it. Since I needed the machine for sound work (recording and MIDI), I was forced to put Gentoo on it. YMMV. -- Charles Ulrich Ideal Solution, LLC - http://www.idealso.com From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 16:33:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14F4116A4CE for ; Wed, 19 Jan 2005 16:33:08 +0000 (GMT) Received: from nabi1.snu.ac.kr (nabi1.snu.ac.kr [147.46.100.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 562E643D48 for ; Wed, 19 Jan 2005 16:33:07 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.100.31] ([147.46.100.31]) by nabi1.snu.ac.kr ([147.46.100.51]) with ESMTP id 2005012001:34:21:025171.29014.2979003312 for ; Thu, 20 Jan 2005 01:34:21 +0900 (KST) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2005012001:33:02:932952.4758.2923326384 for ; Thu, 20 Jan 2005 01:33:02 +0900 (KST) Message-ID: <41EE8BBF.1010408@yahoo.com> Date: Thu, 20 Jan 2005 01:33:03 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rob , freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:10.58) (by Terrace) Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 16:33:08 -0000 Raymond Wiker wrote: > Rob writes: > > Raymond Wiker wrote: > > > Peter Jeremy writes: > > > > On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote: > > > > > tunnel="-L 55110:localhost:110 pop3.univ.net" > > > > > tunnel_up=`pgrep -f -- "${tunnel}"` > > > > > [ "${tunnel_up}" = "" ] && /usr/bin/ssh -N -f ${tunnel} > > > > > > > > >It works beautifully, but why does this also generate one zombie process: > > > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > > > > rob 655 0.0 0.0 0 0 ?? Z Sat02PM 0:00.01 > > > > > > > > You get a zombie when a process has exited and the parent hasn't issued > > > > a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process > > > > is and that might give you an idea as to what is going wrong. > > > > > > Ancient Perl did not collect for children started via the > > > backtick operator - is this a possible issue for /bin/sh as well? It > > > should be harmless to call wait just after the use of the backtick > > > operator above; does that change anything? I.e: > > > > > > tunnel_up=`pgrep -f -- "${tunnel}"`; wait > > > > > > To see the parent pid, add "-O ppid" to the arguments to ps; > > > e.g, > > > > > > ps axww -O ppid > > > > Adding the "wait" here does not help at all. > > > > When I verify the parent process I have this: > > > > PID PPID TT STAT TIME COMMAND USER %CPU %MEM VSZ RSS STARTED > > 423 417 ?? I 0:00.00 cron: running jo root 0.0 0.2 1360 1148 11:38PM > > 425 423 ?? Z 0:00.00 lahaye 0.0 0.0 0 0 11:38PM > > > > > > So PID 423 "cron: running job (cron)" is the parent of my zombie. > > > > After playing with commenting out lines, I found out that the ssh call is the > > reason for the zombie: "/usr/bin/ssh -N -f -L 55110:localhost:110 pop3.univ.net" > > > > Then I tried exec : "exec /usr/bin/ssh -N -f ..." > > And I also tried & : "/usr/bin/ssh -N -f ... &" > > Both to no avail. > > > > What else can I try, and why is this ssh command causing a zombie process when > > called from cron? > > Hmm... Maybe this will work? > > /bin/sh -c "/usr/bin/ssh -n -f ${tunnel} &" > > --- the effect of this should (hopefully) be that init becomes the > parent of the zombie process. No, makes no difference. Peculiar of the problem is: I use this construct to keep a ssh-tunnel alive. What else is better, than having a cron-script check whether the tunnel is still active, and if not, re-establish the ssh-tunnel. Strange, that such an obvious contruct ends up with a zombie process. Another interesting detail: as soon as I kill the tunnel, created by the cron-script, then the zombie process also disappears. Does that give a clue? Any more suggestions how to tackle this? Thsnks, Rob. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 16:51:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FF0416A4E6 for ; Wed, 19 Jan 2005 16:51:58 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BE5F43D46 for ; Wed, 19 Jan 2005 16:51:58 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j0JGpva0097493 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 10:51:57 -0600 (CST) (envelope-from dan) Date: Wed, 19 Jan 2005 10:51:57 -0600 From: Dan Nelson To: freebsd-stable@freebsd.org Message-ID: <20050119165157.GA93125@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: panic: Duplicate free of item 0xc37aa200 from zone 0xc103f9a0(Mbuf) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 16:51:58 -0000 I've gotten this one twice in 5 days (still have the cores if anyone needs more info): FreeBSD dan.emsphone.com 5.3-STABLE FreeBSD 5.3-STABLE #387: Thu Jan 13 14:43:03 CST 2005 zsh@dan.emsphone.com:/usr/src/sys/i386/compile/DANSMP i386 panic: Duplicate free of item 0xc37aa200 from zone 0xc103f9a0(Mbuf) #0 doadump () at pcpu.h:159 #1 0xc059c1c6 in boot (howto=260) at ../../../kern/kern_shutdown.c:410 #2 0xc059bc3b in panic (fmt=0xc079a0b3 "Duplicate free of item %p from zone %p(%s)\n") at ../../../kern/kern_shutdown.c:566 #3 0xc06e4b96 in uma_dbg_free (zone=0xc103f9a0, slab=0xc37aafa8, item=0xc37aa200) at ../../../vm/uma_dbg.c:299 #4 0xc06e2ce0 in uma_zfree_arg (zone=0xc103f9a0, item=0xc37aa200, udata=0x0) at ../../../vm/uma_core.c:2257 #5 0xc05d760c in m_freem (mb=0x0) at uma.h:302 #6 0xc05d8d15 in m_defrag (m0=0xc37aa200, how=1) at ../../../kern/uipc_mbuf.c:1124 #7 0xc068d49a in dc_start (ifp=0xc238d000) at ../../../pci/if_dc.c:3337 #8 0xc05bf76d in taskqueue_run (queue=0xc2324900) at ../../../kern/subr_taskqueue.c:191 #9 0xc05854f2 in ithread_loop (arg=0xc227d900) at ../../../kern/kern_intr.c:547 #10 0xc05843f9 in fork_exit (callout=0xc0585310 , arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:807 #11 0xc071a3dc in fork_trampoline () at ../../../i386/i386/exception.s:209 panic: Duplicate free of item 0xc274d000 from zone 0xc103f9a0(Mbuf) #0 doadump () at pcpu.h:159 #1 0xc059c1c6 in boot (howto=260) at ../../../kern/kern_shutdown.c:410 #2 0xc059bc3b in panic (fmt=0xc079a0b3 "Duplicate free of item %p from zone %p(%s)\n") at ../../../kern/kern_shutdown.c:566 #3 0xc06e4b96 in uma_dbg_free (zone=0xc103f9a0, slab=0xc274dfa8, item=0xc274d000) at ../../../vm/uma_dbg.c:299 #4 0xc06e2ce0 in uma_zfree_arg (zone=0xc103f9a0, item=0xc274d000, udata=0x0) at ../../../vm/uma_core.c:2257 #5 0xc05d760c in m_freem (mb=0x0) at uma.h:302 #6 0xc05d8d15 in m_defrag (m0=0xc274d000, how=1) at ../../../kern/uipc_mbuf.c:1124 #7 0xc068d49a in dc_start (ifp=0xc238d000) at ../../../pci/if_dc.c:3337 #8 0xc05bf76d in taskqueue_run (queue=0xc2324900) at ../../../kern/subr_taskqueue.c:191 #9 0xc05854f2 in ithread_loop (arg=0xc227d900) at ../../../kern/kern_intr.c:547 #10 0xc05843f9 in fork_exit (callout=0xc0585310 , arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:807 #11 0xc071a3dc in fork_trampoline () at ../../../i386/i386/exception.s:209 -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 18:28:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D7716A4CE for ; Wed, 19 Jan 2005 18:28:27 +0000 (GMT) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EA4D43D62 for ; Wed, 19 Jan 2005 18:28:26 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [127.0.0.1] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 28FC3BA008 for ; Wed, 19 Jan 2005 20:28:25 +0200 (EET) Message-ID: <41EEA6CB.2030201@pp.nic.fi> Date: Wed, 19 Jan 2005 20:28:27 +0200 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0 / FreeBSD 5.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41ECC3A7.8040300@ISI.EDU> <200501190003.20614.olivier.certner@free.fr> <1737.207.179.91.96.1106151006.squirrel@207.179.91.96> In-Reply-To: <1737.207.179.91.96.1106151006.squirrel@207.179.91.96> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: poor sound quality in 5.3 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 18:28:27 -0000 Charles Ulrich wrote: >I too had problems with a SoundBlaster Live card on a workstation running >5.2.1. Sometimes the sound was nice and clean, but most of the time it was >just horrible. Nothing I did had any noticable effect and the mailing lists >unusually quiet on the issue, so I gave up. The emu10k1 cards are the best you >can buy in their price range, and I didn't want to replace it. Since I needed >the machine for sound work (recording and MIDI), I was forced to put Gentoo on >it. YMMV. > > > Could this be shared irq issue? Though, i have seen it only in windoze. Different pci-slot might help. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 18:37:17 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E2B616A4CE for ; Wed, 19 Jan 2005 18:37:17 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E195343D49 for ; Wed, 19 Jan 2005 18:37:16 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so10854wri for ; Wed, 19 Jan 2005 10:37:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=WrISr/NT+CeM/U/JAHULnL3UQo+YThtyQV0LOnzF7rt8yAET547/AlVHBSTDbpQVwCaRA2L8mxQWSkF2+BNAIVTrc/co1E8T/WgaJuL+O9BuRsbGjcE1ah/ylfPsvozKX/OTIaOkKxDhnxjIovuhgpNsmAozDn6h0jI+pRHxpso= Received: by 10.54.7.10 with SMTP id 10mr47168wrg; Wed, 19 Jan 2005 10:37:15 -0800 (PST) Received: by 10.54.33.22 with HTTP; Wed, 19 Jan 2005 10:37:14 -0800 (PST) Message-ID: <747dc8f305011910372f6bbc6c@mail.gmail.com> Date: Wed, 19 Jan 2005 16:37:14 -0200 From: Renato Botelho To: whitevamp In-Reply-To: <20050118105945.M12726@vampextream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050118105945.M12726@vampextream.com> cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: ruby and portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Renato Botelho List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 18:37:17 -0000 On Tue, 18 Jan 2005 03:01:46 -0800, whitevamp wrote: > 1. what would be causeing this?? > 2. how do i fix this? I had a problem like this today on one box, and I fixed it doing it: Insert these two lines on /usr/local/etc/pkgtools.conf ENV['PKG_DBDRIVER'] ||= 'dbm_hash' ENV['PORTS_DBDRIVER'] ||= 'dbm_hash' Rebuild your pkgdb.db using `pkgdb -fu` Rebuild your INDEX.db using `portsdb -u` After I did it all worked fine! -- Renato Botelho ICQ: 54596223 AIM: RBGargaBR From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 18:46:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 017EE16A4CE for ; Wed, 19 Jan 2005 18:46:55 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DDC043D55 for ; Wed, 19 Jan 2005 18:46:54 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so14180wri for ; Wed, 19 Jan 2005 10:46:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Q+xKhGPo5qPq87kCwJ3fzqMzjTod1owtsHmxSxVMDRN8M9OPxpy3rfHcW7PQ8K0mgOkOIb6E7mkuZuSPhILRy+DkxbXH9pi0TlEY4LcV74k9+7ErIbNrsOEhHCkHNaPU1vBK7TndEL2ZWc8MMNB3oTGMR3YjQ2l+bBqUv6T/WAg= Received: by 10.54.52.62 with SMTP id z62mr176507wrz; Wed, 19 Jan 2005 10:46:51 -0800 (PST) Received: by 10.54.33.22 with HTTP; Wed, 19 Jan 2005 10:46:51 -0800 (PST) Message-ID: <747dc8f30501191046192b0259@mail.gmail.com> Date: Wed, 19 Jan 2005 16:46:51 -0200 From: Renato Botelho To: whitevamp In-Reply-To: <20050118105945.M12726@vampextream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050118105945.M12726@vampextream.com> cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: ruby and portupgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Renato Botelho List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 18:46:55 -0000 On Tue, 18 Jan 2005 03:01:46 -0800, whitevamp wrote: > 1. what would be causeing this?? > 2. how do i fix this? Just completing my previous email, before run pkgdb -fu and portsdb -u, I recompile and reinstall ruby-bdb1 I forgot to say it... =) -- Renato Botelho ICQ: 54596223 AIM: RBGargaBR From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 19:27:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24EDE16A4CE for ; Wed, 19 Jan 2005 19:27:39 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF90743D41 for ; Wed, 19 Jan 2005 19:27:38 +0000 (GMT) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 4B13F3C62 for ; Wed, 19 Jan 2005 12:27:35 -0700 (MST) Received: from wcosvs03.cos.agilent.com (wcosvs03.cos.agilent.com [130.29.152.233]) by relcos1.cos.agilent.com (Postfix) with ESMTP id DB8C52DC for ; Wed, 19 Jan 2005 12:27:37 -0700 (MST) Received: from mina.soco.agilent.com ([141.121.54.157]) by wcosvs03.cos.agilent.com with InterScan Messaging Security Suite; Wed, 19 Jan 2005 12:27:36 -0700 Received: from mina.soco.agilent.com (localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id LAA07487; Wed, 19 Jan 2005 11:27:35 -0800 (PST) Message-Id: <200501191927.LAA07487@mina.soco.agilent.com> To: Raymond Wiker In-Reply-To: Your message of "Wed, 19 Jan 2005 16:47:10 +0100." <16878.33022.866459.717977@raw.grenland.fast.no> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Wed, 19 Jan 2005 11:27:35 -0800 From: Darryl Okahata cc: Rob cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 19:27:39 -0000 Raymond Wiker wrote: > Hmm... Maybe this will work? > > /bin/sh -c "/usr/bin/ssh -n -f ${tunnel} &" > > --- the effect of this should (hopefully) be that init becomes the > parent of the zombie process. An easier-to-read way, assuming that a Bourne-compatible shell is used (e.g., /bin/sh and not /bin/csh), would be: ( /usr/bin/ssh -n -f ${tunnel} & ) -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 21:13:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA7CA16A4CE for ; Wed, 19 Jan 2005 21:13:03 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E311D43D3F for ; Wed, 19 Jan 2005 21:13:02 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0JLD2qP022406 for ; Wed, 19 Jan 2005 15:13:02 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 15:13:02 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0JLD1Mh022402 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 15:13:01 -0600 (CST) Message-ID: <20050119151301.A22310@Denninger.Net> Date: Wed, 19 Jan 2005 15:13:01 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 21:13:03 -0000 Hi folks; New one... I've got a 2 x SATA system here I'm playing with in preparation to move over production to 5.x. These drives have been working under 4.x for quite some time - they're 250GB Maxtor disks.... ad4: 239372MB [486344/16/63] at ata2-master SATA150 ad6: 239372MB [486344/16/63] at ata3-master SATA150 The first disk runs nice and happy. The second does too, provided that the load isn't too high. If it is, then I start to get DMA transfer errors, such as the following: ad6: FAILURE - READ_DMA status=51 error=40 LBA=543191 GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, length=102400)] GEOM_MIRROR: Device m0: provider ad6 disconnected. ad6: FAILURE - READ_DMA status=51 error=40 LBA=300463 ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 ad6: FAILURE - READ_DMA timed out ad6: FAILURE - READ_DMA status=51 error=40 ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 ad6: FAILURE - READ_DMA timed out I'm having a lot of trouble believing this is an actual disk problem. Among other things, its happening at different places - not always at the same block. The above (after the first one) are all being provoked with a "dd if=/dev/ad6s1 of=/dev/null bs=100k". Anyone else seeing this with a -STABLE build from the last few days, and only on a secondary (and/or SATA) channel? Note that this disk can be reintegrated into the mirror, and it will rebuild happily. Its only when I put a real working load on it that things act up. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 21:33:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F78416A4CE for ; Wed, 19 Jan 2005 21:33:15 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E11F43D39 for ; Wed, 19 Jan 2005 21:33:15 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: by wproxy.gmail.com with SMTP id 67so10054wri for ; Wed, 19 Jan 2005 13:33:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=mkoSJf/61ltksaiexfQ5/WmcdajQRPHnUB0h2R4uyToeIzJPRdu1GsV81gXr7zNSnI15hNbzBrv2PO3etQ90CtmNMlEKPMJ3TZmjYeqCRwCcD9L4agEpnm8+i3/UOlY9UEDwgy0HJTNZpCc3ci8FvQ2TCA23Mqlkqj2lk+t/xxY= Received: by 10.54.54.39 with SMTP id c39mr200265wra; Wed, 19 Jan 2005 13:33:12 -0800 (PST) Received: by 10.54.39.34 with HTTP; Wed, 19 Jan 2005 13:33:12 -0800 (PST) Message-ID: <8eea040805011913334b140af6@mail.gmail.com> Date: Wed, 19 Jan 2005 13:33:12 -0800 From: Jon Simola To: Karl Denninger , freebsd-stable@freebsd.org In-Reply-To: <20050119151301.A22310@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050119151301.A22310@Denninger.Net> Subject: Re: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jon@abccomm.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 21:33:15 -0000 On Wed, 19 Jan 2005 15:13:01 -0600, Karl Denninger wrote: > I've got a 2 x SATA system here I'm playing with in preparation to move > over production to 5.x. > > These drives have been working under 4.x for quite some time - they're 250GB > Maxtor disks.... > > ad4: 239372MB [486344/16/63] at ata2-master SATA150 > ad6: 239372MB [486344/16/63] at ata3-master SATA150 > > The first disk runs nice and happy. > > The second does too, provided that the load isn't too high. If it is, then I > start to get DMA transfer errors, such as the following: > > ad6: FAILURE - READ_DMA status=51 error=40 > LBA=543191 > GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, > length=102400)] > GEOM_MIRROR: Device m0: provider ad6 disconnected. > ad6: FAILURE - READ_DMA status=51 error=40 > LBA=300463 > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 > ad6: FAILURE - READ_DMA timed out > ad6: FAILURE - READ_DMA status=51 error=40 > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 > ad6: FAILURE - READ_DMA timed out > > I'm having a lot of trouble believing this is an actual disk problem. Among > other things, its happening at different places - not always at the same > block. I've got a few 1U Supermicro boxes running dual SATA drives: ad4: 78167MB [158816/16/63] at ata2-master SATA150 ad6: 78167MB [158816/16/63] at ata3-master SATA150 I've run into all sorts of problems with every one, and changing the IDE channel settings in the BIOS always fixes it. Which really annoys me, because I setup a new box, run it for a couple weeks, then the drives start getting flaky under load. Then I go change the setting in the BIOS (that I always forget to do on initial setup) and it's dead stable for months at a time. I've had the exact same problem with FreeBSD 5.3 and OpenBSD 3.5 as well. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 21:39:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6261216A4CE for ; Wed, 19 Jan 2005 21:39:46 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id C128743D54 for ; Wed, 19 Jan 2005 21:39:45 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0JLdjqP022664 for ; Wed, 19 Jan 2005 15:39:45 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 15:39:45 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0JLdjcO022662; Wed, 19 Jan 2005 15:39:45 -0600 (CST) Message-ID: <20050119153945.A22642@Denninger.Net> Date: Wed, 19 Jan 2005 15:39:45 -0600 From: Karl Denninger To: jon@abccomm.com, freebsd-stable@freebsd.org References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <8eea040805011913334b140af6@mail.gmail.com>; from Jon Simola on Wed, Jan 19, 2005 at 01:33:12PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 21:39:46 -0000 On Wed, Jan 19, 2005 at 01:33:12PM -0800, Jon Simola wrote: > On Wed, 19 Jan 2005 15:13:01 -0600, Karl Denninger wrote: > > > I've got a 2 x SATA system here I'm playing with in preparation to move > > over production to 5.x. > > > > These drives have been working under 4.x for quite some time - they're 250GB > > Maxtor disks.... > > > > ad4: 239372MB [486344/16/63] at ata2-master SATA150 > > ad6: 239372MB [486344/16/63] at ata3-master SATA150 > > > > The first disk runs nice and happy. > > > > The second does too, provided that the load isn't too high. If it is, then I > > start to get DMA transfer errors, such as the following: > > > > ad6: FAILURE - READ_DMA status=51 error=40 > > LBA=543191 > > GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, > > length=102400)] > > GEOM_MIRROR: Device m0: provider ad6 disconnected. > > ad6: FAILURE - READ_DMA status=51 error=40 > > LBA=300463 > > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 > > ad6: FAILURE - READ_DMA timed out > > ad6: FAILURE - READ_DMA status=51 error=40 > > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 > > ad6: FAILURE - READ_DMA timed out > > > > I'm having a lot of trouble believing this is an actual disk problem. Among > > other things, its happening at different places - not always at the same > > block. > > I've got a few 1U Supermicro boxes running dual SATA drives: > ad4: 78167MB [158816/16/63] at ata2-master SATA150 > ad6: 78167MB [158816/16/63] at ata3-master SATA150 > > I've run into all sorts of problems with every one, and changing the > IDE channel settings in the BIOS always fixes it. Which really annoys > me, because I setup a new box, run it for a couple weeks, then the > drives start getting flaky under load. Then I go change the setting in > the BIOS (that I always forget to do on initial setup) and it's dead > stable for months at a time. > > I've had the exact same problem with FreeBSD 5.3 and OpenBSD 3.5 as well. There are no channel settings available on this system in the BIOS... (Dell 400SC) I am running the most current BIOS as well, if it matters..... -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 21:42:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 135B116A4D3; Wed, 19 Jan 2005 21:42:33 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC9BD43D39; Wed, 19 Jan 2005 21:42:32 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id j0JLgTTA082822; Wed, 19 Jan 2005 16:42:31 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0JLgTBC082821; Wed, 19 Jan 2005 16:42:29 -0500 (EST) (envelope-from wayne) Date: Wed, 19 Jan 2005 16:42:29 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org Message-ID: <20050119214229.GE1168@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 21:42:33 -0000 CVS today. Dual Opteron running 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 Following the instructions in UPDATING, I get the following, indicating a bad kernel. 2 questions: 1) Is this a known, corrected issue as of today? I ran another CVSUP and did not see any changed to src. 2) More importantly, I recovered by loading /boot/kernel.old/kernel and the box is up BUT I am concerned that the NEXT time that I do "make installkernel" I'll stomp on kernel.old losing this fallback procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save but is there something else I should save? Or is there another suggested procedure? /\/\ \/\/ The box failed with: Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 22:10:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AA2916A4CE for ; Wed, 19 Jan 2005 22:10:55 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65A4243D2F for ; Wed, 19 Jan 2005 22:10:54 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id 80B261F87BF4; Wed, 19 Jan 2005 23:10:53 +0100 (CET) Date: Wed, 19 Jan 2005 23:10:53 +0100 From: Roman Neuhauser To: freebsd-stable@freebsd.org Message-ID: <20050119221053.GC79433@isis.wad.cz> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: 5.3-RELEASE/amd64 kernel panic with GENERIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 22:10:55 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, this is what I got after running buildkernel on 5.3-RELEASE with GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM (transcribed as I didn't have the opportunity to set up crashdumps; does it work in 5.3-REL?): page fault while in kernel mode fault virtual address = 0xffffffff00496328 fault code = supervisor write, page not present instruction pointer = 0x8:0xffffffff8050364f stack pointer = 0x10:0xffffffffb0404ad0 frame pointer = 0x10:0xffffffff00496300 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2607 (cc1) trap number = 12 panic: page fault Uptime: 6m41s /var/run/dmesg.boot and the output of pciconf -lv attached -- FreeBSD 4.10-STABLE 10:57PM up 14:29, 5 users, load averages: 0.00, 0.00, 0.00 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 2800+ (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1610547200 (1535 MB) avail memory = 1543385088 (1471 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci1: at device 0.1 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe000-0xe07f mem 0xcfffef80-0xcfffefff irq 19 at device 8.0 on pci0 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:50:da:68:1b:69 re0: port 0xdc00-0xdcff mem 0xcfffee00-0xcfffeeff irq 16 at device 11.0 on pci0 miibus1: on re0 rgephy0: on miibus1 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:11:09:96:0b:fd atapci0: port 0xe400-0xe47f,0xe800-0xe80f,0xec00-0xec3f mem 0xcffc0000-0xcffdffff,0xcffff000-0xcfffffff irq 17 at device 13.0 on pci0 atapci0: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 fwohci0: port 0xd800-0xd87f mem 0xcfffe000-0xcfffe7ff irq 19 at device 14.0 on pci0 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:10:dc:00:00:7c:14:73 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:10:dc:7c:14:73 fwe0: Ethernet address: 02:10:dc:7c:14:73 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci1: port 0xc000-0xc0ff,0xc400-0xc40f,0xc800-0xc803,0xcc00-0xcc07,0xd000-0xd003,0xd400-0xd407 irq 20 at device 15.0 on pci0 ata5: channel #0 on atapci1 ata6: channel #1 on atapci1 atapci2: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci2 ata1: channel #1 on atapci2 uhci0: port 0xb000-0xb01f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb400-0xb41f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb800-0xb81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbc00-0xbc1f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) acpi_button1: on acpi0 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 fdc0: [FAST] 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 ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xce800-0xd27ff,0xcd800-0xce7ff,0xcd000-0xcd7ff,0xc0000-0xccfff on isa0 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 Timecounter "TSC" frequency 1800075440 Hz quality 800 Timecounters tick every 0.976 msec ata1-master: DMA limited to UDMA33, non-ATA66 cable or device acd0: DVDR at ata1-master UDMA33 ad10: 114498MB [232632/16/63] at ata5-master SATA150 Mounting root from ufs:/dev/ad10s1a WARNING: / was not properly dismounted WARNING: /usr was not properly dismounted /usr: superblock summary recomputed --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pciconf.lv" hostb0@pci0:0:0: class=0x060000 card=0x31881106 chip=0x31881106 rev=0x01 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'Apollo K8HTB CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb1881106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'Apollo K8HTB CPU to AGP 2.0/3.0 Bridge' class = bridge subclass = PCI-PCI xl0@pci0:8:0: class=0x020000 card=0x100010b7 chip=0x920010b7 rev=0x6c hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet re0@pci0:11:0: class=0x020000 card=0x702c1462 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class = network subclass = ethernet atapci0@pci0:13:0: class=0x010400 card=0x702e1462 chip=0x3373105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20378? FastTrak RAID Controller' class = mass storage subclass = RAID fwohci0@pci0:14:0: class=0x0c0010 card=0x702d1462 chip=0x30441106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' class = serial bus subclass = FireWire atapci1@pci0:15:0: class=0x010400 card=0x70201462 chip=0x31491106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = '??? SATA RAID Controller' class = mass storage subclass = RAID atapci2@pci0:15:1: class=0x01018a card=0x70201462 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' class = mass storage subclass = ATA uhci0@pci0:16:0: class=0x0c0300 card=0x70201462 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci1@pci0:16:1: class=0x0c0300 card=0x70201462 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci2@pci0:16:2: class=0x0c0300 card=0x70201462 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci3@pci0:16:3: class=0x0c0300 card=0x70201462 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB none0@pci0:16:4: class=0x0c0320 card=0x70201462 chip=0x31041106 rev=0x86 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:17:0: class=0x060100 card=0x32271106 chip=0x32271106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 PCI-to-ISA Bridge' class = bridge subclass = PCI-ISA none1@pci0:17:5: class=0x040100 card=0x00801462 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class = multimedia subclass = audio hostb1@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI none2@pci1:0:0: class=0x030000 card=0x1005196d chip=0x41521002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Radeon 9600 XT (V350)' class = display subclass = VGA none3@pci1:0:1: class=0x038000 card=0x1004196d chip=0x41721002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'RV360 Radeon 9600 XT - Secondary' class = display --MGYHOYXEY6WxJCY8-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 22:21:22 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3535A16A4CE for ; Wed, 19 Jan 2005 22:21:22 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2E4143D53 for ; Wed, 19 Jan 2005 22:21:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BA8C5511C1; Wed, 19 Jan 2005 14:21:20 -0800 (PST) Date: Wed, 19 Jan 2005 14:21:20 -0800 From: Kris Kennaway To: Roman Neuhauser Message-ID: <20050119222120.GA96163@xor.obsecurity.org> References: <20050119221053.GC79433@isis.wad.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: <20050119221053.GC79433@isis.wad.cz> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: 5.3-RELEASE/amd64 kernel panic with GENERIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 22:21:22 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 19, 2005 at 11:10:53PM +0100, Roman Neuhauser wrote: > Hello, this is what I got after running buildkernel on 5.3-RELEASE with > GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM > (transcribed as I didn't have the opportunity to set up crashdumps; does > it work in 5.3-REL?): Yes. > page fault while in kernel mode > fault virtual address = 0xffffffff00496328 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xffffffff8050364f Try: addr2line -e /path/to/kernel.debug 0xffffffff8050364f Not as good as a real traceback, but at least it's a start. Kris --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7t1gWry0BWjoQKURAs7CAKDJFKg9hr3fYc9YlicMLLy8uMIB1wCgkLhu f6oc0PDkbdRRyow5BRIkJJs= =k3My -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 22:33:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41F9D16A4CE for ; Wed, 19 Jan 2005 22:33:48 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0E0843D54 for ; Wed, 19 Jan 2005 22:33:47 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id 323721F87BF4; Wed, 19 Jan 2005 23:33:47 +0100 (CET) Date: Wed, 19 Jan 2005 23:33:47 +0100 From: Roman Neuhauser To: Kris Kennaway Message-ID: <20050119223347.GA79637@isis.wad.cz> References: <20050119221053.GC79433@isis.wad.cz> <20050119222120.GA96163@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119222120.GA96163@xor.obsecurity.org> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org Subject: Re: 5.3-RELEASE/amd64 kernel panic with GENERIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 22:33:48 -0000 # kris@obsecurity.org / 2005-01-19 14:21:20 -0800: > On Wed, Jan 19, 2005 at 11:10:53PM +0100, Roman Neuhauser wrote: > > Hello, this is what I got after running buildkernel on 5.3-RELEASE with > > GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM > > (transcribed as I didn't have the opportunity to set up crashdumps; does > > it work in 5.3-REL?): > > Yes. ok, I'll try to get that set. > > page fault while in kernel mode > > fault virtual address = 0xffffffff00496328 > > fault code = supervisor write, page not present > > instruction pointer = 0x8:0xffffffff8050364f > > Try: > > addr2line -e /path/to/kernel.debug 0xffffffff8050364f I don't have a debug kernel, this is a system freshly installed from the cd; here's what I get: addr2line -e /boot/kernel/kernel 0xffffffff8050364f ??:0 So, where can I find a 5.3-RELEASE amd64 debug kernel? -- FreeBSD 4.10-STABLE 11:29PM up 15:01, 5 users, load averages: 0.00, 0.00, 0.00 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 23:06:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 671E016A4CE for ; Wed, 19 Jan 2005 23:06:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E566A43D1D for ; Wed, 19 Jan 2005 23:06:04 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so29100wri for ; Wed, 19 Jan 2005 15:06:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YRdUkOGlcu8kZMgrA3VOVrbC9652uGQ91hSP7Oii5fGwYu7anH0isFsms4Q6CBLbyMN5TyaKnBiTsC408CiYLOIsYfPidPg8nVfqAWZwQeST1W2sqM3TlBfZI+/YjId3G1V1nMDQfP3W4Jb87433PrT5FlAa3SjX8iSLZ5vH4ik= Received: by 10.54.53.6 with SMTP id b6mr79482wra; Wed, 19 Jan 2005 15:06:04 -0800 (PST) Received: by 10.54.39.34 with HTTP; Wed, 19 Jan 2005 15:06:04 -0800 (PST) Message-ID: <8eea04080501191506237fc762@mail.gmail.com> Date: Wed, 19 Jan 2005 15:06:04 -0800 From: Jon Simola To: freebsd-stable@freebsd.org In-Reply-To: <8eea040805011913334b140af6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> Subject: Re: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jon@abccomm.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 23:06:05 -0000 On Wed, 19 Jan 2005 13:33:12 -0800, Jon Simola wrote: > I've got a few 1U Supermicro boxes running dual SATA drives: > I've run into all sorts of problems with every one, and changing the > IDE channel settings in the BIOS always fixes it. Which really annoys > me, because I setup a new box, run it for a couple weeks, then the > drives start getting flaky under load. Then I go change the setting in > the BIOS (that I always forget to do on initial setup) and it's dead > stable for months at a time. I was politely asked to actually dig up the settings, which cut through my lack of sleep. I should have done this earlier :) On this one box (Supermicro SuperServer 5013C-T, P4SCE BIOS v1.2c): 5.2.1-RELEASE-p4 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0- 0x7 irq 16 at device 31.2 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] GEOM: create disk ad0 dp=0xc671a560 ad0: 70911MB [144073/16/63] at ata0-master UDMA100 GEOM: create disk ad1 dp=0xc671a460 ad1: 70911MB [144073/16/63] at ata0-slave UDMA100 acd0: CDROM at ata1-master PIO4 That's a pair of SATA 74GB WD Raptors. The BIOS IDE setting is for "Combined" - SATA drives will appear on the Primary IDE channel. On a different box (Supermicro SuperServer 5013C-T, P4SCE BIOS v1.2c): 5.3-STABLE-20050107 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 irq 18 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 acd0: CDROM at ata1-master UDMA33 ad4: 78167MB [158816/16/63] at ata2-master SATA150 ad6: 78167MB [158816/16/63] at ata3-master SATA150 A pair of Maxtor 80GBs, the BIOS is set for "Enhanced", up to 6 drives (4 IDE + 2 SATA). Crazy as though it seems, I wasn't kidding about changing the BIOS. The other 2 settings are "SATA only" and "Auto". When the drives started flaking out (timeouts on reads) I would go into the BIOS and cycle through the BIOS settings. After changing it once or twice, things would be fine for months at a time. My best suspicion is that "something" makes the ICH5 a little flaky, and twiddling the BIOS clears it somehow. My only evidence supporting that is that twice the bios stalled on probing the drives once this error had happened, and I had to physically remove the drives, twiddle the bios settings, and replace the drives before it would work again. On OpenBSD, this problem on the same hardware manifests as a read timeout failure during the initial boot probes. Same fix, play with the BIOS and it suddenly works. There's a term in the Jargon file for this, but I can't recall it at the moment. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 23:15:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A331116A4CE for ; Wed, 19 Jan 2005 23:15:05 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1356443D31 for ; Wed, 19 Jan 2005 23:15:05 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0JNF4Q6023672 for ; Wed, 19 Jan 2005 17:15:04 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 17:15:04 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0JNF4B2023670 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 17:15:04 -0600 (CST) Message-ID: <20050119171504.A23623@Denninger.Net> Date: Wed, 19 Jan 2005 17:15:04 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <8eea04080501191506237fc762@mail.gmail.com>; from Jon Simola on Wed, Jan 19, 2005 at 03:06:04PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 19 Jan 2005 23:15:05 -0000 On Wed, Jan 19, 2005 at 03:06:04PM -0800, Jon Simola wrote: > On a different box (Supermicro SuperServer 5013C-T, P4SCE BIOS v1.2c): ...... > A pair of Maxtor 80GBs, the BIOS is set for "Enhanced", up to 6 drives > (4 IDE + 2 SATA). .... > Crazy as though it seems, I wasn't kidding about changing the BIOS. > The other 2 settings are "SATA only" and "Auto". When the drives > started flaking out (timeouts on reads) I would go into the BIOS and > cycle through the BIOS settings. After changing it once or twice, > things would be fine for months at a time. After swapping the "suspect" drive around in an attempt to get the failure to move to the other disk in the pair I actually got a failure on the OTHER channel (in other words, the problem followed the DISK) That got followed up with a soak test with DOS-based diags, which eventually spat out a hard failure code. It took some effort, since the problem doesn't appear on a quick test nor does it show up at the same block all the time - indeed, the block where it finally pukes is all over the place. Back to Maxtor it goes - it appears that FreeBSD's driver (and the bios, etc) is not at fault here, and was indeed reporting a "real" failure. I guess the mirroring code in 5.3-STABLE actually works :-> -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 01:36:19 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BADE416A4CE for ; Thu, 20 Jan 2005 01:36:19 +0000 (GMT) Received: from dd3.kasserver.com (dd2718.kasserver.com [81.209.184.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id E561943D5A for ; Thu, 20 Jan 2005 01:36:18 +0000 (GMT) (envelope-from freebsd@chillt.de) Received: from [192.168.0.5] (dsl-082-083-049-133.arcor-ip.net [82.83.49.133]) by dd3.kasserver.com (Postfix) with ESMTP id 634812AE1C for ; Thu, 20 Jan 2005 02:35:42 +0100 (CET) Message-ID: <41EF0B1E.6010209@chillt.de> Date: Thu, 20 Jan 2005 02:36:30 +0100 From: Bartosz Fabianowski User-Agent: Mozilla Thunderbird 1.0 (X11/20050107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Persisting troubles with periodic stalls every few minutes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 01:36:19 -0000 Hi list, I have been having a lot of trouble with performance on my laptop, which I first set up with 5.3-RELEASE and constantly keep up to date with 5.3-STABLE. The box runs stable, but periodically, somewhere between every few minutes down to every few seconds, it stalls for 5 seconds. By that I mean that the screen is not being refreshed and all keyboard strokes go into some kind of buffer to get processed when the stall is over. Some key strokes also get lost or reversed in order, which makes this even more annoying. I know that during the stalls, CPU usage goes up to 100%, so it is some process that periodically wakes up and hogs the CPU for a few seconds. Also, during the stalls, there is always a lot of disk activity. The only "special" thing about this machine is that /usr/home is GBDE encrypted. But even when I am not doing anything on that partition, stalls occur. The rate of stalls varies a depending on what I am doing. Even when the box is idle, it does stall periodically. But when I am making world, the box becomes almost completely unusable as disk activity on /usr (which is not GBDE encrypted) triggers the same symptoms. The trouble is that I cannot figure out how to find the responsible process. Tools such as top(1) update in one second intervals at best and as there are no screen updates during the stall, so they produce nothing useful. The only tool that gave me some kind of information was systat(1). When I invoke "systat -vmstat 1", I see the following: When everything is working normally, the CPU is at: 15% system 30% user 65% idle At the first screen update after a stall, the CPU is at: 15% system 85% user 0% idle Also, the VM statistics such as "zfod" and "ofod" have jumped from their usual zero level to several thousand. And disk activity is reported as high, of course. A couple seconds after the stall is over, all statistics return to their normal values. So, some user process is misbehaving. And has been doing so ever since this box was set up. Plus, it is somehow disk related and happens no matter what I am running or not, what I am doing or not. Any ideas on how to debug this? How can I find the guilty process? Thanks for any and all input, - Bartosz Fabianowski PS: According to sysctl, DMA is enabled on both ata and atapi so that is not the issue. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:02:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0B7716A4CE; Thu, 20 Jan 2005 03:02:42 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 859C643D46; Thu, 20 Jan 2005 03:02:42 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])9F5FC3787C; Thu, 20 Jan 2005 04:02:41 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29750-03; Thu, 20 Jan 2005 04:02:36 +0100 (CET) Received: from m2a2.dyndns.org (p508EF896.dip.t-dialin.net [80.142.248.150]) A01A54CCED; Thu, 20 Jan 2005 04:02:36 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 9F25A87C09; Thu, 20 Jan 2005 04:02:35 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17812-05-3; Thu, 20 Jan 2005 04:02:34 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 2D29D87C08; Thu, 20 Jan 2005 04:02:34 +0100 (CET) Date: Thu, 20 Jan 2005 04:02:33 +0100 From: "matthias.andree" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906 X-Accept-Language: de, en, fr MIME-Version: 1.0 To: freebsd-gnats-submit@FreeBSD.org, matthias.andree@gmx.de, re@freebsd.org, stable@freebsd.org, freebsd-bugs@freebsd.org X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20050120030234.2D29D87C08@merlin.emma.line.org> X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: Re: gnu/76381: FreeBSD 4.11-RC3 GCC preprocessor failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:02:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (puts on brown paperbag to not be recognized) Please close this problem report, the problem is non-existent. Turns out that GCC is fine, e2fsprogs was grabbing an obsolete header file from below /usr/local, and gcc34 actually wasn't working when compiling e2fsprogs on FreeBSD 5... how embarrassing. (This is a long-standing bug.) Shuffling around the -I CPPFLAGS fixes the problem. PR against ports/sysutils/e2fsprogs (updating it to 1.35_4) to fix the bug in the right place has been filed as ports/76488. My fault. Please accept my apologies for this false alarm. - -- Matthias Andree -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQe8fSSdEoB0mv1ypAQIOJwQAjWN1OpS+NPHBylk8fRVV4TOhHyj3BpxK q5+QJmJOMNsGL73brkamILJ95g8ApPD4+K/XmXx1OhgYYHU34GXKqkErKXt/OtOs 3sEdX4yLC7klut7kOAPvQnrJKGu0Ki5QjhS1P0oPoB04enH1UR07xsg2b3nrN5+m KhhG4VGnwG4= =zl8r -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:17:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27AC316A4CE for ; Thu, 20 Jan 2005 03:17:46 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF51E43D48 for ; Thu, 20 Jan 2005 03:17:45 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] (sam@[66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j0K3HdWi075643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jan 2005 19:17:40 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41EF22F0.7010009@errno.com> Date: Wed, 19 Jan 2005 19:18:08 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karl Denninger References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> In-Reply-To: <20050119171504.A23623@Denninger.Net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:17:46 -0000 I have had spectacularly bad luck with Maxtor SATA drives. I've already RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the rest failed completely while in operation (typically locking up the machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial ATA drives. After testing for power, cables, disk controller, motherboard, and other potential reasons I've decided the drives were just faulty and have switched to another vendor. Sam From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:19:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFFCE16A4CE for ; Thu, 20 Jan 2005 03:19:44 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9646343D1D for ; Thu, 20 Jan 2005 03:19:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6F4D55129D; Wed, 19 Jan 2005 19:19:43 -0800 (PST) Date: Wed, 19 Jan 2005 19:19:43 -0800 From: Kris Kennaway To: Bartosz Fabianowski Message-ID: <20050120031943.GA75048@xor.obsecurity.org> References: <41EF0B1E.6010209@chillt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <41EF0B1E.6010209@chillt.de> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: Persisting troubles with periodic stalls every few minutes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:19:45 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 02:36:30AM +0100, Bartosz Fabianowski wrote: > When everything is working normally, the CPU is at: > 15% system 30% user 65% idle >=20 > At the first screen update after a stall, the CPU is at: > 15% system 85% user 0% idle >=20 > Also, the VM statistics such as "zfod" and "ofod" have jumped from their= =20 > usual zero level to several thousand. And disk activity is reported as=20 > high, of course. A couple seconds after the stall is over, all=20 > statistics return to their normal values. >=20 > So, some user process is misbehaving. And has been doing so ever since=20 > this box was set up. Plus, it is somehow disk related and happens no=20 > matter what I am running or not, what I am doing or not. >=20 > Any ideas on how to debug this? How can I find the guilty process? Try top, ps, systat, etc. Kris --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7yNPWry0BWjoQKURAgOKAJ99eMOGwimx6nH/0AT1ybbdKBS3IwCfUdW+ o3QlWs0Ecgl8f9f+SYDIDiA= =1SPK -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:19:50 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F328A16A505; Thu, 20 Jan 2005 03:19:49 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6ACB43D46; Thu, 20 Jan 2005 03:19:49 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id C176D72DD4; Wed, 19 Jan 2005 19:19:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id BEB7372DCB; Wed, 19 Jan 2005 19:19:49 -0800 (PST) Date: Wed, 19 Jan 2005 19:19:49 -0800 (PST) From: Doug White To: "Michael R. Wayne" In-Reply-To: <20050119214229.GE1168@manor.msen.com> Message-ID: <20050119191813.H78340@carver.gumbysoft.com> References: <20050119214229.GE1168@manor.msen.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:19:50 -0000 On Wed, 19 Jan 2005, Michael R. Wayne wrote: > CVS today. Dual Opteron running > 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > Following the instructions in UPDATING, I get the following, > indicating a bad kernel. 2 questions: > > 1) Is this a known, corrected issue as of today? I ran another > CVSUP and did not see any changed to src. Looks like your SCSi controller stopped probing. You'll need to look at the dmesg more closely to identify why. > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure? You can use "make reinstallkernel", which will just spam over the current one without rotating it. I'd make the backup anyway in case you screw up; its also nice to keep a known working kenrel around Just In Case. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:30:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CF0D16A4CE for ; Thu, 20 Jan 2005 03:30:31 +0000 (GMT) Received: from superman.pns.networktel.net (superman.pns.networktel.net [216.83.236.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09CDD43D53 for ; Thu, 20 Jan 2005 03:30:31 +0000 (GMT) (envelope-from phill@sysctl.net) Received: from jor-l.pns.networktel.net (jor-l.pns.networktel.net [216.83.236.236])j0K3UUA1036242 for ; Thu, 20 Jan 2005 03:30:30 GMT (envelope-from phill@sysctl.net) Received: from MESE (wifi-ipnet.sysctl.net [216.83.242.102]) j0K3TPC6046626 for ; Thu, 20 Jan 2005 03:29:26 GMT (envelope-from phill@sysctl.net) From: "Phillip Salzman" To: Date: Wed, 19 Jan 2005 21:30:53 -0600 Message-ID: <00b001c4fea0$7533d490$6745a8c0@MESE> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.29.0.5; VDF 6.29.0.52 Subject: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:30:31 -0000 Hello, I have a pair of servers that act as SMTP/AV gateways. It seems that = even though we've told the AV software not to store messages, it is anyway. They've been running for a little while now - and recently we've noticed = a lot of disk space disappearing. Shortly after that, a simple du into = our /var/spool returned a not so nice error: du: fts_read: Cannot allocate memory No matter what command I run on that directory, I just don't seem to = have enough available resources to show the files let alone delete them = (echo *, ls, find, rm -rf, etc.) I'm hoping someone else here might have a suggestion as to what I can do = to fix this. Thanks, Phillip Salzman From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:36:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC20616A4CE for ; Thu, 20 Jan 2005 03:36:07 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13DF343D3F for ; Thu, 20 Jan 2005 03:36:07 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0K3a5AS026514 for ; Wed, 19 Jan 2005 21:36:05 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 21:36:05 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0K3a5IW026512 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 21:36:05 -0600 (CST) Message-ID: <20050119213605.B26294@Denninger.Net> Date: Wed, 19 Jan 2005 21:36:05 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <41EF22F0.7010009@errno.com>; from Sam Leffler on Wed, Jan 19, 2005 at 07:18:08PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:36:08 -0000 On Wed, Jan 19, 2005 at 07:18:08PM -0800, Sam Leffler wrote: > I have had spectacularly bad luck with Maxtor SATA drives. I've already > RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the > rest failed completely while in operation (typically locking up the > machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial > ATA drives. After testing for power, cables, disk controller, > motherboard, and other potential reasons I've decided the drives were > just faulty and have switched to another vendor. > > Sam These two are DiamondMax10s - let's hope that this doesn't apply to that line as well. I'm going to be royally POd if so. One RMA is already issued and that one is going back - hopefully the replacement is good. If not, I will not be amused.... BTW I've had relatively bad luck with recent WD drives - which is why I decided to try the Maxtors. My experience with WDs is that in a server they last about a year before locking up with unrecoverable errors which cannot be cleared except by a power cycle. The lockup extends to the host bus; it appears that the microcode is holding either DREQ or DACK on the cable and as such that entire PATA bus is locked out. I've sent two back in the last six months with the exact same problem - WD has been replacing them, but this failure mode is very ugly as it takes down the machine that they're in at the time, RAID or no RAID. What 'other vendor' have you found that makes RELIABLE SATA disks in the high capacity (e.g. 200-300gb) arena? -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:37:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 440FB16A4CE for ; Thu, 20 Jan 2005 03:37:57 +0000 (GMT) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA11D43D39 for ; Thu, 20 Jan 2005 03:37:54 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id j0K3beu2023310; Wed, 19 Jan 2005 19:37:40 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.1/8.13.1/Submit) id j0K3bYAB023309; Wed, 19 Jan 2005 19:37:34 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Wed, 19 Jan 2005 19:37:34 -0800 From: "David G. Lawrence" To: Sam Leffler Message-ID: <20050120033734.GA594@opteron.dglawrence.com> References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EF22F0.7010009@errno.com> cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:37:57 -0000 > I have had spectacularly bad luck with Maxtor SATA drives. I've already > RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the > rest failed completely while in operation (typically locking up the > machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial > ATA drives. After testing for power, cables, disk controller, > motherboard, and other potential reasons I've decided the drives were > just faulty and have switched to another vendor. Yeah, the 6Y series Maxtor is particularly bad. More than half of all of them that I've had (a few dozen in total) have gone bad. The 7Y series is a slightly better, but still well short of an acceptable failure rate. On the other hand, the Hitachi 7K250 and 7K400 series SATA drives have worked quite well for us, with failure rates in the low single digits. Seagate SATA drives also seem to be reliable, although they don't perform very well. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 03:47:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50C3A16A4CF; Thu, 20 Jan 2005 03:47:59 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC01E43D1F; Thu, 20 Jan 2005 03:47:57 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IALJW000.2AS; Wed, 19 Jan 2005 19:48:00 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005011919505908873 ; Wed, 19 Jan 2005 19:50:59 -0800 From: "Vinod Kashyap" To: Michael Meltzer Date: Wed, 19 Jan 2005 19:47:45 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=-------797c823797c823 Message-ID: cc: freebsd stable cc: Jean-Yves Avenard cc: freebsd-amd64@freebsd.org cc: freebsd-scsi@FreeBSD.org Subject: RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 03:47:59 -0000 This is a multi-part message in MIME format ---------797c823797c823 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Strange... CAM doesn't seem to be sending down inquiries to the twa driver, although it was requested to do so (twa_request_bus_scan). I have seen this kind of behavior on 5.x, when doing kldload of the driver, and when logical units are created/deleted on the fly. Although the SIM (twa) requests for a bus scan, CAM never sends down inquiries, and the logical units underneath don't get detected. This behavior is not consistent, and happens some times only. However, I have never seen a case where CAM fails to send inquiries when twa is integrated into the kernel. Do any CAM experts know what might be happening? Also strange is the fact that twa of 5.3-RELEASE works fine. In the attached patch, I have tried to revert back to the way XPT_PATH_INQ is handled by twa of 5.3-RELEASE. Could you apply it to RELENG_5 and let me know the results? > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer > Sent: Tuesday, January 18, 2005 9:47 PM > To: Vinod Kashyap > Cc: Jean-Yves Avenard > Subject: Re: twa breakage on AMD64 > with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit > = > = > twa_patch2.diff, had to add the "int error; in twa_alloc_req_pkts > = > -mjm > = > = > = > Copyright (c) 1992-2005 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 5.3-STABLE #17: Wed Jan 19 00:44:33 EST 2005 > root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0xf51 Stepping =3D 1 > = > Features=3D0x78bfbff ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=3D0xe0500800 > real memory =3D 6442450944 (6144 MB) > avail memory =3D 5963784192 (5687 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > unknown: I/O range not supported > unknown: I/O range not supported > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > twa_probe: entered > pcib1: at device 6.0 on pci0 > pci1: on pcib1 > twa_probe: entered > pci1: at device 6.0 (no driver attached) > twa_probe: entered > isab0: at device 7.0 on pci0 > isa0: on isab0 > twa_probe: entered > atapci0: port > 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > twa_probe: entered > pci0: at device 7.2 (no driver attached) > twa_probe: entered > pci0: at device 7.3 (no driver attached) > twa_probe: entered > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > twa_probe: entered > bge0: mem > 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:50:45:5b:8e:76 > twa_probe: entered > bge1: mem > 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:50:45:5b:8e:77 > twa_probe: entered > atapci1: port > 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem > 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device = > 5.0 on pci2 > atapci1: failed: rid 0x20 is memory, requested 4 > ata2: channel #0 on atapci1 > ata3: channel #1 on atapci1 > ata4: channel #2 on atapci1 > ata5: channel #3 on atapci1 > twa_probe: entered > pci0: at device 10.1 = > (no driver > attached) > twa_probe: entered > pcib3: at device 11.0 on pci0 > pci3: on pcib3 > twa_probe: entered > 3ware device driver for 9000 series storage controllers, version: > 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem > 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device = > 2.0 on pci3 > unknown: twa_attach: entered. > twa0: [GIANT-LOCKED] > twa0: twa_setup: entered. > twa0: twa_setup_request_dmamap: entered. > twa0: twa_setup_request_dmamap: error =3D 0, segs[0].addr =3D = > 17f2da000, len > =3D 40000 > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_init_ctlr: entered. > twa0: twa_wait_status: entered. > twa0: twa_drain_response_queue: entered. > twa0: twa_init_connection: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_request: entered. > twa0: twa_execute_scsi: SCSI I/O request 0x3 > twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_enqueue_aen: entered. > twa0: twa_enqueue_aen: AEN queue empty > twa0: twa_release_request: entered. > twa0: twa_init_ctlr: exiting. > twa0: twa_describe_controller: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > twa0: twa_cam_setup: sc =3D 0xffffffff8082f000 > twa0: twa_cam_setup: Calling cam_sim_alloc > twa0: twa_cam_setup: Calling xpt_bus_register > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_cam_setup: Calling xpt_create_path > twa0: twa_cam_setup: Calling xpt_setup_ccb > twa0: twa_cam_setup: Calling twa_request_bus_scan > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_cam_setup: Exiting > twa_probe: entered > pci0: at device 11.1 = > (no driver > attached) > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse, device ID 3 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > flags 0x10 on > acpi0 > sio0: type 16550A, console > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > ppc0: port = > 0x778-0x77f,0x378-0x37f irq 7 drq > 4 on acpi0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > orm0: at iomem > 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7ff > f on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x100> > 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 > Timecounters tick every 1.000 msec > IP Filter: v3.4.35 initialized. Default =3D pass all, Logging = > =3D disabled > twa0: twa_interrupt: entered. > twa_bus_scan_cb: ccb =3D 0xffffff017f236800 > = > twa_bus_scan_cb: success > acd0: DVDROM at ata0-master UDMA33 > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > = > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0a > ? List valid disk boot devices > Abort manual input > = > mountroo > = > _______________________________________________ > 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" > ---------797c823797c823 Content-Type: application/octet-stream; name="twa_patch3.diff" Content-Disposition: attachment; filename="twa_patch3.diff" Content-Transfer-Encoding: base64 SW5kZXg6IHR3YV9jYW0uYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3Ny Yy9zeXMvZGV2L3R3YS90d2FfY2FtLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMy4yLjEK ZGlmZiAtdSAtcjEuMy4yLjEgdHdhX2NhbS5jCi0tLSB0d2FfY2FtLmMJMTEgSmFuIDIwMDUg MDM6MDA6NDggLTAwMDAJMS4zLjIuMQorKysgdHdhX2NhbS5jCTIwIEphbiAyMDA1IDAzOjI2 OjM1IC0wMDAwCkBAIC00MDksOSArNDA5LDkgQEAKIAkJdHdhX2RiZ19kcHJpbnQoMywgc2Ms ICJYUFRfUEFUSF9JTlEgcmVxdWVzdCIpOwogCiAJCXBhdGhfaW5xLT52ZXJzaW9uX251bSA9 IDE7Ci0JCXBhdGhfaW5xLT5oYmFfaW5xdWlyeSA9IFBJX1dJREVfMTY7CisJCXBhdGhfaW5x LT5oYmFfaW5xdWlyeSA9IDA7CiAJCXBhdGhfaW5xLT50YXJnZXRfc3BydCA9IDA7Ci0JCXBh dGhfaW5xLT5oYmFfbWlzYyB8PSBQSU1fTk9CVVNSRVNFVDsKKwkJcGF0aF9pbnEtPmhiYV9t aXNjID0gMDsKIAkJcGF0aF9pbnEtPmhiYV9lbmdfY250ID0gMDsKIAkJcGF0aF9pbnEtPm1h eF90YXJnZXQgPSBUV0FfTUFYX1VOSVRTOwogCQlwYXRoX2lucS0+bWF4X2x1biA9IDA7Cklu ZGV4OiB0d2FfZnJlZWJzZC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMv c3JjL3N5cy9kZXYvdHdhL3R3YV9mcmVlYnNkLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEu Ny4yLjIKZGlmZiAtdSAtcjEuNy4yLjIgdHdhX2ZyZWVic2QuYwotLS0gdHdhX2ZyZWVic2Qu YwkxMSBKYW4gMjAwNSAwMzowMDo0OCAtMDAwMAkxLjcuMi4yCisrKyB0d2FfZnJlZWJzZC5j CTIwIEphbiAyMDA1IDAzOjI2OjM1IC0wMDAwCkBAIC0yNjEsMTUgKzI2MSw2IEBACiAJc2Mt PnR3YV9idXNfdGFnID0gcm1hbl9nZXRfYnVzdGFnKHNjLT50d2FfaW9fcmVzKTsKIAlzYy0+ dHdhX2J1c19oYW5kbGUgPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnR3YV9pb19yZXMpOwog Ci0JLyogSW5pdGlhbGl6ZSB0aGUgZHJpdmVyIGZvciB0aGlzIGNvbnRyb2xsZXIuICovCi0J aWYgKChlcnJvciA9IHR3YV9zZXR1cChzYykpKSB7Ci0JCXR3YV9mcmVlKHNjKTsKLQkJcmV0 dXJuKGVycm9yKTsKLQl9Ci0KLQkvKiBQcmludCBzb21lIGluZm9ybWF0aW9uIGFib3V0IHRo ZSBjb250cm9sbGVyIGFuZCBjb25maWd1cmF0aW9uLiAqLwotCXR3YV9kZXNjcmliZV9jb250 cm9sbGVyKHNjKTsKLQogCS8qIEFsbG9jYXRlIGFuZCBjb25uZWN0IG91ciBpbnRlcnJ1cHQu ICovCiAJcmVzX2lkID0gMDsKIAlpZiAoKHNjLT50d2FfaXJxX3JlcyA9IGJ1c19hbGxvY19y ZXNvdXJjZShzYy0+dHdhX2J1c19kZXYsIFNZU19SRVNfSVJRLApAQCAtMjg2LDYgKzI3Nywx NSBAQAogCQlyZXR1cm4oRU5YSU8pOwogCX0KIAorCS8qIEluaXRpYWxpemUgdGhlIGRyaXZl ciBmb3IgdGhpcyBjb250cm9sbGVyLiAqLworCWlmICgoZXJyb3IgPSB0d2Ffc2V0dXAoc2Mp KSkgeworCQl0d2FfZnJlZShzYyk7CisJCXJldHVybihlcnJvcik7CisJfQorCisJLyogUHJp bnQgc29tZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgY29udHJvbGxlciBhbmQgY29uZmlndXJh dGlvbi4gKi8KKwl0d2FfZGVzY3JpYmVfY29udHJvbGxlcihzYyk7CisKIAkvKiBDcmVhdGUg dGhlIGNvbnRyb2wgZGV2aWNlLiAqLwogCXNjLT50d2FfY3RybF9kZXYgPSBtYWtlX2Rldigm dHdhX2NkZXZzdywgZGV2aWNlX2dldF91bml0KHNjLT50d2FfYnVzX2RldiksCiAJCQkJCVVJ RF9ST09ULCBHSURfT1BFUkFUT1IsIFNfSVJVU1IgfCBTX0lXVVNSLApAQCAtNTQzLDYgKzU0 Myw3IEBACiB7CiAJc3RydWN0IHR3YV9yZXF1ZXN0CSp0cjsKIAlpbnQJCQlpOworCWludAkJ CWVycm9yOwogCiAJaWYgKChzYy0+dHdhX3JlcV9idWYgPSBtYWxsb2MobnVtX3JlcXMgKiBz aXplb2Yoc3RydWN0IHR3YV9yZXF1ZXN0KSwKIAkJCQkJVFdBX01BTExPQ19DTEFTUywgTV9O T1dBSVQpKSA9PSBOVUxMKQpAQCAtNTk1LDEwICs1OTYsMTIgQEAKIAkJcmV0dXJuKEVOT01F TSk7CiAJfQogCi0JYnVzX2RtYW1hcF9sb2FkKHNjLT50d2FfY21kX3RhZywgc2MtPnR3YV9j bWRfbWFwLAorCWlmICgoZXJyb3IgPSBidXNfZG1hbWFwX2xvYWQoc2MtPnR3YV9jbWRfdGFn LCBzYy0+dHdhX2NtZF9tYXAsCiAJCQkJc2MtPnR3YV9jbWRfcGt0X2J1ZiwKIAkJCQludW1f cmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX2NvbW1hbmRfcGFja2V0KSwKLQkJCQl0d2Ffc2V0 dXBfcmVxdWVzdF9kbWFtYXAsIHNjLCAwKTsKKwkJCQl0d2Ffc2V0dXBfcmVxdWVzdF9kbWFt YXAsIHNjLCBCVVNfRE1BX05PV0FJVCkpKSB7CisJCXR3YV9wcmludGYoc2MsICJidXNfZG1h bWFwX2xvYWQgcmV0dXJuZWQgJWRcbiIsIGVycm9yKTsKKwl9CiAJYnplcm8oc2MtPnR3YV9y ZXFfYnVmLCBudW1fcmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX3JlcXVlc3QpKTsKIAliemVy byhzYy0+dHdhX2NtZF9wa3RfYnVmLAogCQkJbnVtX3JlcXMgKiBzaXplb2Yoc3RydWN0IHR3 YV9jb21tYW5kX3BhY2tldCkpOwpAQCAtNzcwLDYgKzc3Myw4IEBACiAJc3RydWN0IHR3YV9z b2Z0Ywkqc2MgPSAoc3RydWN0IHR3YV9zb2Z0YyAqKWFyZzsKIAogCXR3YV9kYmdfZHByaW50 X2VudGVyKDEwLCBzYyk7CisJdHdhX2RiZ19kcHJpbnQoMywgc2MsICJlcnJvciA9ICVkLCBz ZWdzWzBdLmFkZHIgPSAlbHgsIGxlbiA9ICVseCIsCisJCWVycm9yLCBzZWdzWzBdLmRzX2Fk ZHIsIHNlZ3NbMF0uZHNfbGVuKTsKIAogCXNjLT50d2FfY21kX3BrdF9waHlzID0gc2Vnc1sw XS5kc19hZGRyOwogfQo= ---------797c823797c823-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 04:09:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C261916A4CE for ; Thu, 20 Jan 2005 04:09:20 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF44C43D1F for ; Thu, 20 Jan 2005 04:09:18 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0K49IAS027001 for ; Wed, 19 Jan 2005 22:09:18 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 22:09:18 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0K49IvN026999; Wed, 19 Jan 2005 22:09:18 -0600 (CST) Message-ID: <20050119220918.C26294@Denninger.Net> Date: Wed, 19 Jan 2005 22:09:18 -0600 From: Karl Denninger To: "David G. Lawrence" , Sam Leffler References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> <20050120033734.GA594@opteron.dglawrence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20050120033734.GA594@opteron.dglawrence.com>; from David G. Lawrence on Wed, Jan 19, 2005 at 07:37:34PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 04:09:20 -0000 On Wed, Jan 19, 2005 at 07:37:34PM -0800, David G. Lawrence wrote: > Yeah, the 6Y series Maxtor is particularly bad. More than half of all > of them that I've had (a few dozen in total) have gone bad. The 7Y series > is a slightly better, but still well short of an acceptable failure rate. > On the other hand, the Hitachi 7K250 and 7K400 series SATA drives have > worked quite well for us, with failure rates in the low single digits. > Seagate SATA drives also seem to be reliable, although they don't perform > very well. > > -DG I have some associates that have had major problems with Deskstars in server use, which is why I didn't consider them originally..... They moved them all to desktop machines where they're getting reasonable life from them - albiet at a pricepoint that didn't make sense compared to the Seagates and WDs of smaller capacity. Often this kind of thing is part and parcel of one given model though, which means that unless you're talking the same line/model/whatever, it may not apply, and some of the issues are firmware related - so a production change can make a formerly unacceptable unit "ok" somewhere - or the reverse. This really bites - while I used to have issues with disks now and then when I ran my ISP, it was typically a rare bad lot once in a while. Products with this kind of failure rate just never made it out - now it seems that the manufacturers will throw whatever they can into the market, hoping they survive until the warranty runs out, and there's a trend towards shortening warranties to one year as well! I wonder if someone could go after these guys on their "MTBF" claims which all appear to be WILDLY optimistic..... Ah well, if I can't get the Maxtors to work reasonably well I guess I can try the Deskstar 250s... Thanks for the datapoints guys... (rant off!) -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 05:14:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F5F16A4CE for ; Thu, 20 Jan 2005 05:14:28 +0000 (GMT) Received: from web54002.mail.yahoo.com (web54002.mail.yahoo.com [206.190.36.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8605743D53 for ; Thu, 20 Jan 2005 05:14:27 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 3629 invoked by uid 60001); 20 Jan 2005 05:14:26 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=vWEzn/DJvvCGodacMdsANEMptTI5mcwomJeTG0/VBJp8DuKKqzXRGIqRyCU9Cc+pmn+ecHF2IF3KgSU9HnG0lbWYdhWC2Ss5MkCNCLP7Lin6INJHLQqc2CVQRR8p44vL3VZMCzGNDyl8isZvoZZcHnK2Tz+Yit2e/Nu1ZLjVJcg= ; Message-ID: <20050120051426.3627.qmail@web54002.mail.yahoo.com> Received: from [147.46.44.181] by web54002.mail.yahoo.com via HTTP; Wed, 19 Jan 2005 21:14:26 PST Date: Wed, 19 Jan 2005 21:14:26 -0800 (PST) From: spam maps To: freebsd-stable@freebsd.org In-Reply-To: <200501191927.LAA07487@mina.soco.agilent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 05:14:28 -0000 --- Darryl Okahata wrote: > Raymond Wiker wrote: > > > Hmm... Maybe this will work? > > > > /bin/sh -c "/usr/bin/ssh -n -f ${tunnel} > &" > > > > --- the effect of this should (hopefully) be that > init becomes the > > parent of the zombie process. > > An easier-to-read way, assuming that a > Bourne-compatible shell is > used (e.g., /bin/sh and not /bin/csh), would be: > > ( /usr/bin/ssh -n -f ${tunnel} & ) Alas, no success. Still get the zombie process. I actually wonder if this is an odd or buggy behaviour of ssh, or is cron making a mistake here? Leaving a zombie process around, means there's a kind of bug/mistake somewhere, right? Regards, Rob. __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 07:01:16 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B66D916A4CE for ; Thu, 20 Jan 2005 07:01:16 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0402643D46 for ; Thu, 20 Jan 2005 07:01:16 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j0K71EXt050149; Thu, 20 Jan 2005 01:01:14 -0600 (CST) (envelope-from dan) Date: Thu, 20 Jan 2005 01:01:13 -0600 From: Dan Nelson To: Phillip Salzman Message-ID: <20050120070113.GC7352@dan.emsphone.com> References: <00b001c4fea0$7533d490$6745a8c0@MESE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00b001c4fea0$7533d490$6745a8c0@MESE> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: stable@freebsd.org Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 07:01:16 -0000 In the last episode (Jan 19), Phillip Salzman said: > I have a pair of servers that act as SMTP/AV gateways. It seems that > even though we've told the AV software not to store messages, it is > anyway. > > They've been running for a little while now - and recently we've > noticed a lot of disk space disappearing. Shortly after that, a > simple du into our /var/spool returned a not so nice error: > > du: fts_read: Cannot allocate memory > > No matter what command I run on that directory, I just don't seem to > have enough available resources to show the files let alone delete > them (echo *, ls, find, rm -rf, etc.) Try raising your datasize rlimit value; also see the thread "Directories with 2 million files" at http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026170.html for some other ideas. "find . | xargs rm" sounds promising. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 07:27:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 207E216A4CE for ; Thu, 20 Jan 2005 07:27:41 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF1B043D5C for ; Thu, 20 Jan 2005 07:27:40 +0000 (GMT) (envelope-from imbutler@comcast.net) Received: from auburn.comcast.net (h000086489e8c.ne.client2.attbi.com[66.31.33.127]) by comcast.net (rwcrmhc12) with ESMTP id <20050120072740014000sgr3e>; Thu, 20 Jan 2005 07:27:40 +0000 Received: from localhost (unknown [127.0.0.1]) by auburn.comcast.net (Postfix) with ESMTP id D931317031 for ; Thu, 20 Jan 2005 02:27:39 -0500 (EST) Received: from auburn.comcast.net ([127.0.0.1]) by localhost (auburn.comcast.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32996-03 for ; Thu, 20 Jan 2005 02:27:33 -0500 (EST) Received: from [127.0.0.1] (localhost.comcast.net [127.0.0.1]) by auburn.comcast.net (Postfix) with ESMTP for ; Thu, 20 Jan 2005 02:27:32 -0500 (EST) Message-ID: <41EF5D64.3000004@comcast.net> Date: Thu, 20 Jan 2005 02:27:32 -0500 From: Michael Butler User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <00b001c4fea0$7533d490$6745a8c0@MESE> <20050120070113.GC7352@dan.emsphone.com> In-Reply-To: <20050120070113.GC7352@dan.emsphone.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: at auburn.comcast.net Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 07:27:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Nelson wrote: | Try raising your datasize rlimit value; .. I found this (lots of files in a directory) to be generally a Bad Idea. Search performance tends to be poor even with the improvements in 5.x While I'm not sure that it's possible to in this instance, I have previously in a practical implementation, used OpenLDAP to specify separate 'Maildir' directories for mail storage based on the first letter of the username. Although I'm sure there are better and more distributed hash mechanisms, this was the quickest (and most commercially expedient) to hack into the LDAP database, Michael Butler CISSP Security Consultant SAVVIS Communications www.savvis.net Transforming Information Technology PGP Key ID: 0x5E873CC5 Fingerprint: 2CFF 581F D192 F885 7ED9 3C44 889C A479 5E87 3CC5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFB711kiJykeV6HPMURAtdIAKC4Su7aFuXEO8vIWtFfJZnpr686tACfWsv1 O7LY1ONU2w4Hf+7DtE+ddog= =72Cu -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 08:54:32 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2793216A4CE for ; Thu, 20 Jan 2005 08:54:32 +0000 (GMT) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5849843D48 for ; Thu, 20 Jan 2005 08:54:31 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0K8sTOw012048 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 20 Jan 2005 19:54:30 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0K8sTxP067276 for ; Thu, 20 Jan 2005 19:54:29 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j0K8sTLS067275 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 19:54:29 +1100 (EST) (envelope-from pjeremy) Date: Thu, 20 Jan 2005 19:54:28 +1100 From: Peter Jeremy To: freebsd-stable@freebsd.org Message-ID: <20050120085428.GJ79646@cirb503493.alcatel.com.au> References: <200501191927.LAA07487@mina.soco.agilent.com> <20050120051426.3627.qmail@web54002.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120051426.3627.qmail@web54002.mail.yahoo.com> User-Agent: Mutt/1.4.2i Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 08:54:32 -0000 On Wed, 2005-Jan-19 21:14:26 -0800, spam maps wrote: >> ( /usr/bin/ssh -n -f ${tunnel} & ) > >Alas, no success. Still get the zombie >process. > >I actually wonder if this is an odd or buggy behaviour >of ssh, or is cron making a mistake here? The cron daemon (which will have a PPID of 1) forks a copy of itself to actually handle the cron job (I suspect this is the parent of the zombie that you are seeing). This child process runs "/bin/sh -c CRONJOB" (where CRONJOB is the line in your crontab) and I suspect this is the zombie you are seeing. My guess is that your ssh process is holding open file descriptors and the cron child process is waiting for these descriptors to close before wait()ing for the child. If this is true, then you should avoid it with something like: ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) (or redirect to a suitable file). >Leaving a zombie process around, means there's a kind >of bug/mistake somewhere, right? Yes. But it's not necessarily a bug in FreeBSD :-). -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 09:45:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3472016A4CE for ; Thu, 20 Jan 2005 09:45:57 +0000 (GMT) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 206FB43D31 for ; Thu, 20 Jan 2005 09:45:56 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0K9jqFU023702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Jan 2005 20:45:54 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0K9jqxP067359; Thu, 20 Jan 2005 20:45:52 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0K9jq0F067358; Thu, 20 Jan 2005 20:45:52 +1100 (EST) (envelope-from pjeremy) Date: Thu, 20 Jan 2005 20:45:52 +1100 From: Peter Jeremy To: Phillip Salzman Message-ID: <20050120094551.GK79646@cirb503493.alcatel.com.au> References: <00b001c4fea0$7533d490$6745a8c0@MESE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00b001c4fea0$7533d490$6745a8c0@MESE> User-Agent: Mutt/1.4.2i cc: stable@freebsd.org Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 09:45:57 -0000 On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: >They've been running for a little while now - and recently we've noticed a >lot of disk space disappearing. Shortly after that, a simple du into our >/var/spool returned a not so nice error: > > du: fts_read: Cannot allocate memory > >No matter what command I run on that directory, I just don't seem to have >enough available resources to show the files let alone delete them (echo *, >ls, find, rm -rf, etc.) I suspect you will need to write something that uses dirent(3) to scan the offending directory and delete (or whatever) the files one by one. Skeleton code (in perl) would look like: chdir $some_dir or die "Can't cd $some_dir: $!"; opendir(DIR, ".") or die "Can't opendir: $!"; while (my $file = readdir(DIR)) { next if ($file eq '.' || $file eq '..'); next if (&this_file_is_still_needed($file)); unlink $file or warn "Unable to delete $file: $!"; } closedir DIR; If you've reached the point where you can't actually read the entire directory into user memory, expect the cleanup to take quite a while. Once you've finished the cleanup, you should confirm that the directory has shrunk to a sensible size. If not, you need to re-create the directory and move the remaining files into the new directory. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 10:06:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E73116A4CE for ; Thu, 20 Jan 2005 10:06:39 +0000 (GMT) Received: from web54002.mail.yahoo.com (web54002.mail.yahoo.com [206.190.36.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C3F7C43D45 for ; Thu, 20 Jan 2005 10:06:38 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 88176 invoked by uid 60001); 20 Jan 2005 10:06:38 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=azpsYoenFhWZN+P49EpxjAo5lzQpr2Ni1aRNm/rDCn4UEyAXb8KHysSfQOG7MFe4ilfoxIqy+U3H/j9tXWvzfCwXtFIovz7wZI40TDPB6acqStAFQ/u5g6hkZ10vJzWMgvzXvXl/vcwx6UmG+D2oBCawD3KclyxdxVAOSoYp6VY= ; Message-ID: <20050120100638.88174.qmail@web54002.mail.yahoo.com> Received: from [147.46.44.181] by web54002.mail.yahoo.com via HTTP; Thu, 20 Jan 2005 02:06:38 PST Date: Thu, 20 Jan 2005 02:06:38 -0800 (PST) From: spam maps To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 10:06:39 -0000 Peter Jeremy wrote: > On Wed, 2005-Jan-19 21:14:26 -0800, spam maps wrote: > >>> ( /usr/bin/ssh -n -f ${tunnel} & ) >> >>Alas, no success. Still get the zombie >>process. >> >>I actually wonder if this is an odd or buggy >>behaviour of ssh, or is cron making a mistake here? > > > The cron daemon (which will have a PPID of 1) forks > a copy of itself to actually handle the cron job > (I suspect this is the parent of the zombie that > you are seeing). This child process runs > "/bin/sh -c CRONJOB" (where CRONJOB is the line in > your crontab) and I suspect this is the zombie you > are seeing. > > My guess is that your ssh process is holding open > file descriptors and the cron child process is > waiting for these descriptors to close before > wait()ing for the child. If this is true, then you > should avoid it with something like: > ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) > BINGO! That works. Zombie has gone. Thank you. >>Leaving a zombie process around, means there's a kind >>of bug/mistake somewhere, right? > > Yes. But it's not necessarily a bug in FreeBSD :-). So, after you've given me a complicated solution to avoid the zombie, can you tell which program is at error here? Cron, ssh, or FreeBSD? Rob. __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 10:25:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0C6416A4CE for ; Thu, 20 Jan 2005 10:25:29 +0000 (GMT) Received: from nuumen.pair.com (nuumen.pair.com [209.68.1.119]) by mx1.FreeBSD.org (Postfix) with SMTP id 7669343D2F for ; Thu, 20 Jan 2005 10:25:29 +0000 (GMT) (envelope-from thuppi@nuumen.pair.com) Received: (qmail 99509 invoked by uid 55300); 20 Jan 2005 10:25:29 -0000 Date: Thu, 20 Jan 2005 05:25:28 -0500 (EST) From: Tom Huppi X-X-Sender: thuppi@nuumen.pair.com To: spam maps In-Reply-To: <20050120100638.88174.qmail@web54002.mail.yahoo.com> Message-ID: References: <20050120100638.88174.qmail@web54002.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 10:25:30 -0000 On Thu, 20 Jan 2005, spam maps wrote: > Peter Jeremy wrote: > > On Wed, 2005-Jan-19 21:14:26 -0800, spam maps wrote: > > > >>> ( /usr/bin/ssh -n -f ${tunnel} & ) > >> > >>Alas, no success. Still get the zombie > >>process. > >> > >>I actually wonder if this is an odd or buggy > >>behaviour of ssh, or is cron making a mistake here? > > > > > > The cron daemon (which will have a PPID of 1) forks > > a copy of itself to actually handle the cron job > > (I suspect this is the parent of the zombie that > > you are seeing). This child process runs > > "/bin/sh -c CRONJOB" (where CRONJOB is the line in > > your crontab) and I suspect this is the zombie you > > are seeing. > > > > My guess is that your ssh process is holding open > > file descriptors and the cron child process is > > waiting for these descriptors to close before > > wait()ing for the child. If this is true, then you > > should avoid it with something like: > > ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) > > > > BINGO! > That works. Zombie has gone. Thank you. > > >>Leaving a zombie process around, means there's a > kind > >>of bug/mistake somewhere, right? > > > > Yes. But it's not necessarily a bug in FreeBSD :-). > > So, after you've given me a complicated solution to > avoid the zombie, can you tell which program is at > error here? Cron, ssh, or FreeBSD? There are two other possibilities I could thing of off hand; Bourne Shell, or indeed, the 'program' (albeit a small one) which you wrote! My vote would be the latter. I vote that way because a change in the code (based on a good knowledge of the mechanics of the language and unix in general) made the problem go away. It's mainly a matter of perspective I guess :) Thanks, - Tom From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 11:30:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D0B916A4CE for ; Thu, 20 Jan 2005 11:30:33 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F05043D6B for ; Thu, 20 Jan 2005 11:30:32 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ezklyv@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id j0KBUKwB066100 for ; Thu, 20 Jan 2005 12:30:20 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id j0KBUKMZ066099; Thu, 20 Jan 2005 12:30:20 +0100 (CET) (envelope-from olli) Date: Thu, 20 Jan 2005 12:30:20 +0100 (CET) Message-Id: <200501201130.j0KBUKMZ066099@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20050120094551.GK79646@cirb503493.alcatel.com.au> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:30:33 -0000 Peter Jeremy wrote: > On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: > > They've been running for a little while now - and recently we've noticed a > > lot of disk space disappearing. Shortly after that, a simple du into our > > /var/spool returned a not so nice error: > > > > du: fts_read: Cannot allocate memory > > > > No matter what command I run on that directory, I just don't seem to have > > enough available resources to show the files let alone delete them (echo *, > > ls, find, rm -rf, etc.) > > I suspect you will need to write something that uses dirent(3) to scan > the offending directory and delete (or whatever) the files one by one. > > Skeleton code (in perl) would look like: > [...] I would suggest trying this simple hack: cd /var/spool/directory ; cat . | strings | xargs rm -f It's a dirty hack, but might work, if the file names in that directory aren't too strange (no spaces etc.). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 12:14:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D3D216A4CE for ; Thu, 20 Jan 2005 12:14:07 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEDB643D54 for ; Thu, 20 Jan 2005 12:14:06 +0000 (GMT) (envelope-from phoa.sec@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so91245rnf for ; Thu, 20 Jan 2005 04:14:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ohqb4sw1YxP8tLxNnjn457IoWCrM3+aWNaz0ayD4ayKrqIrTTgU6sTMrT4bDLtKBooRDSKgIYLheG57bVNULY55vbnuzl8RvfLWvv0Kc5cgIcOTWiPwI30K0qi1jjqMQTcv9dLQbeEnsr5ht3TQmq9SnkePM0JjY1ZEe69/oejI= Received: by 10.38.11.19 with SMTP id 19mr301422rnk; Thu, 20 Jan 2005 04:14:06 -0800 (PST) Received: by 10.38.97.6 with HTTP; Thu, 20 Jan 2005 04:14:06 -0800 (PST) Message-ID: Date: Thu, 20 Jan 2005 20:14:06 +0800 From: PhoA Sec To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: PhoA Sec List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 12:14:07 -0000 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 12:15:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B86D016A4CE for ; Thu, 20 Jan 2005 12:15:24 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B4843D48 for ; Thu, 20 Jan 2005 12:15:23 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id j0KCFCZV010559; Thu, 20 Jan 2005 12:15:12 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id j0KCFBjc068691; Thu, 20 Jan 2005 12:15:11 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id j0KCFBCP068690; Thu, 20 Jan 2005 12:15:11 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Bartosz Fabianowski In-Reply-To: <41EF0B1E.6010209@chillt.de> References: <41EF0B1E.6010209@chillt.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 20 Jan 2005 12:15:10 +0000 Message-Id: <1106223310.68614.4.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: freebsd-stable@freebsd.org Subject: Re: Persisting troubles with periodic stalls every few minutes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 12:15:24 -0000 On Thu, 2005-01-20 at 02:36 +0100, Bartosz Fabianowski wrote: > Hi list, > > I have been having a lot of trouble with performance on my laptop, which > I first set up with 5.3-RELEASE and constantly keep up to date with > 5.3-STABLE. The box runs stable, but periodically, somewhere between > every few minutes down to every few seconds, it stalls for 5 seconds. By > that I mean that the screen is not being refreshed and all keyboard > strokes go into some kind of buffer to get processed when the stall is > over. Some key strokes also get lost or reversed in order, which makes > this even more annoying. > > The trouble is that I cannot figure out how to find the responsible > process. Tools such as top(1) update in one second intervals at best and > as there are no screen updates during the stall, so they produce nothing > useful. The only tool that gave me some kind of information was > systat(1). When I invoke "systat -vmstat 1", I see the following: Try running top with the -q option, and/or pressing space (which causes top to try and refresh immediately). If you still can't get any screen updates to happen during the freeze, try top -qbSs 1 -d max > /var/tmp/somefile And look through the file to see if you can establish what was actually happening at the time of the freeze. Gavin From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 13:18:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 031B116A4CE; Thu, 20 Jan 2005 13:18:39 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id E794B43D4C; Thu, 20 Jan 2005 13:18:37 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0KDIrmi073375; Thu, 20 Jan 2005 14:18:54 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <1106134006.1132.12.camel@genius2.i.cz> References: <1106134006.1132.12.camel@genius2.i.cz> Content-Type: multipart/mixed; boundary="=-k3av6U01ybkct5I0WZMD" Date: Thu, 20 Jan 2005 14:18:30 +0100 Message-Id: <1106227110.716.11.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 13:18:39 -0000 --=-k3av6U01ybkct5I0WZMD Content-Type: text/plain Content-Transfer-Encoding: 7bit I wrote: > Emanuel Strobl wrote: > > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > > Dear experts, > > > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > > the other one not (I hate to say it but both are working under win). > > > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > > ucom0, also I can receive signal but not transmit. > > > > > > [skip] > > > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > > > It can break old (working) PL2303 chip, but it works for me with newer > > > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > > also breakes the 2.02 version :( > > > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > > this information (akiyama?)? > > > > Thanks a lot, > > I've just recently been looking into this too. I used the mentioned > patch and also linux driver source and have come with the attached > patch. It contains one more change but I don't know if it's correct. It > works for both chips on CURRENT for serial console. It detects if the > chip is rev 3.00 and aplies the patch only for it. > > The author of the patch mentions it isn't binary safe - sometimes the > chip stops working. I planned to test it with binary transfers (ppp) > today, check if it's working and submit it (with some cleanup) for > inclusion in FreeBSD. > > Michal Mertl I tested my patch for binary safety on CURRENT yesterday (dialed with ppp) and didn't notice any problem. I'm attaching my patch again because some recipients didn't probably receive it yesterday. Michal --=-k3av6U01ybkct5I0WZMD Content-Disposition: attachment; filename=uplcom.c.pl2303x.diff Content-Type: text/x-patch; name=uplcom.c.pl2303x.diff; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 20 Jan 2005 13:15:40 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -113,30 +116,34 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_CTS 0x80 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define UPLCOM_SET_CRTSCTS_2303X 0x61 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,14 +163,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -299,6 +307,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -374,7 +383,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -617,7 +633,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, UPLCOM_SET_CRTSCTS_2303X); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -713,6 +732,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { /* XXX - shouldn't happen */ \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -743,7 +799,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --=-k3av6U01ybkct5I0WZMD-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 13:28:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC70B16A4CE; Thu, 20 Jan 2005 13:28:23 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEFF343D1F; Thu, 20 Jan 2005 13:28:20 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id 40A187C008; Thu, 20 Jan 2005 08:28:20 -0500 (EST) Message-ID: <41EFB111.8010906@michaelmeltzer.com> Date: Thu, 20 Jan 2005 08:24:33 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd stable cc: Jean-Yves Avenard cc: freebsd-amd64@freebsd.org cc: freebsd-scsi@FreeBSD.org Subject: Re: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 13:28:24 -0000 looks like patch3 worked, good job! I had to turn off TWA_DEBUG to get the boot going, the debug was starving the boot on a 9600 baud terminal. I can increase the speed and caputer the output on monday if it will help(it on the large side, bigger than the 10,000 line capture buffer in am using). I incude 2 iozone reports, the first one the new driver the second one the old driver, Is thier a way to increase the "read ahead" in freebsd?? -mjm iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Iozone: Performance Test of File I/O Version $Revision: 3.196 $ Compiled for 64 bit mode. Build: freebsd Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Jean-Marc Zucconi, Jeff Blomberg. Run began: Thu Jan 20 07:45:52 2005 File size set to 20971520 KB Record Size 60 KB Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Output is in Kbytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 Kbytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. Throughput test with 1 process Each process writes a 20971520 Kbyte file in 60 Kbyte records Children see throughput for 1 initial writers = 78219.47 KB/sec Parent sees throughput for 1 initial writers = 78060.45 KB/sec Min throughput per process = 78219.47 KB/sec Max throughput per process = 78219.47 KB/sec Avg throughput per process = 78219.47 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 rewriters = 19394.53 KB/sec Parent sees throughput for 1 rewriters = 19394.32 KB/sec Min throughput per process = 19394.53 KB/sec Max throughput per process = 19394.53 KB/sec Avg throughput per process = 19394.53 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 readers = 55960.09 KB/sec Parent sees throughput for 1 readers = 55954.25 KB/sec Min throughput per process = 55960.09 KB/sec Max throughput per process = 55960.09 KB/sec Avg throughput per process = 55960.09 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 re-readers = 55948.26 KB/sec Parent sees throughput for 1 re-readers = 55946.60 KB/sec Min throughput per process = 55948.26 KB/sec Max throughput per process = 55948.26 KB/sec Avg throughput per process = 55948.26 KB/sec Min xfer = 20971500.00 KB iozone test complete. iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Iozone: Performance Test of File I/O Version $Revision: 3.196 $ Compiled for 64 bit mode. Build: freebsd Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Jean-Marc Zucconi, Jeff Blomberg. Run began: Mon Dec 20 21:03:36 2004 File size set to 20971520 KB Record Size 60 KB Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Output is in Kbytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 Kbytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. Throughput test with 1 process Each process writes a 20971520 Kbyte file in 60 Kbyte records Children see throughput for 1 initial writers = 78738.67 KB/sec Parent sees throughput for 1 initial writers = 78716.55 KB/sec Min throughput per process = 78738.67 KB/sec Max throughput per process = 78738.67 KB/sec Avg throughput per process = 78738.67 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 rewriters = 32126.46 KB/sec Parent sees throughput for 1 rewriters = 32125.77 KB/sec Min throughput per process = 32126.46 KB/sec Max throughput per process = 32126.46 KB/sec Avg throughput per process = 32126.46 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 readers = 58563.70 KB/sec Parent sees throughput for 1 readers = 58557.14 KB/sec Min throughput per process = 58563.70 KB/sec Max throughput per process = 58563.70 KB/sec Avg throughput per process = 58563.70 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 re-readers = 58583.77 KB/sec Parent sees throughput for 1 re-readers = 58581.98 KB/sec Min throughput per process = 58583.77 KB/sec Max throughput per process = 58583.77 KB/sec Avg throughput per process = 58583.77 KB/sec Min xfer = 20971500.00 KB iozone test complete. Copyright (c) 1992-2005 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 5.3-STABLE #21: Thu Jan 20 01:21:10 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5964316672 (5688 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 twa0: [GIANT-LOCKED] twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 pci0: at device 11.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> 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 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled acd0: DVDROM at ata0-master UDMA33 da0 at twa0 bus 0 target 0 lun 0 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 70550MB (144486400 512 byte sectors: 255H 63S/T 8993C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/da0s1b as swap device Starting file system checks: /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 3005287 free (1559 frags, 375466 blocks, 0.1% fragmentation) /dev/da0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1h: clean, 15168492 free (20 frags, 1896059 blocks, 0.0% fragmentation) /dev/da0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1g: clean, 5010318 free (56766 frags, 619194 blocks, 0.9% fragmentation) /dev/da0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1f: clean, 6078377 free (553 frags, 759728 blocks, 0.0% fragmentation) Enabling ipfilter. ioctl(SIOCIPFL6): Invalid argument Setting hostname: web7.thecenturiongroup.com. Installing NAT rules. 0 entries flushed from NAT table 0 entries flushed from NAT list bge0: flags=8843 mtu 1500 options=1a inet 192.32.248.84 netmask 0xffffff00 broadcast 192.32.248.255 ether 00:50:45:5b:8e:76 media: Ethernet autoselect (none) status: no carrier bge1: flags=8843 mtu 1500 options=1a inet 10.200.0.7 netmask 0xffffff00 broadcast 10.200.0.255 ether 00:50:45:5b:8e:77 media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 filter sync'd add net default: gateway 10.200.0.1 Additional routing options: IP gateway=YES. Starting devd. Mounting NFS file systems:. Starting syslogd. Jan 20 01:24:35 web7 syslogd: kernel boot file is /boot/kernel/kernel ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib Starting usbd. No USB host controllers found Starting local daemons:. Updating motd. Starting ntpd. Jan 20 01:24:35 web7 ntpd[393]: no IPv6 interfaces found Configuring syscons: blanktime screensaver. Starting sshd. Initial amd64 initialization:. Additional ABI support:. Starting cron. Local package initialization:. Additional TCP options:. Starting moused:. Starting inetd. Starting background file system checks in 60 seconds. Thu Jan 20 01:24:36 EST 2005 FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) login: Jan 20 01:24:43 web7 ntpd[393]: sendto(139.88.35.33): No route to host Jan 20 01:24:44 web7 ntpd[393]: sendto(208.184.49.9): No route to host Jan 20 01:24:45 web7 ntpd[393]: sendto(216.200.93.8): No route to host FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) login: From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 13:53:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9CCA16A4CE for ; Thu, 20 Jan 2005 13:53:20 +0000 (GMT) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 591BC43D2F for ; Thu, 20 Jan 2005 13:53:20 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j0KDrE7R065781 for ; Thu, 20 Jan 2005 08:53:14 -0500 (EST) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j0KDrESg065780 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 08:53:14 -0500 (EST) (envelope-from bv) Date: Thu, 20 Jan 2005 08:53:14 -0500 From: Bill Vermillion To: freebsd-stable@freebsd.org Message-ID: <20050120135314.GA65676@wjv.com> References: <20050120120114.27CE616A4E7@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120120114.27CE616A4E7@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on bilver.wjv.com Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 13:53:21 -0000 > > From: "Phillip Salzman" > Subject: Very large directory > I have a pair of servers that act as SMTP/AV gateways. It > seems that even though we've told the AV software not to store > messages, it is anyway. > > They've been running for a little while now - and recently we've > noticed a lot of disk space disappearing. Shortly after that, a > simple du into our /var/spool returned a not so nice error: > du: fts_read: Cannot allocate memory > No matter what command I run on that directory, I just don't > seem to have enough available resources to show the files let > alone delete them (echo *, ls, find, rm -rf, etc.) Even echo * sorts the output, and the sorting consumes a large amount of resources. Try and ls with a "-f" option. To prove it to yourself take any directory and perform echo * and then do the same with ls -f I first noticed this years ago when on an old SysV I had a directory that took 5 minutes to display and the ls -f was quite fast. > End of freebsd-stable Digest, Vol 95, Issue 8 -- Bill Vermillion - bv @ wjv . com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 14:46:13 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1014E16A4CE for ; Thu, 20 Jan 2005 14:46:13 +0000 (GMT) Received: from sferics.mongueurs.net (sferics.mongueurs.net [81.80.147.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A0F43D2F for ; Thu, 20 Jan 2005 14:46:12 +0000 (GMT) (envelope-from david@landgren.net) Received: from [127.0.0.1] (exo.bpinet.com [81.80.147.206]) by sferics.mongueurs.net (Postfix) with ESMTP id 4E24CAA47 for ; Thu, 20 Jan 2005 15:46:10 +0100 (CET) Message-ID: <41EFC430.9010308@landgren.net> Date: Thu, 20 Jan 2005 15:46:08 +0100 From: David Landgren Organization: The Lusty Decadent Delights of Imperial Pompeii User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <00b001c4fea0$7533d490$6745a8c0@MESE> <20050120094551.GK79646@cirb503493.alcatel.com.au> In-Reply-To: <20050120094551.GK79646@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 14:46:13 -0000 Peter Jeremy wrote: > On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: > >>They've been running for a little while now - and recently we've noticed a >>lot of disk space disappearing. Shortly after that, a simple du into our >>/var/spool returned a not so nice error: >> >> du: fts_read: Cannot allocate memory >> >>No matter what command I run on that directory, I just don't seem to have >>enough available resources to show the files let alone delete them (echo *, >>ls, find, rm -rf, etc.) > > > I suspect you will need to write something that uses dirent(3) to scan > the offending directory and delete (or whatever) the files one by one. > > Skeleton code (in perl) would look like: > > chdir $some_dir or die "Can't cd $some_dir: $!"; > opendir(DIR, ".") or die "Can't opendir: $!"; > while (my $file = readdir(DIR)) { > next if ($file eq '.' || $file eq '..'); > next if (&this_file_is_still_needed($file)); > unlink $file or warn "Unable to delete $file: $!"; > } > closedir DIR; similarly, opendir(DIR, $some_dir ) or die "Can't open dir $some_dir: $!"; while ( defined(my $file = readdir(DIR))) { print "$file\n" unless ($file eq '.' || $file eq '..'); } closedir(DIR); ...will print the files one per line, which can be piped to more or redirected to another file. This will let you get a feel for the names of the files in the directory. It could then be cleaned up with various pipelines like egrep 'foo|bar|rat' | xargs rm Note: you want to wrap the my $file = readdir(DIR) in a defined(), otherwise your loop will exit early if you come across a file named 0 (zero). David From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 14:47:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9522716A4CE for ; Thu, 20 Jan 2005 14:47:09 +0000 (GMT) Received: from sferics.mongueurs.net (sferics.mongueurs.net [81.80.147.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5220E43D1F for ; Thu, 20 Jan 2005 14:47:09 +0000 (GMT) (envelope-from david@landgren.net) Received: from [127.0.0.1] (exo.bpinet.com [81.80.147.206]) by sferics.mongueurs.net (Postfix) with ESMTP id CC1DFAA09 for ; Thu, 20 Jan 2005 15:47:08 +0100 (CET) Message-ID: <41EFC46B.6070909@landgren.net> Date: Thu, 20 Jan 2005 15:47:07 +0100 From: David Landgren Organization: The Lusty Decadent Delights of Imperial Pompeii User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <200501201130.j0KBUKMZ066099@lurza.secnetix.de> In-Reply-To: <200501201130.j0KBUKMZ066099@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 14:47:09 -0000 Oliver Fromme wrote: > Peter Jeremy wrote: > > On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: > > > They've been running for a little while now - and recently we've noticed a > > > lot of disk space disappearing. Shortly after that, a simple du into our > > > /var/spool returned a not so nice error: > > > > > > du: fts_read: Cannot allocate memory > > > > > > No matter what command I run on that directory, I just don't seem to have > > > enough available resources to show the files let alone delete them (echo *, > > > ls, find, rm -rf, etc.) > > > > I suspect you will need to write something that uses dirent(3) to scan > > the offending directory and delete (or whatever) the files one by one. > > > > Skeleton code (in perl) would look like: > > [...] > > I would suggest trying this simple hack: > > cd /var/spool/directory ; cat . | strings | xargs rm -f > > It's a dirty hack, but might work, if the file names in > that directory aren't too strange (no spaces etc.). why suggest a dirty hack that might not work, when the proposed Perl script would have worked perfectly? David From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 14:58:40 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94C4C16A4CF for ; Thu, 20 Jan 2005 14:58:40 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id C083343D5C for ; Thu, 20 Jan 2005 14:58:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ghcxin@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id j0KEwcQH075823 for ; Thu, 20 Jan 2005 15:58:38 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id j0KEwce6075822; Thu, 20 Jan 2005 15:58:38 +0100 (CET) (envelope-from olli) Date: Thu, 20 Jan 2005 15:58:38 +0100 (CET) Message-Id: <200501201458.j0KEwce6075822@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <41EFC46B.6070909@landgren.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 14:58:40 -0000 David Landgren wrote: > Oliver Fromme wrote: > > I would suggest trying this simple hack: > > > > cd /var/spool/directory ; cat . | strings | xargs rm -f > > > > It's a dirty hack, but might work, if the file names in > > that directory aren't too strange (no spaces etc.). > > why suggest a dirty hack that might not work, when the proposed Perl > script would have worked perfectly? In this case, the hack _should_ work, and is about 1/10 of the size of the perl script and leaves a lot less room for typing errors. Aport from that, perl might not even be installed on the machine in question, who knows. But of course: YMMV. It was just a suggestion. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 15:13:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CEFB16A4CE for ; Thu, 20 Jan 2005 15:13:07 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77CFC43D70 for ; Thu, 20 Jan 2005 15:13:06 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tgbshk@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id j0KFD5Pj076663 for ; Thu, 20 Jan 2005 16:13:05 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id j0KFD5Xc076662; Thu, 20 Jan 2005 16:13:05 +0100 (CET) (envelope-from olli) Date: Thu, 20 Jan 2005 16:13:05 +0100 (CET) Message-Id: <200501201513.j0KFD5Xc076662@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: ciss(4) adapter not recognized (Compaq/HP Smart Array 6i/64xx) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 15:13:07 -0000 Hi, We've got a new Compaq/HP server machine, but there are problems installing FreeBSD because the RAID controller is not recognized. It's a CISS 6i (according to the specs) which I expected to be recognized by the ciss(4) driver. But unfortunately, it isn't. This is the output from dmesg: pci2: (vendor=0x0e11, dev=0x0046) at 1.0 irq 5 According to pciids.sourceforge.net, 0e11 is Compaq, and 0046 is their ID for the Smart Array 64xx. It is not in the list of supported IDS in src/sys/dev/ciss/ciss.c. Would it work to just add that ID to the list, compile a kernel, and then use that kernel to boot the installation? (I don't have time for many experiments, because the box is installed in a computing centre which is not exactly nearby. That's why I'm asking here first, instead of just trying to insert that ID in the source.) I'm wondering if the device ID is really correct. All the other IDs in the ciss.c source are in the 0x40XX range. 0x0046 seems pretty odd. Also, there's a CISS_BOARD flag associated with each of the devices. Should I set it to SA5 or SA5B for the new ID? (My guess would be SA5, but I could be wrong.) Any hints and advice would be greatly appreciated! Best regards Oliver PS: I'm using 4-stable, but I checked the CVS repository and verified that the device ID is neither in 5-stable nor HEAD. Searching for this device in the list archives gave zero hits. -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:12:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88F3316A4CE for ; Thu, 20 Jan 2005 16:12:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0441843D45 for ; Thu, 20 Jan 2005 16:12:05 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so3018wri for ; Thu, 20 Jan 2005 08:12:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=i3po18Kd675+Qj+uifF2TuVIUL0uXxUg1bjjXVrT5LjQoPcnGSeWm4ayUirNw8RbJBvouwQqVjKD8tW2Wai2OlkZUF1X1H6QnheW2VUy9g6YriYVNLakQ7ITKLZDlK+1IMDJIftMcwxlBSIYAivr+UdeVAGpAMlVhDw2lqRrpu4= Received: by 10.54.46.68 with SMTP id t68mr262863wrt; Thu, 20 Jan 2005 08:12:04 -0800 (PST) Received: by 10.54.29.4 with HTTP; Thu, 20 Jan 2005 08:12:04 -0800 (PST) Message-ID: <790a9fff050120081229a3ec6a@mail.gmail.com> Date: Thu, 20 Jan 2005 10:12:04 -0600 From: Scot Hetzel To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org In-Reply-To: <20050119214229.GE1168@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050119214229.GE1168@manor.msen.com> Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 16:12:05 -0000 On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne wrote: > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure? > When I have a bad kernel I do the following after booting the good kernel. cd /boot rm -rf kernel cp -rp kernel.old kernel cp -rp kernel.old kernel.good This way I can reboot the box without going into the loader to load kernel.old. Scot From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:17:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F064F16A4CE for ; Thu, 20 Jan 2005 16:17:42 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id C46C843D54 for ; Thu, 20 Jan 2005 16:17:42 +0000 (GMT) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 6FF4A2A10 for ; Thu, 20 Jan 2005 09:17:40 -0700 (MST) Received: from wcosvs02.cos.agilent.com (wcosvs02.cos.agilent.com [130.29.152.188]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 576F12A5 for ; Thu, 20 Jan 2005 09:17:42 -0700 (MST) Received: from mina.soco.agilent.com ([141.121.54.157]) by wcosvs02.cos.agilent.com with InterScan Messaging Security Suite; Thu, 20 Jan 2005 09:17:41 -0700 Received: from mina.soco.agilent.com (localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id IAA07355 for ; Thu, 20 Jan 2005 08:17:40 -0800 (PST) Message-Id: <200501201617.IAA07355@mina.soco.agilent.com> To: freebsd-stable@freebsd.org In-Reply-To: Your message of "Wed, 19 Jan 2005 21:36:05 CST." <20050119213605.B26294@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Thu, 20 Jan 2005 08:17:40 -0800 From: Darryl Okahata Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 16:17:43 -0000 Karl Denninger wrote: > These two are DiamondMax10s - let's hope that this doesn't apply to that > line as well. Out of curiosity, why didn't you consider Seagate ? The recent Maxtors that I have, if run 24x7, seem to die just after the warranty expires (for me, just over a year). I'm now switching back to Seagate, as they now have a nice 5-year warranty, but I don't have much experience with these new drives. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:31:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5500816A4CE for ; Thu, 20 Jan 2005 16:31:04 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF22643D54 for ; Thu, 20 Jan 2005 16:31:01 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id BC6905FE7B for ; Thu, 20 Jan 2005 16:30:59 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 16:30:03 +0000 User-Agent: KMail/1.7.91 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501201630.04506.imobachgs@banot.net> Subject: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 16:31:04 -0000 Hi all, I'm havin' a strange problem with my Realtek Network Adapter. On boot, the= =20 detection looks just fine: $ dmesg| grep rl rl0: port 0xd000-0xd0ff mem 0xee000000-0xee000= 0ff =20 irq 10 at device 10.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:40:f4:32:e5:12 However, the performance is very poor. Some examples: * using 'fetch' command, I get a lot of "timeouts", so some "ports" fail to= =20 install (I have to retry). * using Konqueror, for instance, I also get some "timeouts" and a very low= =20 speed connecting to different websites. I've done the some test on the same machine (and on my laptop) using=20 GNU/Linux, and works pretty fine. So I discarded a network hardware issue a= s=20 the origin of the problem. Any ideas? Thank you all in advance. =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:36:21 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAA8A16A4CE for ; Thu, 20 Jan 2005 16:36:21 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 13ADE43D4C for ; Thu, 20 Jan 2005 16:36:16 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 98278 invoked by uid 0); 20 Jan 2005 16:28:25 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.99.7) by mail.freebsd.org.cn with SMTP; 20 Jan 2005 16:28:25 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id EE4E11335C0; Fri, 21 Jan 2005 00:36:10 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44853-14; Fri, 21 Jan 2005 00:35:59 +0800 (CST) Received: from localhost.localdomain (unknown [61.48.135.6]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by beastie.frontfree.net (Postfix) with ESMTP id B8552133598; Fri, 21 Jan 2005 00:35:57 +0800 (CST) From: Xin LI To: "Michael R. Wayne" In-Reply-To: <20050119214229.GE1168@manor.msen.com> References: <20050119214229.GE1168@manor.msen.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NZ7y5Bhvmo3DnfIk7N+N" Organization: The FreeBSD Simplified Chinese Project Date: Fri, 21 Jan 2005 00:34:42 +0800 Message-Id: <1106238882.1019.48.camel@spirit> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at frontfree.net cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: delphij@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 16:36:21 -0000 --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Michael, =E5=9C=A8 2005-01-19=E4=B8=89=E7=9A=84 16:42 -0500=EF=BC=8CMichael R. Wayne= =E5=86=99=E9=81=93=EF=BC=9A > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another=20 > suggested procedure? I personally do: cp -R /boot/kernel /boot/kernel.good If the kernel has provided stability for 30 days. For your case, you may want to do: cp -R /boot/kernel.old /boot/kernel.good since the kernel.old is last known good kernel. Of course kernel.save is a good name. For a STABLE branch you generally won't need to fear that loader changes can prevent you from being able to boot from older kernels. Therefore, I think the procedure you have listed is enough to do. Cheers, --=20 Xin LI http://www.delphij.net/ --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0?= =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8?= =?UTF-8?Q?=E5=88=86?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB792i/cVsHxFZiIoRAmPyAJ0c5XWM/RuUgYSLU+RMmsj/iMFLPgCfQp3Q xqgIceP0t6xDmtNxE1RAac4= =9iwj -----END PGP SIGNATURE----- --=-NZ7y5Bhvmo3DnfIk7N+N-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:54:26 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1152316A4CE for ; Thu, 20 Jan 2005 16:54:26 +0000 (GMT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 845B643D4C for ; Thu, 20 Jan 2005 16:54:25 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KGsOf9041788; Thu, 20 Jan 2005 11:54:24 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 41151-09; Thu, 20 Jan 2005 11:54:24 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KGsNNh041773; Thu, 20 Jan 2005 11:54:23 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KGsGhr045891; Thu, 20 Jan 2005 11:54:17 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.0.14.0.20050120115013.088cd320@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Thu, 20 Jan 2005 11:55:24 -0500 To: Karl Denninger , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050119151301.A22310@Denninger.Net> References: <20050119151301.A22310@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan2b Subject: Re: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 16:54:26 -0000 At 04:13 PM 19/01/2005, Karl Denninger wrote: >I'm having a lot of trouble believing this is an actual disk problem. Among >other things, its happening at different places - not always at the same >block. If you have the drives on a RELENG_5 box, try /usr/ports/sysutils/smartmontools/ Its quite handy to sort of various drive issues as well as to monitor for ongoing errors via the daemon. ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 16:56:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BFA616A4CE for ; Thu, 20 Jan 2005 16:56:35 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA0B43D39 for ; Thu, 20 Jan 2005 16:56:34 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j0KGuXA6039476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jan 2005 08:56:34 -0800 (PST) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id j0KGuXre071006; Thu, 20 Jan 2005 08:56:33 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3aaaa3a0501181530975fecf@mail.gmail.com> Date: Thu, 20 Jan 2005 08:56:33 -0800 (PST) From: John Polstra To: Chris X-Bogosity: No, tests=bogofilter, spamicity=0.099652, version=0.14.5 cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 16:56:35 -0000 On 18-Jan-2005 Chris wrote: > I have been compiling ports using -O2 since I started using FreeBSD > back in 2003 and only port that has had issues with this is lang/ezm3 > in FreeBSD 5.2.1 it needed -O. I fixed that at the beginning of November. John From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 17:09:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 920D116A4CE for ; Thu, 20 Jan 2005 17:09:20 +0000 (GMT) Received: from alpha.VL7.net (CPE00a0242ca70c-CM014090203816.cpe.net.cable.rogers.com [65.50.68.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F7BD43D4C for ; Thu, 20 Jan 2005 17:09:19 +0000 (GMT) (envelope-from vlad@alpha.VL7.net) Received: from alpha.VL7.net (vlad@localhost [127.0.0.1]) by alpha.VL7.net (8.12.10/8.12.10) with ESMTP id j0KH8Vss038800; Thu, 20 Jan 2005 12:08:47 -0500 (EST) (envelope-from vlad@alpha.VL7.net) Received: (from vlad@localhost) by alpha.VL7.net (8.12.10/8.12.10/Submit) id j0KH8GIq038799; Thu, 20 Jan 2005 12:08:16 -0500 (EST) (envelope-from vlad) Date: Thu, 20 Jan 2005 12:08:16 -0500 (EST) From: Vladimir Pianykh Message-Id: <200501201708.j0KH8GIq038799@alpha.VL7.net> To: freebsd-stable@freebsd.org, imobachgs@banot.net In-Reply-To: <200501201630.04506.imobachgs@banot.net> Subject: Re: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vlad@VL7.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 17:09:20 -0000 Hi! I had some problems with "rl" cards with "auto" media. It happens with some kind of hubs. Try to specify type of your network media, for example: # ifconfig rl0 inet 10.0.0.5 netmask 255.255.255.0 media 100baseTX mediaopt full-duplex # route add default 10.0.0.254 Vlad. > From owner-freebsd-stable@freebsd.org Thu Jan 20 11:31:23 2005 > From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= > To: freebsd-stable@freebsd.org > Date: Thu, 20 Jan 2005 16:30:03 +0000 > Subject: Realtek 8139 (rl) very poor performance > > Hi all, > > I'm havin' a strange problem with my Realtek Network Adapter. On boot, the > detection looks just fine: > > $ dmesg| grep rl > rl0: port 0xd000-0xd0ff mem 0xee000000-0xee0000ff > irq 10 at device 10.0 on pci0 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:40:f4:32:e5:12 > > However, the performance is very poor. Some examples: > > * using 'fetch' command, I get a lot of "timeouts", so some "ports" fail to > install (I have to retry). > * using Konqueror, for instance, I also get some "timeouts" and a very low > speed connecting to different websites. > > I've done the some test on the same machine (and on my laptop) using > GNU/Linux, and works pretty fine. So I discarded a network hardware issue as > the origin of the problem. > > Any ideas? > > Thank you all in advance. > > -- > Imobach González Sosa > imobachgs en banot punto net > osoh en jabber.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" > > From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 17:27:50 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DDB816A4CF for ; Thu, 20 Jan 2005 17:27:50 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D534843D4C for ; Thu, 20 Jan 2005 17:27:49 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 20 Jan 2005 09:27:49 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 5038C5D08; Thu, 20 Jan 2005 09:27:48 -0800 (PST) To: spam maps In-reply-to: Your message of "Thu, 20 Jan 2005 02:06:38 PST." <20050120100638.88174.qmail@web54002.mail.yahoo.com> Date: Thu, 20 Jan 2005 09:27:48 -0800 From: "Kevin Oberman" Message-Id: <20050120172748.5038C5D08@ptavv.es.net> cc: freebsd-stable@freebsd.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 17:27:50 -0000 > Date: Thu, 20 Jan 2005 02:06:38 -0800 (PST) > From: spam maps > Sender: owner-freebsd-stable@freebsd.org > > Peter Jeremy wrote: > > On Wed, 2005-Jan-19 21:14:26 -0800, spam maps wrote: > > > >>> ( /usr/bin/ssh -n -f ${tunnel} & ) > >> > >>Alas, no success. Still get the zombie > >>process. > >> > >>I actually wonder if this is an odd or buggy > >>behaviour of ssh, or is cron making a mistake here? > > > > > > The cron daemon (which will have a PPID of 1) forks > > a copy of itself to actually handle the cron job > > (I suspect this is the parent of the zombie that > > you are seeing). This child process runs > > "/bin/sh -c CRONJOB" (where CRONJOB is the line in > > your crontab) and I suspect this is the zombie you > > are seeing. > > > > My guess is that your ssh process is holding open > > file descriptors and the cron child process is > > waiting for these descriptors to close before > > wait()ing for the child. If this is true, then you > > should avoid it with something like: > > ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) > > > > BINGO! > That works. Zombie has gone. Thank you. > > >>Leaving a zombie process around, means there's a > kind > >>of bug/mistake somewhere, right? > > > > Yes. But it's not necessarily a bug in FreeBSD :-). > > So, after you've given me a complicated solution to > avoid the zombie, can you tell which program is at > error here? Cron, ssh, or FreeBSD? FreeBSD is an operating system, not a kernel like Linux. Both cron and ssh are part of FreeBSD. That said, the problem could be in sh or in the program executed, too. I trivial note: -f implies -n. There is no need to specify both, but no harm in doing so. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 17:32:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8CF716A4CE for ; Thu, 20 Jan 2005 17:32:49 +0000 (GMT) Received: from resmo.com (resmo.com [204.202.11.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EA4A43D46 for ; Thu, 20 Jan 2005 17:32:49 +0000 (GMT) (envelope-from gstewart@bonivet.net) X-Resmo-Authenticated-User: [godwin] X-Resmo-Msg-Submitted-By: mail.bonivet.net [81.56.185.133] Received: from dragonfly.bonivet.net (mail.bonivet.net [81.56.185.133]) (authenticated bits=0) by resmo.com (8.13.1/8.12.11) with ESMTP id j0KHWlP5034689 for ; Thu, 20 Jan 2005 17:32:48 GMT Date: Thu, 20 Jan 2005 18:32:40 +0100 From: Godwin Stewart To: freebsd-stable@freebsd.org Message-Id: <20050120183240.44512515.gstewart@bonivet.net> In-Reply-To: <200501201708.j0KH8GIq038799@alpha.VL7.net> References: <200501201630.04506.imobachgs@banot.net> <200501201708.j0KH8GIq038799@alpha.VL7.net> X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i386-unknown-freebsd5.3) X-Face: #T;eJks=B[`71qrwp`l6BW8xI&hP8S*4Kd%e?8o"rL02ZYf"rWa41l83a)L,*; S).Ukq$U% II{-z#5%i&X8"%{$)ZWmE7WBDF)?wK1^7]u9T;@jqdZo?IT!d-L`!@&vW)F_1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 17:32:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 20 Jan 2005 12:08:16 -0500 (EST), Vladimir Pianykh wrote: > I had some problems with "rl" cards with "auto" media. You're probably not the only one. Note this comment from sys/pci/if_rl.c /* * The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is * probably the worst PCI ethernet controller ever made, with the possible * exception of the FEAST chip made by SMC. The 8139 supports bus-master * DMA, but it has a terrible interface that nullifies any performance * gains that bus-master DMA usually offers. - -- G. Stewart - gstewart@bonivet.net Sign spotted outside a second hand shop: WE EXCHANGE ANYTHING - BICYCLES, WASHING MACHINES, ETC. WHY NOT BRING YOUR WIFE ALONG AND GET A WONDERFUL BARGAIN? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7+s4K5oiGLo9AcYRAhFnAJwMVwWjqVG9GgvD4uqqx2kotqB8aACcD7N4 64wIPwIEKgzzQmJgdMn58UU= =17Dp -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 17:57:54 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C6D216A4CE for ; Thu, 20 Jan 2005 17:57:54 +0000 (GMT) Received: from lora.pns.networktel.net (lora.pns.networktel.net [216.83.236.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB6B743D1F for ; Thu, 20 Jan 2005 17:57:53 +0000 (GMT) (envelope-from phill@sysctl.net) Received: from MESE (wifi-ipnet.sysctl.net [216.83.242.102]) j0KHxkTB011455; Thu, 20 Jan 2005 17:59:47 GMT (envelope-from phill@sysctl.net) From: "Phillip Salzman" To: "'Peter Jeremy'" Date: Thu, 20 Jan 2005 11:58:19 -0600 Message-ID: <008001c4ff19$a38deff0$6745a8c0@MESE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <20050120094551.GK79646@cirb503493.alcatel.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.29.0.5; VDF 6.29.0.52 cc: stable@freebsd.org Subject: RE: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 17:57:54 -0000 Thanks Peter (along with everyone else who's responded.) I've received a couple perl scripts from a few different people. I can't use any of them until this evening due to the current load of the machines though. Last night I ended up doing a strings on the directory, and taking its output into a for loop removing the files. -- Phillip Salzman > -----Original Message----- > From: Peter Jeremy [mailto:PeterJeremy@optushome.com.au] > Sent: January 20, 2005 3:46 AM > To: Phillip Salzman > Cc: stable@freebsd.org > Subject: Re: Very large directory > > > On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote: > >They've been running for a little while now - and recently we've > >noticed a lot of disk space disappearing. Shortly after > that, a simple > >du into our /var/spool returned a not so nice error: > > > > du: fts_read: Cannot allocate memory > > > >No matter what command I run on that directory, I just don't seem to > >have enough available resources to show the files let alone delete > >them (echo *, ls, find, rm -rf, etc.) > > I suspect you will need to write something that uses > dirent(3) to scan the offending directory and delete (or > whatever) the files one by one. > > Skeleton code (in perl) would look like: > > chdir $some_dir or die "Can't cd $some_dir: $!"; > opendir(DIR, ".") or die "Can't opendir: $!"; > while (my $file = readdir(DIR)) { > next if ($file eq '.' || $file eq '..'); > next if (&this_file_is_still_needed($file)); > unlink $file or warn "Unable to delete $file: $!"; > } > closedir DIR; > > If you've reached the point where you can't actually read the > entire directory into user memory, expect the cleanup to take > quite a while. > > Once you've finished the cleanup, you should confirm that the > directory has shrunk to a sensible size. If not, you need to > re-create the directory and move the remaining files into the > new directory. > > -- > Peter Jeremy > From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:01:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F08516A4CE; Thu, 20 Jan 2005 18:01:28 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1FE643D49; Thu, 20 Jan 2005 18:01:27 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 20 Jan 2005 10:01:27 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3BCB35D07; Thu, 20 Jan 2005 10:01:27 -0800 (PST) To: Scot Hetzel In-reply-to: Your message of "Thu, 20 Jan 2005 10:12:04 CST." <790a9fff050120081229a3ec6a@mail.gmail.com> Date: Thu, 20 Jan 2005 10:01:27 -0800 From: "Kevin Oberman" Message-Id: <20050120180127.3BCB35D07@ptavv.es.net> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 18:01:28 -0000 > Date: Thu, 20 Jan 2005 10:12:04 -0600 > From: Scot Hetzel > Sender: owner-freebsd-stable@freebsd.org > > On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne > wrote: > > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > > and the box is up BUT I am concerned that the NEXT time that I > > do "make installkernel" I'll stomp on kernel.old losing this fallback > > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > > but is there something else I should save? Or is there another > > suggested procedure? > > > When I have a bad kernel I do the following after booting the good kernel. > > cd /boot > rm -rf kernel > cp -rp kernel.old kernel > cp -rp kernel.old kernel.good > > This way I can reboot the box without going into the loader to load kernel.old. While this works (I've done it), "make reinstallkernel" and "make -DMODULES_WITH_WORLD" reinstallkernel" can also be good friends. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:03:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B04EB16A4CE for ; Thu, 20 Jan 2005 18:03:29 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9931943D4C for ; Thu, 20 Jan 2005 18:03:28 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 18:03:27 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp022) with SMTP; 20 Jan 2005 19:03:27 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Thu, 20 Jan 2005 19:03:19 +0100 User-Agent: KMail/1.7.2 References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1144706.gKzGBK3ITW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501201903.24020.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: akiyama@jp.freebsd.org cc: Michal Mertl cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 18:03:29 -0000 --nextPart1144706.gKzGBK3ITW Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > > works for both chips on CURRENT for serial console. It detects if the > > chip is rev 3.00 and aplies the patch only for it. > > > > The author of the patch mentions it isn't binary safe - sometimes the > > chip stops working. I planned to test it with binary transfers (ppp) > > today, check if it's working and submit it (with some cleanup) for > > inclusion in FreeBSD. > > > > Michal Mertl > > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. Thanks a lot, unfortunately my notebook died (the display mechanic) so I=20 cannot test it at the moment (my workstation box is too far away from my=20 servers with serial stuff). But I think this should be commited, otherwiese more people like me go=20 shopping, testing the adaptor, seeing that it gets recognized as Prolific=20 2303, purchasing some of them and then at home find out that there is also = a=20 unsupported version of the 2303 :( I'm sure someone (bernd?) will commit it for you. Thanks a lot for your work, I'll test it asap and let you know if I find=20 anything unusual. Best regards, =2DHarry > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. > > Michal --nextPart1144706.gKzGBK3ITW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7/JrBylq0S4AzzwRAkbZAJ9Om883mEQNCCbkKw4QwMoF/A/7+wCdH/K+ sYwjb9wGiN1x6F5bLahnPSI= =9Pcs -----END PGP SIGNATURE----- --nextPart1144706.gKzGBK3ITW-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:33:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 175D016A4CE for ; Thu, 20 Jan 2005 18:33:07 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BD2FC43D3F for ; Thu, 20 Jan 2005 18:33:05 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 18:33:01 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp026) with SMTP; 20 Jan 2005 19:33:01 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 19:32:54 +0100 User-Agent: KMail/1.7.2 X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1335144.nSmCZzz7qs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501201932.58869.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: fwe and em ftp transfer rates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 18:33:07 -0000 --nextPart1335144.nSmCZzz7qs Content-Type: multipart/mixed; boundary="Boundary-01=_Xl/7BohF1nZkE+l" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_Xl/7BohF1nZkE+l Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear all, I'm sorry but I have to report something's going wrong with simple ftp file= =20 transfers. I have two Fujitsu Siemens Primergy B125 servers (PIII@866MHz,=20 512MB) with both 'em' cards in it which are connected directly together, so= =20 no switch can drop packets. When I transfer a large testfile (400MB) via ft= p=20 I get unbelievable 18MB/s. Both servers are 0% idle (~60% intr 40% sys). What the heck is this machine doing? There's nothing else on the machines=20 running, sure! I can dump to the disks with ~55MB/s so the bottleneck is not the hardware. Things go worse if I use fwe (TI chipest) or fwip instead of em. Then trans= fer=20 rates decrease to 15MB/s for the fwe and 13MB/s with the fwip. One good thin is that using NFS instead of ftp gives comparable transfer ra= tes=20 (~5% less) without tuning and regardless of udp or tcp. world an kernel are built with -O2 -march=3Dpentium3, kernel config and dme= sg=20 are attached (CUV-LV ist the kernel config). What can I do to get reasonable GbE performance (with this hw I expect at=20 least 40MB/s, it's what a friend achieves with an other graphical OS on=20 similar hw). Thanks, =2DHarry --Boundary-01=_Xl/7BohF1nZkE+l Content-Type: text/plain; charset="us-ascii"; name="dmesg.test2" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.test2" Copyright (c) 1992-2005 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 5.3-STABLE #0: Thu Jan 20 02:12:36 CET 2005 root@test1.flintsbach.schmalzbauer.de:/builder/obj/builder/src/sys/CUV-LV Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (870.58-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 536854528 (511 MB) avail memory = 515629056 (491 MB) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xfe000000-0xfe3fffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xb400-0xb41f irq 12 at device 4.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 12 at device 4.3 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered viapropm0: SMBus I/O base at 0xe800 viapropm0: port 0xe800-0xe80f at device 4.4 on pci0 viapropm0: SMBus revision code 0x0 smbus0: on viapropm0 smb0: on smbus0 fxp0: port 0xa800-0xa83f mem 0xfa800000-0xfa8fffff,0xfb000000-0xfb000fff irq 5 at device 7.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:18:06:ad:59 em0: port 0xa400-0xa43f mem 0xf9800000-0xf981ffff,0xfa000000-0xfa01ffff irq 10 at device 9.0 on pci0 em0: Ethernet address: 00:0e:0c:34:2b:f8 em0: Speed:N/A Duplex:N/A fwohci0: mem 0xf8800000-0xf8803fff,0xf9000000-0xf90007ff irq 12 at device 10.0 on pci0 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:01:08:00:20:01:eb:10 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:01:08:01:eb:10 fwe0: Ethernet address: 02:01:08:01:eb:10 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci1: port 0x8800-0x88ff,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 irq 11 at device 12.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] npx0: [FAST] npx0: on motherboard npx0: INT 16 interface orm0: at iomem 0xcc000-0xccfff,0xc0000-0xca7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 870581132 Hz quality 800 Timecounters tick every 1.953 msec acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% ad0: 76351MB [155127/16/63] at ata0-master PIO4 ad2: 245MB [980/16/32] at ata1-master PIO4 ad4: 57259MB [116336/16/63] at ata2-master PIO4 Mounting root from ufs:/dev/ad2a em0: Link is up 1000 Mbps Full Duplex --Boundary-01=_Xl/7BohF1nZkE+l Content-Type: text/plain; charset="us-ascii"; name="CUV-LV" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="CUV-LV" machine i386 cpu I686_CPU options PQ_CACHESIZE=256 # color for 512k cache ident CUV-LV options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options NULLFS #NULL filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options QUOTA #enable disk quotas #options SUIDDIR options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options CD9660 # ISO 9660 Filesystem #options PROCFS # Process filesystem (requires PSEUDOFS) #options PSEUDOFS # Pseudo-filesystem framework options GEOM_BDE options GEOM_GPT # GPT partitioning options GEOM_BSD # BSD disklabels options GEOM_GATE # Userland services. options GEOM_MIRROR # Disk mirroring. options GEOM_STRIPE # Disk striping. options GEOM_CONCAT # Disk concatenation. options GEOM_LABEL # Providers labelization. options GEOM_FOX # Redundant path mitigation options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options PREEMPTION options HZ=256 #options DEVICE_POLLING options ZERO_COPY_SOCKETS device agp # support several AGP chipsets device npx device apic # I/O APIC device isa device pci device acpi # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP=german.iso device psm # PS/2 mouse device vga # VGA video card driver options VESA device splash # Splash screen and screen saver support device sc options MAXCONS=8 options SC_DISABLE_REBOOT options SC_PIXEL_MODE options SC_HISTORY_SIZE=1000 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso15 # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # PCI Ethernet NICs. device em # Intel PRO/1000 adapter Gigabit Ethernet Card # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uplcom device ucom # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) #device fwip # IP over FireWire (rfc2734 and rfc3146) device iicbus device iicbb device smbus # Bus support, required for smb below. device viapm device smb device iicsmb options SW_WATCHDOG --Boundary-01=_Xl/7BohF1nZkE+l-- --nextPart1335144.nSmCZzz7qs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7/laBylq0S4AzzwRApOkAJ420YenNU/8naIj0xZFO6sDIAWD7gCfUE3P I1n6CREK0Elcpicl+PjG/Zo= =4mYW -----END PGP SIGNATURE----- --nextPart1335144.nSmCZzz7qs-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:37:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14F5116A4CE for ; Thu, 20 Jan 2005 18:37:02 +0000 (GMT) Received: from www.wcborstel.nl (wcborstel.demon.nl [82.161.134.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AE5843D2D for ; Thu, 20 Jan 2005 18:37:01 +0000 (GMT) (envelope-from jorn@wcborstel.nl) Received: from localhost (localhost [127.0.0.1]) by www.wcborstel.nl (Postfix) with ESMTP id E2B634391; Thu, 20 Jan 2005 19:37:51 +0100 (CET) Received: from www.wcborstel.nl ([127.0.0.1]) by localhost (www.wcborstel.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79758-07; Thu, 20 Jan 2005 19:37:47 +0100 (CET) Received: from www.wcborstel.nl (localhost [127.0.0.1]) by www.wcborstel.nl (Postfix) with ESMTP id A9422421A; Thu, 20 Jan 2005 19:37:47 +0100 (CET) From: "Jorn Argelo" To: =?ISO-8859-1?Q?Imobach_Gonz=E1lez_S?=osa , freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 19:37:47 +0100 Message-Id: <20050120183517.M81458@wcborstel.nl> In-Reply-To: <200501201630.04506.imobachgs@banot.net> References: <200501201630.04506.imobachgs@banot.net> X-Mailer: Open WebMail 2.41 20040926 X-OriginatingIP: 82.161.134.53 (jorn) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: by amavisd-new at mail.wcborstel.nl Subject: Re: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 18:37:02 -0000 On Thu, 20 Jan 2005 16:30:03 +0000, Imobach González Sosa wrote > Hi all, > > I'm havin' a strange problem with my Realtek Network Adapter. On > boot, the detection looks just fine: > > $ dmesg| grep rl > rl0: port 0xd000-0xd0ff mem 0xee000000- > 0xee0000ff irq 10 at device 10.0 on pci0 miibus0: on rl0 > rlphy0: on miibus0 rlphy0: > 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet > address: 00:40:f4:32:e5:12 > > However, the performance is very poor. Some examples: > > * using 'fetch' command, I get a lot of "timeouts", so some "ports" > fail to install (I have to retry). * using Konqueror, for instance, > I also get some "timeouts" and a very low speed connecting to > different websites. > > I've done the some test on the same machine (and on my laptop) using > GNU/Linux, and works pretty fine. So I discarded a network hardware > issue as the origin of the problem. If it's on an old machine then you have your problem there. The Realtek chips and its drivers put everything on the CPU, because the chip is not capable of doing too much. Which is why it's so cheap. Modern CPUs don't have too much problems with it, but older ones do. Of course, the Linux driver might be a bit better written then the FreeBSD one. It's advicable to get yourself a better network card if it's indeed an old machine. Cheers, Jorn From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:48:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54ECA16A4CE for ; Thu, 20 Jan 2005 18:48:47 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4538D43D2D for ; Thu, 20 Jan 2005 18:48:46 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 18:48:44 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp012) with SMTP; 20 Jan 2005 19:48:44 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 19:48:38 +0100 User-Agent: KMail/1.7.2 X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2359445.XJB2V7ZaMH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501201948.42707.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: Higher ATA-Mode -> lower speed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 18:48:47 -0000 --nextPart2359445.XJB2V7ZaMH Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear ata interested guys, I observed a strange behaviour which seems to explain my often noticed "16M= B/s=20 hard-limit" I have a UDMA133 drive (MAXTOR 6L060J3) which saturates at 16MB/s when I du= mp=20 anything to it, regardless of the block size. This transfer rate is reached= =20 with bs=3D4k and doesn't increase any more even not with bs=3D64k. Now, when I set the mode to UDMA100 I get well over 40MB/s!!!! Can anybody confirm that for different hw? Especially people like fandino w= ho=20 already discussed poor ata performance on -current (~16 Oct. 04). Why does UDMA133 mode limit the transfer speed so badly? And why do I get=20 significantly slower transfer rates (32MB/s insted of 42MB/s) when I set th= e=20 mode to UDMA66 (compared to UDMA100 but twice the speed of UDMA133)? There'= s=20 only one device on the channel, so UDMA66 should be fine for 42MB/s. The controller is a HPT372. Best regards, =2DHarry --nextPart2359445.XJB2V7ZaMH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7/0KBylq0S4AzzwRAlXlAKCLCXNUVkjXQmNWDV4Hd/kOg4dNGQCfW9LK uuUs0LRqrsuhqlS4qEseVU8= =T5QT -----END PGP SIGNATURE----- --nextPart2359445.XJB2V7ZaMH-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 18:54:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6FD916A4CE for ; Thu, 20 Jan 2005 18:54:06 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4796E43D3F for ; Thu, 20 Jan 2005 18:54:06 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id g11so15757rne for ; Thu, 20 Jan 2005 10:54:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ugCJbj/aZuZLsNgAQHTW3NfOQV3E2RJCHsRrwLNSOAaNCca/ycUvj0QNrla/oQ2CgTyJWi420V28HCFoQcXuVXxYicmscKXOCgQdlVERlYiR8lH4Jb3C2Hs+J4kQTXA9fiOaHfDdTceXoz98DivrqMvnkUumzEr3SspjcOgUgDU= Received: by 10.38.86.16 with SMTP id j16mr99160rnb; Thu, 20 Jan 2005 10:54:05 -0800 (PST) Received: by 10.39.1.45 with HTTP; Thu, 20 Jan 2005 10:54:05 -0800 (PST) Message-ID: <3aaaa3a050120105459f7d015@mail.gmail.com> Date: Thu, 20 Jan 2005 18:54:05 +0000 From: Chris To: John Polstra In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3aaaa3a0501181530975fecf@mail.gmail.com> cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 18:54:06 -0000 Yep its fixed now I know, I was saying its the only time I have ever had a problem, the problem no longer exists now tho. Chris On Thu, 20 Jan 2005 08:56:33 -0800 (PST), John Polstra wrote: > On 18-Jan-2005 Chris wrote: > > I have been compiling ports using -O2 since I started using FreeBSD > > back in 2003 and only port that has had issues with this is lang/ezm3 > > in FreeBSD 5.2.1 it needed -O. > > I fixed that at the beginning of November. > > John > From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 19:00:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59F5C16A54D for ; Thu, 20 Jan 2005 19:00:48 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2C3D943D1F for ; Thu, 20 Jan 2005 19:00:47 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 19:00:46 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp007) with SMTP; 20 Jan 2005 20:00:46 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 20:00:39 +0100 User-Agent: KMail/1.7.2 References: <200501201948.42707.emanuel.strobl@gmx.net> In-Reply-To: <200501201948.42707.emanuel.strobl@gmx.net> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1646911.PjIfmrZUXT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501202000.43688.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: Re: Higher ATA-Mode -> lower speed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 19:00:48 -0000 --nextPart1646911.PjIfmrZUXT Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 20. Januar 2005 19:48 schrieb Emanuel Strobl: > Dear ata interested guys, > > I observed a strange behaviour which seems to explain my often noticed > "16MB/s hard-limit" > > I have a UDMA133 drive (MAXTOR 6L060J3) which saturates at 16MB/s when I > dump anything to it, regardless of the block size. This transfer rate is > reached with bs=3D4k and doesn't increase any more even not with bs=3D64k. > > Now, when I set the mode to UDMA100 I get well over 40MB/s!!!! > > Can anybody confirm that for different hw? Especially people like fandino > who already discussed poor ata performance on -current (~16 Oct. 04). I can confirm that for my workstation here. i815 chipset and seagate=20 ST380011A. When set to UDMA100 (the maximum) the following dump gives 16MB/s 'dd=20 if=3D/dev/zero of=3D/usr/testfile bs=3D16k count=3D2000). When I limit the mode to UDMA66 I get 53MB/s !!!!!!!!!!!!!!!! It seems that's independent of UDMA133 instead it's when mode is set to the= =20 maximum the chipset can handle! This really hurts! But it's _the_ eplanation for all the "poor ata=20 performance" reports. =2DHarry > > Why does UDMA133 mode limit the transfer speed so badly? And why do I get > significantly slower transfer rates (32MB/s insted of 42MB/s) when I set > the mode to UDMA66 (compared to UDMA100 but twice the speed of UDMA133)? > There's only one device on the channel, so UDMA66 should be fine for > 42MB/s. The controller is a HPT372. > > Best regards, > > -Harry --nextPart1646911.PjIfmrZUXT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7//bBylq0S4AzzwRArKYAJ4mtS4/I7cpUnqvIrLzgO/MpWIe6gCff7WP pHaAdinpIqJ34qpEI25zd/U= =rO5Y -----END PGP SIGNATURE----- --nextPart1646911.PjIfmrZUXT-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 19:10:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E09F16A4CE for ; Thu, 20 Jan 2005 19:10:05 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9477F43D46 for ; Thu, 20 Jan 2005 19:10:04 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 19:10:03 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp012) with SMTP; 20 Jan 2005 20:10:03 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 20 Jan 2005 20:09:57 +0100 User-Agent: KMail/1.7.2 References: <200501201948.42707.emanuel.strobl@gmx.net> <200501202000.43688.emanuel.strobl@gmx.net> In-Reply-To: <200501202000.43688.emanuel.strobl@gmx.net> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1618033.AHgYaLUpV2"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501202010.01675.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: Re: Higher ATA-Mode -> lower speed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 19:10:05 -0000 --nextPart1618033.AHgYaLUpV2 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 20. Januar 2005 20:00 schrieb Emanuel Strobl: > Am Donnerstag, 20. Januar 2005 19:48 schrieb Emanuel Strobl: > > Dear ata interested guys, > > > > I observed a strange behaviour which seems to explain my often noticed > > "16MB/s hard-limit" > > > > I have a UDMA133 drive (MAXTOR 6L060J3) which saturates at 16MB/s when I > > dump anything to it, regardless of the block size. This transfer rate is > > reached with bs=3D4k and doesn't increase any more even not with bs=3D6= 4k. > > > > Now, when I set the mode to UDMA100 I get well over 40MB/s!!!! > > > > Can anybody confirm that for different hw? Especially people like fandi= no > > who already discussed poor ata performance on -current (~16 Oct. 04). > > I can confirm that for my workstation here. i815 chipset and seagate > ST380011A. > When set to UDMA100 (the maximum) the following dump gives 16MB/s 'dd > if=3D/dev/zero of=3D/usr/testfile bs=3D16k count=3D2000). > When I limit the mode to UDMA66 I get 53MB/s !!!!!!!!!!!!!!!! Sorry, that's not 100% correct. After booting the machine I get 16MB/s. That's the hard limit. The disk is shown to operate with UDMA100 (that's the highest mode of the=20 chipset). Now when I issue a 'atacontrol mode 0 udma100 udma100' (set the same mode a= s=20 it's said to be) I get 57MB/s!!!!! =46rom this point it doesn't matter what mode I set, the 16MB/s hard-limit= =20 vanished :)) But the original described problem of the 16MB/s hard-limit with udma133 is= =20 reproducable, means if I return mode to udma133 I see the 16MB/s limit agai= n! =2DHarry > > It seems that's independent of UDMA133 instead it's when mode is set to t= he > maximum the chipset can handle! > > This really hurts! But it's _the_ eplanation for all the "poor ata > performance" reports. > > -Harry > > > Why does UDMA133 mode limit the transfer speed so badly? And why do I g= et > > significantly slower transfer rates (32MB/s insted of 42MB/s) when I set > > the mode to UDMA66 (compared to UDMA100 but twice the speed of UDMA133)? > > There's only one device on the channel, so UDMA66 should be fine for > > 42MB/s. The controller is a HPT372. > > > > Best regards, > > > > -Harry --nextPart1618033.AHgYaLUpV2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB8AIJBylq0S4AzzwRAnOfAJwJ7zZcrzXVWXTGURfARQUVwBleowCfYS+U +eQ2vQo2MJPjrJPvXSdyYKU= =piaG -----END PGP SIGNATURE----- --nextPart1618033.AHgYaLUpV2-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 19:17:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED8E316A4CE for ; Thu, 20 Jan 2005 19:17:04 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55A4C43D39 for ; Thu, 20 Jan 2005 19:17:04 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id g11so20760rne for ; Thu, 20 Jan 2005 11:17:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ur+9aGGyxaUMS+J6Lo0O4anRBOa+LRa9mIPJpxABh1D+knxp8MCHr/oZLN4OR0xKODXlPuK/8E8Yaxt1nUhUU+23Yo214nZAQ0pNfI//pcjBEMK8BcW+OXSmN7MxAxxI26RnjINHcZB4K84Kc0Lbxjuza/xDaaSIsh5g72H4A3g= Received: by 10.38.86.16 with SMTP id j16mr111234rnb; Thu, 20 Jan 2005 11:17:03 -0800 (PST) Received: by 10.39.1.45 with HTTP; Thu, 20 Jan 2005 11:17:03 -0800 (PST) Message-ID: <3aaaa3a050120111777ada357@mail.gmail.com> Date: Thu, 20 Jan 2005 19:17:03 +0000 From: Chris To: John Polstra In-Reply-To: <3aaaa3a050120105459f7d015@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3aaaa3a0501181530975fecf@mail.gmail.com> <3aaaa3a050120105459f7d015@mail.gmail.com> cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:17:05 -0000 what does -fno-strict-alias do? I cannot find it in man gcc Chris On Thu, 20 Jan 2005 18:54:05 +0000, Chris wrote: > Yep its fixed now I know, I was saying its the only time I have ever > had a problem, the problem no longer exists now tho. > > Chris > > > On Thu, 20 Jan 2005 08:56:33 -0800 (PST), John Polstra wrote: > > On 18-Jan-2005 Chris wrote: > > > I have been compiling ports using -O2 since I started using FreeBSD > > > back in 2003 and only port that has had issues with this is lang/ezm3 > > > in FreeBSD 5.2.1 it needed -O. > > > > I fixed that at the beginning of November. > > > > John > > > From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 19:27:43 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CF216A4CE for ; Thu, 20 Jan 2005 19:27:43 +0000 (GMT) Received: from amber.aeternal.net (amber.in.markiza.sk [62.168.76.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2234343D46 for ; Thu, 20 Jan 2005 19:27:42 +0000 (GMT) (envelope-from corwin@pleiades.aeternal.net) Received: from localhost (localhost.aeternal.net [127.0.0.1]) by amber.aeternal.net (Postfix) with ESMTP id 76E47B875 for ; Thu, 20 Jan 2005 20:30:49 +0100 (CET) Received: from amber.aeternal.net ([127.0.0.1]) by localhost (amber.aeternal.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00438-05 for ; Thu, 20 Jan 2005 20:30:48 +0100 (CET) Received: from pleiades.aeternal.net (pleiades.markiza.sk [192.168.0.7]) by amber.aeternal.net (Postfix) with ESMTP id 0736DB873 for ; Thu, 20 Jan 2005 20:30:48 +0100 (CET) Received: from pleiades.aeternal.net (localhost.aeternal.net [127.0.0.1]) by pleiades.aeternal.net (Postfix) with ESMTP id 942DA7E824 for ; Thu, 20 Jan 2005 20:27:40 +0100 (CET) Received: (from corwin@localhost) by pleiades.aeternal.net (8.13.1/8.13.1/Submit) id j0KJRe6W006932 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 20:27:40 +0100 (CET) (envelope-from corwin) Date: Thu, 20 Jan 2005 20:27:39 +0100 From: martin hudec To: freebsd-stable@freebsd.org Message-ID: <20050120192739.GD5431@pleiades.aeternal.net> References: <200501201948.42707.emanuel.strobl@gmx.net> <200501202000.43688.emanuel.strobl@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dFWYt1i2NyOo1oI9" Content-Disposition: inline In-Reply-To: <200501202000.43688.emanuel.strobl@gmx.net> X-Copyright: (C) 2005 Martin Hudec X-Operating-System: FreeBSD pleiades.aeternal.net 6.0-CURRENT i386 X-PGP-Key: http://www.aeternal.net/corwin_aeternal.asc User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at aeternal.net Subject: Re: Higher ATA-Mode -> lower speed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: martin hudec List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:27:43 -0000 --dFWYt1i2NyOo1oI9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, On Thu, Jan 20, 2005 at 08:00:39PM +0100 or thereabouts, Emanuel Strobl wro= te: > > > > I observed a strange behaviour which seems to explain my often noticed > > "16MB/s hard-limit" > > > > I have a UDMA133 drive (MAXTOR 6L060J3) which saturates at 16MB/s when I > > dump anything to it, regardless of the block size. This transfer rate is > > reached with bs=3D4k and doesn't increase any more even not with bs=3D6= 4k. > > > > Can anybody confirm that for different hw? Especially people like fandi= no > > who already discussed poor ata performance on -current (~16 Oct. 04). my tests shows speeds ranging from 36.9MB/s up to 59.3MB/s.=20 System is 6.0-CURRENT (yup I know this is -stable list), built on Jan 10, 2005 with VIA 8235 UDMA133 controller. Disk configuration is as following: ad0: 38172MB [77557/16/63] at ata0-master UDMA133 ad1: 39205MB [79656/16/63] at ata0-slave UDMA133 /usr is located on /dev/ad0s1e, and /various is located on /dev/ad1s1d. Testing of ad0: pleiades# dd if=3D/dev/zero of=3D/usr/testfile bs=3D4k count=3D2000 8192000 bytes transferred in 0.161283 secs (50792701 bytes/sec) pleiades# dd if=3D/dev/zero of=3D/usr/testfile bs=3D16k count=3D2000 32768000 bytes transferred in 0.792992 secs (41321975 bytes/sec) pleiades# dd if=3D/dev/zero of=3D/usr/testfile bs=3D64k count=3D2000 131072000 bytes transferred in 3.386982 secs (38698759 bytes/sec) Testing for ad1: pleiades# dd if=3D/dev/zero of=3D/various/testfile bs=3D4k count=3D2000 8192000 bytes transferred in 0.131618 secs (62240716 bytes/sec) pleiades# dd if=3D/dev/zero of=3D/various/testfile bs=3D16k count=3D2000 32768000 bytes transferred in 0.674646 secs (48570665 bytes/sec) pleiades# dd if=3D/dev/zero of=3D/various/testfile bs=3D64k count=3D2000 131072000 bytes transferred in 3.184140 secs (41164020 bytes/sec) =20 I also run these tests on another machine shows speeds ranging from 49MB/s up to 63MB/s. System is 5.3-STABLE built on Dec 7, 2004 with SiS 735 UDMA100 controller. Disk configuration is as following: ad0: 76319MB [155061/16/63] at ata0-master UDMA100 /usr is located on /dev/ad0s1e. Testing of ad0: amber# dd if=3D/dev/zero of=3D/usr/testfile bs=3D4k count=3D2000 8192000 bytes transferred in 0.154835 secs (52907939 bytes/sec) amber# dd if=3D/dev/zero of=3D/usr/testfile bs=3D16k count=3D2000 32768000 bytes transferred in 0.495422 secs (66141576 bytes/sec) amber# dd if=3D/dev/zero of=3D/usr/testfile bs=3D64k count=3D2000 131072000 bytes transferred in 2.546718 secs (51467023 bytes/sec) I hope that this information will help you.=20 Cheers, Martin --=20 martin hudec * 421 907 303 393 * corwin@aeternal.net * http://www.aeternal.net "Nothing travels faster than the speed of light with the possible=20 exception of bad news, which obeys its own special laws." Douglas Adams, "The Hitchhiker's Guide to the Galaxy" --dFWYt1i2NyOo1oI9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8AYrZYEZIv+rgggRAlyQAJ93v/Np7hiT91V7alHQ+nfPJTy0pgCgly9R sdTVkNzAvriJjVNAMGYrrW8= =xVnu -----END PGP SIGNATURE----- --dFWYt1i2NyOo1oI9-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 20:05:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E2D216A4CE for ; Thu, 20 Jan 2005 20:05:11 +0000 (GMT) Received: from subnet.sub.net (subnet.sub.net [193.197.184.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA6A43D45 for ; Thu, 20 Jan 2005 20:05:09 +0000 (GMT) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from subnet.sub.net (uucp@localhost [127.0.0.1]) j0KK56lb032607; Thu, 20 Jan 2005 21:05:07 +0100 (CET) (envelope-from wolfgang@lyxys.ka.sub.org) X-MDaemon-Deliver-To: stable@freebsd.org Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.13.2/8.13.2/Submit) with bsmtp id j0KK55ui032606; Thu, 20 Jan 2005 21:05:05 +0100 (CET) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from localhost (992 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Thu, 20 Jan 2005 21:03:30 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) In-Reply-To: <008001c4ff19$a38deff0$6745a8c0@MESE> To: Phillip Salzman Date: Thu, 20 Jan 2005 21:03:30 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: 'Peter Jeremy' cc: stable@freebsd.org Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 20:05:11 -0000 Hello Phillip, > I've received a couple perl scripts from a few different people. I can't > use any of them until this evening due to the current load of the machines > though. Last night I ended up doing a strings on the directory, and taking > its output into a for loop removing the files. if you have a bit of time to spare, take a look at the xargs(1) manpage. Using xargs instead of a for loop would have saved you a lot of time and system load (and a little bit of typing :-) Wolfgang From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 20:06:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12CAE16A4CE; Thu, 20 Jan 2005 20:06:25 +0000 (GMT) Received: from fe09.axelero.hu (fe09.axelero.hu [195.228.240.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 478E943D48; Thu, 20 Jan 2005 20:06:24 +0000 (GMT) (envelope-from kutizs@axelero.hu) Received: from fe09 (localhost-02 [127.0.2.1]) by fe09.axelero.hu (8.12.11/8.12.11) with SMTP id j0KK6Nvx085435; Thu, 20 Jan 2005 21:06:23 +0100 (CET) Received: from fe09.axelero.hu [127.0.2.1] via SMTP gateway by fe09 [195.228.240.97]; id A04DADCDADC at Thu, 20 Jan 2005 21:06:22 +0100 Received: from tinca.kuti.hu (ktv32-154-73.catv-pool.axelero.hu [62.201.73.154]) by fe09.axelero.hu (8.12.11/8.12.11) with SMTP id j0KK6H1c085292; Thu, 20 Jan 2005 21:06:18 +0100 (CET) Date: Thu, 20 Jan 2005 21:07:04 +0100 From: Zsolt =?ISO-8859-2?Q?K=FAti?= To: freebsd-stable@freebsd.org Message-Id: <20050120210704.19642e07.kutizs@axelero.hu> In-Reply-To: <20050116181433.29ae0a21.kutizs@axelero.hu> References: <20050114102346.GA53545@cirb503493.alcatel.com.au> <41E960BA.3010502@sailorfej.net> <20050115203049.GE53545@cirb503493.alcatel.com.au> <41E989E0.3000903@sailorfej.net> <20050116181433.29ae0a21.kutizs@axelero.hu> X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable cc: freebsd-openoffice@freebsd.org cc: jeff@sailorfej.net cc: PeterJeremy@optushome.com.au Subject: Re: Unkillable OpenOffice.org process in 5.3p2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 20:06:25 -0000 On Sun, 16 Jan 2005 18:14:33 +0100 Zsolt K=FAti wrote: > On Sat, 15 Jan 2005 13:23:44 -0800 > Jeffrey Williams wrote: [...] >=20 > > wondering if it is a problem with the interaction between the OO and > > java, or OO the pdf libraries, or a some shared library that > > facilitates the interaction between these components. I am afraid I > I extensively use Java applications (jEdit, DBVisualizer, jCVS, Java > Web Start and apps launched by JWS). I am going to try to experiment > with all these in mind on Monday (at work). Since I have been avoiding java apps when workin with OO, I don't experience any problems! Bye Zsolt From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 20:43:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C92816A4CE for ; Thu, 20 Jan 2005 20:43:50 +0000 (GMT) Received: from lora.pns.networktel.net (lora.pns.networktel.net [216.83.236.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54BE443D54 for ; Thu, 20 Jan 2005 20:43:50 +0000 (GMT) (envelope-from phill@sysctl.net) Received: from MESE (wifi-ipnet.sysctl.net [216.83.242.102]) j0KKjfg3000306; Thu, 20 Jan 2005 20:45:42 GMT (envelope-from phill@sysctl.net) From: "Phillip Salzman" To: "'Wolfgang Zenker'" Date: Thu, 20 Jan 2005 14:43:39 -0600 Message-ID: <00d001c4ff30$bda2e960$6745a8c0@MESE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.29.0.5; VDF 6.29.0.52 cc: 'Peter Jeremy' cc: stable@freebsd.org Subject: RE: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 20:43:51 -0000 Yeah - I thought of that after the for loop had already been in the = process of starting for an hour. I figured I wasn't going to worry about it, = and just head to bed at that point. If I wasn't drunk at the time (I'll = pretend thats my excuse) I might have done a strings .| xargs instead of the = shell script. Oh well. I can't really wo > -----Original Message----- > From: Wolfgang Zenker [mailto:wolfgang@lyxys.ka.sub.org]=20 > Sent: January 20, 2005 2:04 PM > To: Phillip Salzman > Cc: 'Peter Jeremy'; stable@freebsd.org > Subject: Re: Very large directory >=20 >=20 > Hello Phillip, >=20 > > I've received a couple perl scripts from a few different people. I=20 > > can't use any of them until this evening due to the current load of=20 > > the machines though. Last night I ended up doing a strings on the=20 > > directory, and taking its output into a for loop removing the files. >=20 > if you have a bit of time to spare, take a look at the=20 > xargs(1) manpage. Using xargs instead of a for loop would=20 > have saved you a lot of time and system load (and a little=20 > bit of typing :-) >=20 > Wolfgang >=20 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:09:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E45B16A4CE for ; Thu, 20 Jan 2005 21:09:25 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E3143D1F for ; Thu, 20 Jan 2005 21:09:24 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id j0KL9OTA097382 for ; Thu, 20 Jan 2005 16:09:24 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0KL9Nml097381 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 16:09:23 -0500 (EST) (envelope-from wayne) Date: Thu, 20 Jan 2005 16:09:23 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org Message-ID: <20050120210923.GJ1168@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> <20050119213605.B26294@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119213605.B26294@Denninger.Net> User-Agent: Mutt/1.4.2.1i Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:09:25 -0000 On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: > > What 'other vendor' have you found that makes RELIABLE SATA disks in the > high capacity (e.g. 200-300gb) arena? WD now makes a SATA RAID line. HIGHLY recommended by 3ware. /\/\ \/\/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:33:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4031C16A4CE for ; Thu, 20 Jan 2005 21:33:09 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id D706743D53 for ; Thu, 20 Jan 2005 21:33:08 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-113-125.roa.east.verizon.net [151.199.113.125]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id j0KLX6Tc082355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2005 16:33:07 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id j0KLX1Jo000715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2005 16:33:01 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id j0KLX0GF000714; Thu, 20 Jan 2005 16:33:00 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: Chris In-Reply-To: <3aaaa3a050120111777ada357@mail.gmail.com> References: <3aaaa3a0501181530975fecf@mail.gmail.com> <3aaaa3a050120105459f7d015@mail.gmail.com> <3aaaa3a050120111777ada357@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 20 Jan 2005 16:33:00 -0500 Message-Id: <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: freebsd-stable@freebsd.org cc: John Polstra Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:33:09 -0000 On Thu, 2005-01-20 at 19:17 +0000, Chris wrote: > what does -fno-strict-alias do? I cannot find it in man gcc It is a truncation of "-fno-strict-aliasing". The flag does not appear to be described in the gcc man page, but is documented in the gcc info page (search for "-fstrict-aliasing"). To quote the info page, -fstrict-aliasing "allows the compiler to assume the strictest aliasing rules applicable to the language being compiled. ..." Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:36:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30A3116A4CE for ; Thu, 20 Jan 2005 21:36:33 +0000 (GMT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id F20A343D1D for ; Thu, 20 Jan 2005 21:36:32 +0000 (GMT) (envelope-from darrylo@soco.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 8200B229C6 for ; Thu, 20 Jan 2005 14:36:32 -0700 (MST) Received: from wlvdvs01.lvld.agilent.com (wlvdvs01.lvld.agilent.com [148.5.6.4]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 46DF6FA0 for ; Thu, 20 Jan 2005 14:36:32 -0700 (MST) Received: from mina.soco.agilent.com ([141.121.54.157]) by wlvdvs01.lvld.agilent.com with InterScan Messaging Security Suite; Thu, 20 Jan 2005 14:36:31 -0700 Received: from mina.soco.agilent.com (localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id NAA13625 for ; Thu, 20 Jan 2005 13:36:31 -0800 (PST) Message-Id: <200501202136.NAA13625@mina.soco.agilent.com> To: freebsd-stable@freebsd.org In-Reply-To: Your message of "Thu, 20 Jan 2005 12:30:20 +0100." <200501201130.j0KBUKMZ066099@lurza.secnetix.de> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Thu, 20 Jan 2005 13:36:30 -0800 From: Darryl Okahata Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 21:36:33 -0000 Oliver Fromme wrote: > I would suggest trying this simple hack: > > cd /var/spool/directory ; cat . | strings | xargs rm -f Since the original poster was willing to use -rf, wouldn't it be better to do: cd /var/spool/directory ; find . -type f -print0 | xargs -0 rm -f Slightly more typing, but more robust. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:39:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 000F516A4CE for ; Thu, 20 Jan 2005 21:39:07 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEFE443D49 for ; Thu, 20 Jan 2005 21:39:07 +0000 (GMT) (envelope-from decibel@decibel.org) Received: by flake.decibel.org (Postfix, from userid 1001) id 771E11C900; Thu, 20 Jan 2005 15:39:06 -0600 (CST) Date: Thu, 20 Jan 2005 15:39:06 -0600 From: "Jim C. Nasby" To: freebsd-stable@freebsd.org Message-ID: <20050120213906.GC67721@decibel.org> Mail-Followup-To: "Jim C. Nasby" , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 4.10-RELEASE-p3 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i Subject: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:39:08 -0000 Question one: how do I disable write caching on IDE drives? I know the setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is FreeBSD 4.10, btw. Also, has any thought been given to making the default 0, like it is for SCSI devices? I'm honestly surprised and disappointed that the default is speed over data integrity. Question two: is there any support for SMART in FreeBSD? I see that atacontrol cap displays the status (supported and disabled), but I don't know of any way to turn it on. Likewise, what about the other options shown by atacontrol cap? -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:44:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB65316A4CE for ; Thu, 20 Jan 2005 21:44:58 +0000 (GMT) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 2553643D2F for ; Thu, 20 Jan 2005 21:44:58 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com) (mikej@69.193.222.195 with login) by smtp103.rog.mail.re2.yahoo.com with SMTP; 20 Jan 2005 21:44:57 -0000 Received: from 207.219.213.162 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Thu, 20 Jan 2005 16:44:59 -0500 (EST) Message-ID: <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> In-Reply-To: <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> References: <3aaaa3a0501181530975fecf@mail.gmail.com> <3aaaa3a050120105459f7d015@mail.gmail.com> <3aaaa3a050120111777ada357@mail.gmail.com> <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> Date: Thu, 20 Jan 2005 16:44:59 -0500 (EST) From: "Mike Jakubik" To: "Paul Mather" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:44:58 -0000 Paul Mather said: > On Thu, 2005-01-20 at 19:17 +0000, Chris wrote: >> what does -fno-strict-alias do? I cannot find it in man gcc > > It is a truncation of "-fno-strict-aliasing". The flag does not appear > to be described in the gcc man page, but is documented in the gcc info > page (search for "-fstrict-aliasing"). To quote the info page, > -fstrict-aliasing "allows the compiler to assume the strictest aliasing > rules applicable to the language being compiled. ..." Wouldn't we want strict aliasing then? From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:51:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C66F416A4CE for ; Thu, 20 Jan 2005 21:51:09 +0000 (GMT) Received: from mail.efacilitas.de (efacilitas.de [213.133.110.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2848743D4C for ; Thu, 20 Jan 2005 21:51:09 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.alpha-tierchen.de (port-212-202-169-228.dynamic.qsc.de [212.202.169.228]) by mail.efacilitas.de (Postfix) with ESMTP id AC505123A05 for ; Thu, 20 Jan 2005 22:50:48 +0100 (CET) Received: from localhost (localhost.local [127.0.0.1]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 06E7CCCE0D2 for ; Thu, 20 Jan 2005 22:50:27 +0100 (CET) Received: from mail.alpha-tierchen.de ([127.0.0.1]) by localhost (mail.efacilitas.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42997-06 for ; Thu, 20 Jan 2005 22:50:25 +0100 (CET) Received: from alpha (alpha.local [192.168.1.2]) by mail.alpha-tierchen.de (Postfix) with ESMTP id B14E1CCE0D4 for ; Thu, 20 Jan 2005 22:50:24 +0100 (CET) From: =?UTF-8?B?QmrDtnJuIEvDtm5pZw==?= To: Date: Thu, 20 Jan 2005 22:51:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT/OjBFymtzFlXeRHeitNRXz0MR8g== Message-Id: <20050120215024.B14E1CCE0D4@mail.alpha-tierchen.de> X-Virus-Scanned: amavisd-new at alpha-tierchen.de Subject: Re: FreeBSD 4.11-RC3 available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:51:09 -0000 > It has been decided to provide two disc1 ISO > images, one with the KDE windowing system > packages on it and the other with the GNOME > windowing system packages. They are named > disc1-kde and disc1-gnome respectively. Other > than which major windowing system is on them > they are identical. It might be useful to put xpdf-3.00_5.tgz with dependencies on = disc1-gnome too or even gpdf it is possible. Regards Bj=C3=B6rn From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:52:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33B5716A4CE for ; Thu, 20 Jan 2005 21:52:37 +0000 (GMT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A06EF43D55 for ; Thu, 20 Jan 2005 21:52:36 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KLqaGT031396; Thu, 20 Jan 2005 16:52:36 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30572-09; Thu, 20 Jan 2005 16:52:36 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KLqavY031373; Thu, 20 Jan 2005 16:52:36 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id j0KLqTQo046869; Thu, 20 Jan 2005 16:52:29 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.0.14.0.20050120165105.10d565d8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Thu, 20 Jan 2005 16:54:06 -0500 To: "Jim C. Nasby" , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050120213906.GC67721@decibel.org> References: <20050120213906.GC67721@decibel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan2b Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:52:37 -0000 At 04:39 PM 20/01/2005, Jim C. Nasby wrote: >Question one: how do I disable write caching on IDE drives? I know the >setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is >FreeBSD 4.10, btw. Yes, you can put it in there. >Also, has any thought been given to making the default 0, like it is for >SCSI devices? I'm honestly surprised and disappointed that the default >is speed over data integrity. It has been discussed quite a bit before and for a number of reasons, the default on was chosen. (google if you want to see the various reasons) >Question two: is there any support for SMART in FreeBSD? RELENG_5 with /usr/ports/sysutils/smartmontools/ works really well. But you need to move to RELENG_5. ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 21:56:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFF7A16A4CE for ; Thu, 20 Jan 2005 21:56:15 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81EDD43D4C for ; Thu, 20 Jan 2005 21:56:15 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-113-125.roa.east.verizon.net [151.199.113.125]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id j0KLuEiB082444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2005 16:56:14 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id j0KLu8m0000798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2005 16:56:09 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id j0KLu89Y000797; Thu, 20 Jan 2005 16:56:08 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: Mike Jakubik In-Reply-To: <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> References: <3aaaa3a0501181530975fecf@mail.gmail.com> <3aaaa3a050120105459f7d015@mail.gmail.com> <3aaaa3a050120111777ada357@mail.gmail.com> <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 20 Jan 2005 16:56:07 -0500 Message-Id: <1106258167.582.10.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 21:56:16 -0000 On Thu, 2005-01-20 at 16:44 -0500, Mike Jakubik wrote: > Paul Mather said: > > > On Thu, 2005-01-20 at 19:17 +0000, Chris wrote: > >> what does -fno-strict-alias do? I cannot find it in man gcc > > > > It is a truncation of "-fno-strict-aliasing". The flag does not appear > > to be described in the gcc man page, but is documented in the gcc info > > page (search for "-fstrict-aliasing"). To quote the info page, > > -fstrict-aliasing "allows the compiler to assume the strictest aliasing > > rules applicable to the language being compiled. ..." > > Wouldn't we want strict aliasing then? Yes, but unfortunately some ports circumvent the strict aliasing rules, which is why those ports break when building with -O2 (which causes -fstrict-aliasing to be enabled). Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 22:30:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F6B816A4CE; Thu, 20 Jan 2005 22:30:42 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4136043D2F; Thu, 20 Jan 2005 22:30:41 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0KMTRxC096358 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 21 Jan 2005 09:30:28 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: <41EFB111.8010906@michaelmeltzer.com> References: <41EFB111.8010906@michaelmeltzer.com> Mime-Version: 1.0 (Apple Message framework v619) Message-Id: From: Jean-Yves Avenard Date: Fri, 21 Jan 2005 09:30:07 +1100 To: Michael Meltzer X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.2 required=6.5 tests=ALL_TRUSTED,J_CHICKENPOX_42 autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-scsi@FreeBSD.ORG cc: freebsd stable cc: Vinod Kashyap cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 22:30:42 -0000 Well, it may work for you, but not for me. Still hangs exactly in the same spot. Jean-Yves On 21/01/2005, at 12:24 AM, Michael Meltzer wrote: > looks like patch3 worked, good job! I had to turn off TWA_DEBUG to=20 > get the boot going, the debug was starving the boot on a 9600 baud=20 > terminal. I can increase the speed and caputer the output on monday if=20= > it will help(it on the large side, bigger than the 10,000 line capture=20= > buffer in am using).=A0 I incude 2 iozone reports, the first one the = new=20 > driver the second one the old driver, Is thier a way to increase the=20= > "read ahead" in freebsd?? -mjm > > --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 22:36:19 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5FAE16A4CE for ; Thu, 20 Jan 2005 22:36:19 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1444F43D1F for ; Thu, 20 Jan 2005 22:36:19 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0KMaIAF039008 for ; Thu, 20 Jan 2005 16:36:18 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Thu Jan 20 16:36:18 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0KMaIMD039006; Thu, 20 Jan 2005 16:36:18 -0600 (CST) Message-ID: <20050120163618.A38962@Denninger.Net> Date: Thu, 20 Jan 2005 16:36:18 -0600 From: Karl Denninger To: Mike Tancsa , freebsd-stable@freebsd.org References: <20050119151301.A22310@Denninger.Net> <6.2.0.14.0.20050120115013.088cd320@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <6.2.0.14.0.20050120115013.088cd320@64.7.153.2>; from Mike Tancsa on Thu, Jan 20, 2005 at 11:55:24AM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 22:36:19 -0000 On Thu, Jan 20, 2005 at 11:55:24AM -0500, Mike Tancsa wrote: > At 04:13 PM 19/01/2005, Karl Denninger wrote: > >I'm having a lot of trouble believing this is an actual disk problem. Among > >other things, its happening at different places - not always at the same > >block. > > If you have the drives on a RELENG_5 box, try > /usr/ports/sysutils/smartmontools/ > Its quite handy to sort of various drive issues as well as to monitor for > ongoing errors via the daemon. > > ---Mike Very cool - didn't know that was there. That's one very useful tool! -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 22:37:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A5FE16A4CE for ; Thu, 20 Jan 2005 22:37:35 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8EB643D55 for ; Thu, 20 Jan 2005 22:37:34 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0KMbYAF039105 for ; Thu, 20 Jan 2005 16:37:34 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Thu Jan 20 16:37:34 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0KMbYtF039101; Thu, 20 Jan 2005 16:37:34 -0600 (CST) Message-ID: <20050120163734.B38962@Denninger.Net> Date: Thu, 20 Jan 2005 16:37:34 -0600 From: Karl Denninger To: Darryl Okahata , freebsd-stable@freebsd.org References: <20050119213605.B26294@Denninger.Net> <200501201617.IAA07355@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200501201617.IAA07355@mina.soco.agilent.com>; from Darryl Okahata on Thu, Jan 20, 2005 at 08:17:40AM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 22:37:35 -0000 On Thu, Jan 20, 2005 at 08:17:40AM -0800, Darryl Okahata wrote: > Karl Denninger wrote: > > > These two are DiamondMax10s - let's hope that this doesn't apply to that > > line as well. > > Out of curiosity, why didn't you consider Seagate ? The recent > Maxtors that I have, if run 24x7, seem to die just after the warranty > expires (for me, just over a year). I'm now switching back to Seagate, > as they now have a nice 5-year warranty, but I don't have much > experience with these new drives. The Maxtors I'm getting have 3-year warranties. Seagate's have been getting very poor performance reviews of late..... ....of course a drive that pukes is worse than one that is slow! -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 23:26:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11B4C16A4CE for ; Thu, 20 Jan 2005 23:26:25 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE36D43D39 for ; Thu, 20 Jan 2005 23:26:24 +0000 (GMT) (envelope-from darrylo@soco.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 7DB412C1C for ; Thu, 20 Jan 2005 16:26:22 -0700 (MST) Received: from wcosvs02.cos.agilent.com (wcosvs02.cos.agilent.com [130.29.152.188]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 6685EF95 for ; Thu, 20 Jan 2005 16:26:24 -0700 (MST) Received: from mina.soco.agilent.com ([141.121.54.157]) by wcosvs02.cos.agilent.com with InterScan Messaging Security Suite; Thu, 20 Jan 2005 16:26:22 -0700 Received: from mina.soco.agilent.com (localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id PAA16070; Thu, 20 Jan 2005 15:26:22 -0800 (PST) Message-Id: <200501202326.PAA16070@mina.soco.agilent.com> To: Karl Denninger In-Reply-To: Your message of "Thu, 20 Jan 2005 16:37:34 CST." <20050120163734.B38962@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Thu, 20 Jan 2005 15:26:21 -0800 From: Darryl Okahata cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 23:26:25 -0000 Karl Denninger wrote: > Seagate's have been getting very poor performance reviews of late..... Do you have any URLs? While I haven't been following disk drives closely, I haven't seen anything that points at "very poor" performance ("average"/boring performance, yes, but nothing really bad). Thanks. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 23:37:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0300516A4CE for ; Thu, 20 Jan 2005 23:37:03 +0000 (GMT) Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id B02A243D45 for ; Thu, 20 Jan 2005 23:37:01 +0000 (GMT) (envelope-from gnb@itga.com.au) Received: from melmail.itga.com.au (lenford.itga.com.au [10.132.2.150]) by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id j0KNalJn070905; Fri, 21 Jan 2005 10:36:49 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from [10.132.2.163] (hellcat.itga.com.au [10.132.2.163]) by melmail.itga.com.au (Postfix) with ESMTP id 4A60844C87; Fri, 21 Jan 2005 10:36:47 +1100 (EST) Message-ID: <41F0408F.2010607@itga.com.au> Date: Fri, 21 Jan 2005 10:36:47 +1100 From: Gregory Bond User-Agent: Mozilla Thunderbird 1.0 (X11/20050104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: martin hudec References: <200501201948.42707.emanuel.strobl@gmx.net> <200501202000.43688.emanuel.strobl@gmx.net> <20050120192739.GD5431@pleiades.aeternal.net> In-Reply-To: <20050120192739.GD5431@pleiades.aeternal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Higher ATA-Mode -> lower speed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 23:37:03 -0000 martin hudec wrote: > amber# dd if=/dev/zero of=/usr/testfile bs=64k count=2000 > 131072000 bytes transferred in 2.546718 secs (51467023 bytes/sec) > > These are not very usefull tests of raw disk bandwith because they use the filesystem (and are hence subject to the vagiaries of block allocation, etc) and are not likely to be very repeatable or comparable. Nore are the big enough or long enough to reduce the variance of the result or cover one-off spikes (e.g. what if it is running just when a cron job happens to kick off?) From owner-freebsd-stable@FreeBSD.ORG Thu Jan 20 23:48:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED66916A4CE for ; Thu, 20 Jan 2005 23:48:04 +0000 (GMT) Received: from mail.efacilitas.de (efacilitas.de [213.133.110.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D22E43D3F for ; Thu, 20 Jan 2005 23:48:04 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.alpha-tierchen.de (port-212-202-169-228.dynamic.qsc.de [212.202.169.228]) by mail.efacilitas.de (Postfix) with ESMTP id 0B396123F81; Fri, 21 Jan 2005 00:47:45 +0100 (CET) Received: from localhost (localhost.local [127.0.0.1]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 3BB6BCCE940; Fri, 21 Jan 2005 00:47:23 +0100 (CET) Received: from mail.alpha-tierchen.de ([127.0.0.1]) by localhost (mail.efacilitas.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15284-09; Fri, 21 Jan 2005 00:47:21 +0100 (CET) Received: from alpha (alpha.local [192.168.1.2]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 282D9CCE93F; Fri, 21 Jan 2005 00:47:21 +0100 (CET) From: =?utf-8?B?QmrDtnJuIEvDtm5pZw==?= To: "'Darryl Okahata'" Date: Fri, 21 Jan 2005 00:48:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <200501202136.NAA13625@mina.soco.agilent.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcT/OHuXvzedhl9vQyO/BOmP/Qvo1wAEZZbQ Message-Id: <20050120234721.282D9CCE93F@mail.alpha-tierchen.de> X-Virus-Scanned: amavisd-new at alpha-tierchen.de cc: freebsd-stable@freebsd.org Subject: RE: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Jan 2005 23:48:05 -0000 Darryl Okahata wrote: > find . -type f -print0 | xargs -0 rm -f > Slightly more typing, but more robust. The find utility of FreeBSD knows a -delete option, e.g.: find /path/to/your/directory -type f -delete Regards Bj=C3=B6rn From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 00:09:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 309E016A4CE for ; Fri, 21 Jan 2005 00:09:09 +0000 (GMT) Received: from dd3.kasserver.com (dd2718.kasserver.com [81.209.184.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F67143D55 for ; Fri, 21 Jan 2005 00:09:08 +0000 (GMT) (envelope-from freebsd@chillt.de) Received: from [192.168.0.5] (dsl-082-083-049-133.arcor-ip.net [82.83.49.133]) by dd3.kasserver.com (Postfix) with ESMTP id A237E81159; Fri, 21 Jan 2005 01:08:30 +0100 (CET) Message-ID: <41F0482D.7080308@chillt.de> Date: Fri, 21 Jan 2005 01:09:17 +0100 From: Bartosz Fabianowski User-Agent: Mozilla Thunderbird 1.0 (X11/20050107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gavin Atkinson References: <41EF0B1E.6010209@chillt.de> <1106223310.68614.4.camel@buffy.york.ac.uk> In-Reply-To: <1106223310.68614.4.camel@buffy.york.ac.uk> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: Kris Kennaway Subject: Re: Persisting troubles with periodic stalls every few minutes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 00:09:09 -0000 > top -qbSs 1 -d max > /var/tmp/somefile Thank you, that helped. Although top did not tell me which process was guilty directly, it allowed me to track it down. For the record: The process hogging the entire CPU was Xorg, which in turn was being pushed by the KDE World Clock. At my screen resolution, the clock redraws itself every 45 minutes. Apparently, it does this in a very inefficient way, using a lot of CPU and making heavy use of the disk drive. I have filed a bug report on this with KDE: http://bugs.kde.org/show_bug.cgi?id=97565 Thanks Gavin and Kris for your input, - Bartosz From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 01:16:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D34CE16A4CE for ; Fri, 21 Jan 2005 01:16:57 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64FBC43D45 for ; Fri, 21 Jan 2005 01:16:57 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IAN7KD00.6J8; Thu, 20 Jan 2005 17:17:01 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005012017202014487 ; Thu, 20 Jan 2005 17:20:20 -0800 From: "Vinod Kashyap" To: Michael Meltzer Date: Thu, 20 Jan 2005 17:16:49 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd stable Subject: RE: twa breakage onAMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 01:16:57 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer > Sent: Thursday, January 20, 2005 5:25 AM > To: Vinod Kashyap > Cc: freebsd stable > Subject: Re: twa breakage on > AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit > = > = > looks like patch3 worked, good job! I had to turn off TWA_DEBUG to get > the boot going, the debug was starving the boot on a 9600 = > baud terminal. > I can increase the speed and caputer the output on monday if it will > help(it on the large side, bigger than the 10,000 line = > capture buffer in Don't worry about capturing all the output... > am using). I incude 2 iozone reports, the first one the new = > driver the > second one the old driver, Is thier a way to increase the "read ahead" > in freebsd?? -mjm > = Setting sysctl vfs.read_max to about 512 helps in sequential reads. > iozone -s 20480m -r 60 -i 0 -i 1 -t 1 > Iozone: Performance Test of File I/O > Version $Revision: 3.196 $ > Compiled for 64 bit mode. > Build: freebsd > = > Contributors:William Norcott, Don Capps, Isom Crawford, Kirby > Collins > Al Slater, Scott Rhine, Mike Wisner, Ken Goss > Steve Landherr, Brad Smith, Mark Kelly, = > Dr. Alain CYR, > Randy Dunlap, Mark Montague, Dan Million, > Jean-Marc Zucconi, Jeff Blomberg. > = > Run began: Thu Jan 20 07:45:52 2005 > = > File size set to 20971520 KB > Record Size 60 KB > Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 > Output is in Kbytes/sec > Time Resolution =3D 0.000001 seconds. > Processor cache size set to 1024 Kbytes. > Processor cache line size set to 32 bytes. > File stride size set to 17 * record size. > Throughput test with 1 process > Each process writes a 20971520 Kbyte file in 60 Kbyte records > = > Children see throughput for 1 initial writers =3D = > 78219.47 KB/sec > Parent sees throughput for 1 initial writers =3D = > 78060.45 KB/sec > Min throughput per process =3D = > 78219.47 KB/sec > Max throughput per process =3D = > 78219.47 KB/sec > Avg throughput per process =3D = > 78219.47 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 rewriters =3D = > 19394.53 KB/sec > Parent sees throughput for 1 rewriters =3D = > 19394.32 KB/sec > Min throughput per process =3D = > 19394.53 KB/sec > Max throughput per process =3D = > 19394.53 KB/sec > Avg throughput per process =3D = > 19394.53 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 readers =3D = > 55960.09 KB/sec > Parent sees throughput for 1 readers =3D = > 55954.25 KB/sec > Min throughput per process =3D = > 55960.09 KB/sec > Max throughput per process =3D = > 55960.09 KB/sec > Avg throughput per process =3D = > 55960.09 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 re-readers =3D = > 55948.26 KB/sec > Parent sees throughput for 1 re-readers =3D = > 55946.60 KB/sec > Min throughput per process =3D = > 55948.26 KB/sec > Max throughput per process =3D = > 55948.26 KB/sec > Avg throughput per process =3D = > 55948.26 KB/sec > Min xfer =3D = > 20971500.00 KB > = > = > = > iozone test complete. > = > iozone -s 20480m -r 60 -i 0 -i 1 -t 1 > Iozone: Performance Test of File I/O > Version $Revision: 3.196 $ > Compiled for 64 bit mode. > Build: freebsd > = > Contributors:William Norcott, Don Capps, Isom Crawford, Kirby > Collins > Al Slater, Scott Rhine, Mike Wisner, Ken Goss > Steve Landherr, Brad Smith, Mark Kelly, = > Dr. Alain CYR, > Randy Dunlap, Mark Montague, Dan Million, > Jean-Marc Zucconi, Jeff Blomberg. > = > Run began: Mon Dec 20 21:03:36 2004 > = > File size set to 20971520 KB > Record Size 60 KB > Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 > Output is in Kbytes/sec > Time Resolution =3D 0.000001 seconds. > Processor cache size set to 1024 Kbytes. > Processor cache line size set to 32 bytes. > File stride size set to 17 * record size. > Throughput test with 1 process > Each process writes a 20971520 Kbyte file in 60 Kbyte records > = > Children see throughput for 1 initial writers =3D = > 78738.67 KB/sec > Parent sees throughput for 1 initial writers =3D = > 78716.55 KB/sec > Min throughput per process =3D = > 78738.67 KB/sec > Max throughput per process =3D = > 78738.67 KB/sec > Avg throughput per process =3D = > 78738.67 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 rewriters =3D = > 32126.46 KB/sec > Parent sees throughput for 1 rewriters =3D = > 32125.77 KB/sec > Min throughput per process =3D = > 32126.46 KB/sec > Max throughput per process =3D = > 32126.46 KB/sec > Avg throughput per process =3D = > 32126.46 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 readers =3D = > 58563.70 KB/sec > Parent sees throughput for 1 readers =3D = > 58557.14 KB/sec > Min throughput per process =3D = > 58563.70 KB/sec > Max throughput per process =3D = > 58563.70 KB/sec > Avg throughput per process =3D = > 58563.70 KB/sec > Min xfer =3D = > 20971500.00 KB > = > Children see throughput for 1 re-readers =3D = > 58583.77 KB/sec > Parent sees throughput for 1 re-readers =3D = > 58581.98 KB/sec > Min throughput per process =3D = > 58583.77 KB/sec > Max throughput per process =3D = > 58583.77 KB/sec > Avg throughput per process =3D = > 58583.77 KB/sec > Min xfer =3D = > 20971500.00 KB > = > = > = > iozone test complete. > = > = > = > = > Copyright (c) 1992-2005 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 5.3-STABLE #21: Thu Jan 20 01:21:10 EST 2005 > root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0xf51 Stepping =3D 1 > = > Features=3D0x78bfbff ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=3D0xe0500800 > real memory =3D 6442450944 (6144 MB) > avail memory =3D 5964316672 (5688 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > unknown: I/O range not supported > unknown: I/O range not supported > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 6.0 on pci0 > pci1: on pcib1 > pci1: at device 6.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > bge0: mem > 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:50:45:5b:8e:76 > bge1: mem > 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:50:45:5b:8e:77 > atapci1: port > 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem > 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device = > 5.0 on pci2 > atapci1: failed: rid 0x20 is memory, requested 4 > ata2: channel #0 on atapci1 > ata3: channel #1 on atapci1 > ata4: channel #2 on atapci1 > ata5: channel #3 on atapci1 > pci0: at device 10.1 = > (no driver > attached) > pcib3: at device 11.0 on pci0 > pci3: on pcib3 > 3ware device driver for 9000 series storage controllers, version: > 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem > 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device = > 2.0 on pci3 > twa0: [GIANT-LOCKED] > twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > pci0: at device 11.1 = > (no driver > attached) > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse, device ID 3 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > flags 0x10 on > acpi0 > sio0: type 16550A, console > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > ppc0: port = > 0x778-0x77f,0x378-0x37f irq 7 drq > 4 on acpi0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > orm0: at iomem > 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7ff > f on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x100> > 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 > Timecounters tick every 1.000 msec > IP Filter: v3.4.35 initialized. Default =3D block all, Logging = > =3D enabled > acd0: DVDROM at ata0-master UDMA33 > da0 at twa0 bus 0 target 0 lun 0 > da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device > da0: 100.000MB/s transfers > da0: 70550MB (144486400 512 byte sectors: 255H 63S/T 8993C) > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > Pre-seeding PRNG: kickstart. > Loading configuration files. > Entropy harvesting: interrupts ethernet point_to_point kickstart. > swapon: adding /dev/da0s1b as swap device > Starting file system checks: > /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/da0s1a: clean, 3005287 free (1559 frags, 375466 blocks, 0.1% > fragmentation) > /dev/da0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/da0s1h: clean, 15168492 free (20 frags, 1896059 blocks, 0.0% > fragmentation) > /dev/da0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/da0s1g: clean, 5010318 free (56766 frags, 619194 blocks, 0.9% > fragmentation) > /dev/da0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/da0s1f: clean, 6078377 free (553 frags, 759728 blocks, 0.0% > fragmentation) > Enabling ipfilter. > ioctl(SIOCIPFL6): Invalid argument > Setting hostname: web7.thecenturiongroup.com. > Installing NAT rules. > 0 entries flushed from NAT table > 0 entries flushed from NAT list > bge0: flags=3D8843 mtu 1500 > options=3D1a > inet 192.32.248.84 netmask 0xffffff00 broadcast 192.32.248.255 > ether 00:50:45:5b:8e:76 > media: Ethernet autoselect (none) > status: no carrier > bge1: flags=3D8843 mtu 1500 > options=3D1a > inet 10.200.0.7 netmask 0xffffff00 broadcast 10.200.0.255 > ether 00:50:45:5b:8e:77 > media: Ethernet autoselect (none) > status: no carrier > lo0: flags=3D8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > filter sync'd > add net default: gateway 10.200.0.1 > Additional routing options: IP gateway=3DYES. > Starting devd. > Mounting NFS file systems:. > Starting syslogd. > Jan 20 01:24:35 web7 syslogd: kernel boot file is /boot/kernel/kernel > ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib > /usr/local/lib > Starting usbd. > No USB host controllers found > Starting local daemons:. > Updating motd. > Starting ntpd. > Jan 20 01:24:35 web7 ntpd[393]: no IPv6 interfaces found > Configuring syscons: blanktime screensaver. > Starting sshd. > Initial amd64 initialization:. > Additional ABI support:. > Starting cron. > Local package initialization:. > Additional TCP options:. > Starting moused:. > Starting inetd. > Starting background file system checks in 60 seconds. > = > Thu Jan 20 01:24:36 EST 2005 > = > FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) > = > login: Jan 20 01:24:43 web7 ntpd[393]: sendto(139.88.35.33): = > No route to > host > Jan 20 01:24:44 web7 ntpd[393]: sendto(208.184.49.9): No route to host > Jan 20 01:24:45 web7 ntpd[393]: sendto(216.200.93.8): No route to host > = > FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) > = > login: > = > = > _______________________________________________ > 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 Jan 21 02:30:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FF6516A4CE for ; Fri, 21 Jan 2005 02:30:08 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25BA343D4C for ; Fri, 21 Jan 2005 02:30:08 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j0L2TwpP050784; Thu, 20 Jan 2005 18:30:04 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200501210230.j0L2TwpP050784@gw.catspoiler.org> Date: Thu, 20 Jan 2005 18:29:58 -0800 (PST) From: Don Lewis To: spamrefuse@yahoo.com In-Reply-To: <20050120100638.88174.qmail@web54002.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-stable@FreeBSD.org Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 02:30:08 -0000 On 20 Jan, spam maps wrote: > Peter Jeremy wrote: >> My guess is that your ssh process is holding open >> file descriptors and the cron child process is >> waiting for these descriptors to close before >> wait()ing for the child. If this is true, then you >> should avoid it with something like: >> ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) >> I suspect that the & to put ssh in the background isn't necessary. > BINGO! > That works. Zombie has gone. Thank you. > >>>Leaving a zombie process around, means there's a > kind >>>of bug/mistake somewhere, right? >> >> Yes. But it's not necessarily a bug in FreeBSD :-). > > So, after you've given me a complicated solution to > avoid the zombie, can you tell which program is at > error here? Cron, ssh, or FreeBSD? Maybe none of the above. I suspect that cron is waiting for stdout and/or stderr from the cron job to close before it reaps the child. The reason is that cron wants to consume any output of the cron job, and if the cron job writes to stdout or stderr, cron will mail it to the owner of the job. The ssh -f flag is what is causing the problem, normally stdout and stderr get closed when the top level process of a cron job exits. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 03:32:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0999D16A4CE for ; Fri, 21 Jan 2005 03:32:03 +0000 (GMT) Received: from pop-a065d05.pas.sa.earthlink.net (pop-a065d05.pas.sa.earthlink.net [207.217.121.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4BB243D45 for ; Fri, 21 Jan 2005 03:32:02 +0000 (GMT) (envelope-from andrei@kableu.com) Received: from h-69-3-26-80.snvacaid.dynamic.covad.net ([69.3.26.80] helo=mail.kableu.com) by pop-a065d05.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1CrpWk-00012C-00 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 19:32:02 -0800 Received: from warrior.kableu.com (warrior.kableu.com [192.168.0.1]) by mail.kableu.com (Postfix) with ESMTP id 6472AC0DB for ; Thu, 20 Jan 2005 19:32:02 -0800 (PST) Received: by warrior.kableu.com (Postfix, from userid 1001) id D89A411445; Thu, 20 Jan 2005 19:32:01 -0800 (PST) Date: Thu, 20 Jan 2005 19:32:01 -0800 From: Andrew Konstantinov To: freebsd-stable@freebsd.org Message-ID: <20050121033201.GA81807@warrior.kableu.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: secure level 2 unable to modify pf rules X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 03:32:03 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, The manual page for securelevel says that secure level 3 provides the same functionality as secure level 2 plus the protection of pf/ipf/ipfw against modification. Since pf/ipf/ipfw protection is an addition, I assume that it should not be present with secure level 2. For some reason that's not the reality. gater# id uid=0(root) gid=0(wheel) groups=0(wheel), 5(operator) gater# uname -rs FreeBSD 5.3-RELEASE-p5 gater# sysctl kern.securelevel kern.securelevel: 2 gater# pfctl -F all pfctl: pfctl_clear_rules: Operation not permitted gater# Is there a bug in the documentation or in the implementation of secure level? Or perhaps, did I misinterpret something? Thanks in advance, Andrew --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8Hexg+6MtxSjexcRAtowAKCmoTEt5PtPHh96zdea6/HxFe/zYwCeI+kp C4LFfe9yHCRgCmISL9vrELQ= =gTa9 -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 04:06:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A91A16A4CE for ; Fri, 21 Jan 2005 04:06:57 +0000 (GMT) Received: from smtp1.mc.surewest.net (smtp1.mc.surewest.net [66.60.130.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B85643D53 for ; Fri, 21 Jan 2005 04:06:57 +0000 (GMT) (envelope-from dislists@updegrove.net) Received: (s3-15561); Thu, 20 Jan 2005 20:02:02 -0800 Received: from unknown (HELO updegrove.net) (64.30.97.117) by smtp1.mc.surewest.net (s3-smtpd/0.90-beta3) with SMTP; Thu, 20 Jan 2005 20:02:02 -0800 Received: (qmail 96449 invoked by uid 98); 21 Jan 2005 04:07:22 -0000 Received: from dislists@updegrove.net by smeagol.skynet by uid 1008 with qmail-scanner-1.22-st-qms (f-prot: 4.4.8/3.14.13. Clear:RC:1(192.168.0.2):. Processed in 2.368261 secs); 21 Jan 2005 04:07:22 -0000 X-Antivirus-RickUp-Mail-From: dislists@updegrove.net via smeagol.skynet X-Antivirus-RickUp: 1.22-st-qms (Clear:RC:1(192.168.0.2):. Processed in 2.368261 secs Process 96438) Received: from unknown (HELO ?192.168.0.2?) (192.168.0.2) by updegrove.net with SMTP; 21 Jan 2005 04:07:18 -0000 Message-ID: <41F08179.7030705@updegrove.net> Date: Thu, 20 Jan 2005 20:13:45 -0800 From: Rick Updegrove User-Agent: Mozilla Thunderbird 1.0 (X11/20050113) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TST: smtp1 SNWK3 0.31-80 ip=64.30.97.117 Subject: /libexec/ld-elf.so.1: /lib/libc.so.5: Unsupported relocation type 136 in non-PLT relocations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 04:06:58 -0000 Hi all, I have been getting this all day today. I have no idea what caused it or how to fix it. Has anyone got a clue? Google doesn't seem too know much about it... /libexec/ld-elf.so.1: /lib/libc.so.5: Unsupported relocation type 136 in non-PLT relocations From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 06:14:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0681D16A4CE for ; Fri, 21 Jan 2005 06:14:27 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40D6243D4C for ; Fri, 21 Jan 2005 06:14:26 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0L6ENa3030282 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 21 Jan 2005 17:14:24 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0L6ENxP068828; Fri, 21 Jan 2005 17:14:23 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0L6EMGv068827; Fri, 21 Jan 2005 17:14:22 +1100 (EST) (envelope-from pjeremy) Date: Fri, 21 Jan 2005 17:14:22 +1100 From: Peter Jeremy To: Darryl Okahata Message-ID: <20050121061421.GA68808@cirb503493.alcatel.com.au> References: <200501201130.j0KBUKMZ066099@lurza.secnetix.de> <200501202136.NAA13625@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501202136.NAA13625@mina.soco.agilent.com> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 06:14:27 -0000 On Thu, 2005-Jan-20 13:36:30 -0800, Darryl Okahata wrote: > Since the original poster was willing to use -rf, wouldn't it be >better to do: > >cd /var/spool/directory ; find . -type f -print0 | xargs -0 rm -f The original poster mentioned that "find" wouldn't work: find(1) uses fts(3) which reads the entire directory into memory. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 06:24:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E2416A4CE for ; Fri, 21 Jan 2005 06:24:27 +0000 (GMT) Received: from web54009.mail.yahoo.com (web54009.mail.yahoo.com [206.190.36.233]) by mx1.FreeBSD.org (Postfix) with SMTP id CA8A043D3F for ; Fri, 21 Jan 2005 06:24:26 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 71555 invoked by uid 60001); 21 Jan 2005 06:24:26 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=lDxxDk0mXGkW4WmK9xosHV9ib6fRaZQlLefH+ciSRcSSuo0oc+6HPesOEDquMVBLg1MM6lIh+Zt//ytSgMcf04yF68YiPzJ4ixxC6aOnfeScQqGWlmYFeRGow61bmZOalQvQNytElOxnEqsbknekjn7thYo+zUcdlmGMHsY3wp0= ; Message-ID: <20050121062426.71553.qmail@web54009.mail.yahoo.com> Received: from [147.46.44.181] by web54009.mail.yahoo.com via HTTP; Thu, 20 Jan 2005 22:24:26 PST Date: Thu, 20 Jan 2005 22:24:26 -0800 (PST) From: spam maps To: freebsd-stable@FreeBSD.org In-Reply-To: <200501210230.j0L2TwpP050784@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: User's cron job creates zombie process on 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 06:24:27 -0000 --- Don Lewis wrote: > On 20 Jan, spam maps wrote: > > Peter Jeremy wrote: > > >> My guess is that your ssh process is holding open > >> file descriptors and the cron child process is > >> waiting for these descriptors to close before > >> wait()ing for the child. If this is true, then > >> you > >> should avoid it with something like: > >> ( /usr/bin/ssh -n -f ${tunnel} >/dev/null 2>&1 & ) > >> > > I suspect that the & to put ssh in the background > isn't necessary. You're right indeed, it also works without the &. Thanks, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 06:47:17 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 161EF16A4DD for ; Fri, 21 Jan 2005 06:47:17 +0000 (GMT) Received: from pop-a065d01.pas.sa.earthlink.net (pop-a065d01.pas.sa.earthlink.net [207.217.121.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF09F43D1F for ; Fri, 21 Jan 2005 06:47:16 +0000 (GMT) (envelope-from andrei@kableu.com) Received: from h-69-3-26-80.snvacaid.dynamic.covad.net ([69.3.26.80] helo=mail.kableu.com) by pop-a065d01.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1CrsZg-0004Oq-00 for freebsd-stable@freebsd.org; Thu, 20 Jan 2005 22:47:16 -0800 Received: from warrior.kableu.com (warrior.kableu.com [192.168.0.1]) by mail.kableu.com (Postfix) with ESMTP id 7A73CC0DB for ; Thu, 20 Jan 2005 22:47:16 -0800 (PST) Received: by warrior.kableu.com (Postfix, from userid 1001) id D736C11445; Thu, 20 Jan 2005 22:47:15 -0800 (PST) Date: Thu, 20 Jan 2005 22:47:15 -0800 From: Andrew Konstantinov To: freebsd-stable@freebsd.org Message-ID: <20050121064715.GA82604@warrior.kableu.com> References: <20050121033201.GA81807@warrior.kableu.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <20050121033201.GA81807@warrior.kableu.com> User-Agent: Mutt/1.4.2.1i Subject: Re: secure level 2 unable to modify pf rules X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 06:47:17 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 07:32:01PM -0800, Andrew Konstantinov wrote: > Hello, >=20 > The manual page for securelevel says that secure level 3 provides the same > functionality as secure level 2 plus the protection of pf/ipf/ipfw against > modification. Since pf/ipf/ipfw protection is an addition, I assume that = it > should not be present with secure level 2. For some reason that's not the > reality. >=20 > gater# id > uid=3D0(root) gid=3D0(wheel) groups=3D0(wheel), 5(operator) > gater# uname -rs > FreeBSD 5.3-RELEASE-p5 > gater# sysctl kern.securelevel > kern.securelevel: 2 > gater# pfctl -F all > pfctl: pfctl_clear_rules: Operation not permitted > gater# >=20 > Is there a bug in the documentation or in the implementation of secure le= vel? > Or perhaps, did I misinterpret something? Replying to myself. This should fix the bug if it's really a bug and not a feature. --- sys/contrib/pf/net/pf_ioctl.c.orig Thu Jan 20 22:40:35 2005 +++ sys/contrib/pf/net/pf_ioctl.c Thu Jan 20 22:41:24 2005 @@ -1058,9 +1058,9 @@ /* XXX keep in sync with switch() below */ #ifdef __FreeBSD__ - if (securelevel_gt(td->td_ucred, 1)) + if (securelevel_gt(td->td_ucred, 2)) #else - if (securelevel > 1) + if (securelevel > 2) #endif switch (cmd) { case DIOCGETRULES: --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8KVzg+6MtxSjexcRAtBxAJoD60x1kh0bMGXuz8kaUMIyt4r41ACcCmwS hKTnKuTvsk/vZ4Ty6RouiT4= =78rh -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 07:49:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F3FF16A4CE for ; Fri, 21 Jan 2005 07:49:24 +0000 (GMT) Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [202.0.58.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA96543D46 for ; Fri, 21 Jan 2005 07:49:23 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (smtp-1a.paradise.net.nz [202.0.32.194]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IAN001F8PQA2G@linda-2.paradise.net.nz> for freebsd-stable@freebsd.org; Fri, 21 Jan 2005 20:49:22 +1300 (NZDT) Received: from [192.168.1.11] (218-101-14-86.paradise.net.nz [218.101.14.86]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 1CB3E828A3; Fri, 21 Jan 2005 20:49:22 +1300 (NZDT) Date: Fri, 21 Jan 2005 20:53:12 +1300 From: Mark Kirkwood In-reply-to: <20050120213906.GC67721@decibel.org> To: "Jim C. Nasby" Message-id: <41F0B4E8.9090507@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 References: <20050120213906.GC67721@decibel.org> cc: freebsd-stable@freebsd.org Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 07:49:24 -0000 Jim C. Nasby wrote: > Question one: how do I disable write caching on IDE drives? I know the > setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is > FreeBSD 4.10, btw. > In /boot/loader.conf will do it. > Also, has any thought been given to making the default 0, like it is for > SCSI devices? I'm honestly surprised and disappointed that the default > is speed over data integrity. I think it was trialled in 4.3 then changed for 4.4 (according to the handbook, the performance hit was considered to be too high) best wishes Mark From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 08:48:54 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5932D16A4CE for ; Fri, 21 Jan 2005 08:48:54 +0000 (GMT) Received: from new-av-inside.euba.sk (new-av.euba.sk [193.87.16.71]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FFAB43D49 for ; Fri, 21 Jan 2005 08:48:53 +0000 (GMT) (envelope-from solko@imladris.sk) Received: (qmail 60341 invoked from network); 21 Jan 2005 08:48:52 -0000 Received: from unknown (HELO new-av-amavisd-new) (127.0.0.1) by new-av-inside.euba.sk with SMTP; 21 Jan 2005 08:48:52 -0000 Received: from QMQPqq client ([127.0.0.1])port 10628) with QMQPqq id 75595-231; Fri, 21 Jan 2005 09:48:51 +0100 (CET) Received: from unknown (HELO bublitrtos) (193.87.16.6) by new-av-outside.euba.sk with SMTP; 21 Jan 2005 08:48:51 -0000 Message-ID: <005501c4ff96$078c9ed0$fb1d57c1@bublitrtos> From: "Martin Solciansky" To: References: <20050121033201.GA81807@warrior.kableu.com> <20050121064715.GA82604@warrior.kableu.com> Date: Fri, 21 Jan 2005 09:48:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new with NOD32 client/server version and clamav cc: Andrew Konstantinov Subject: Re: secure level 2 unable to modify pf rules X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Martin Solciansky List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 08:48:54 -0000 > Replying to myself. This should fix the bug if it's really a bug and not a > feature. already fixed. http://lists.freebsd.org/pipermail/cvs-src/2005-January/038877.html From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 09:19:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E864616A4CE for ; Fri, 21 Jan 2005 09:19:48 +0000 (GMT) Received: from wopr.ife.no (wopr.ife.no [128.39.4.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FCB643D53 for ; Fri, 21 Jan 2005 09:19:47 +0000 (GMT) (envelope-from stein@ife.no) Received: from [128.39.229.229] (dhcpaddr1.ife.no [128.39.229.229]) by wopr.ife.no (8.9.3/8.9.3) with ESMTP id KAA12735 for ; Fri, 21 Jan 2005 10:19:45 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20050120210923.GJ1168@manor.msen.com> References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> <20050119213605.B26294@Denninger.Net> <20050120210923.GJ1168@manor.msen.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Stein M. Sandbech" Date: Fri, 21 Jan 2005 10:20:39 +0100 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 09:19:49 -0000 On Jan 20, 2005, at 22:09, Michael R. Wayne wrote: > On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: >> >> What 'other vendor' have you found that makes RELIABLE SATA disks in >> the >> high capacity (e.g. 200-300gb) arena? > > WD now makes a SATA RAID line. HIGHLY recommended by 3ware. > FYI, Im using a Maxtor 6B200M0 200GB Serial ATA disk in a Shuttle XPC. FreeBSD 5.3R. I'm having problems with this disk just after startup, and it seem to me its related to temperature. Occationally, when starting up with disk @ room temperature I usually get a handfull of the checksum errors listed below. If it been sitting in the car for a while and temp is down to 15C or below, it wont start at all. Just giving a lot more of the CRC errors, and usually a kernel panic. I sometimes heated the disk with a hairdryer ;-) The normal procedure is now to start the PC and stop the boot process, and let the system heat up by itself, 5mins usaually. Any got similar experiences with the Maxtor SATA's? If this is the norm, I'd rather stay away from these Maxtor products... ----------------------- Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209417132 Jan 9 16:35:43 biosphere kernel: ad4: FAILURE - WRITE_DMA status=51 error=84 dma=0x02LBA=209417132Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209679308 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210203692 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210203692 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209950124 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209950124 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:47 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=302277292 Jan 9 16:35:47 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=302099020 Jan 9 16:35:55 biosphere kernel: ad4: TIMEOUT - READ_DMA retrying (2 retries left) LBA=302077068 Jan 9 16:35:55 biosphere kernel: ad4: FAILURE - READ_DMA timed outJan 9 16:35:59 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210465708 Jan 9 16:36:00 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=221218956 -------------------------- Best Regards Stein Morten From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 09:46:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED92A16A4CE for ; Fri, 21 Jan 2005 09:46:42 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9020943D49 for ; Fri, 21 Jan 2005 09:46:39 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AC752511C1; Fri, 21 Jan 2005 01:46:31 -0800 (PST) Date: Fri, 21 Jan 2005 01:46:31 -0800 From: Kris Kennaway To: Mike Jakubik Message-ID: <20050121094631.GA47975@xor.obsecurity.org> References: <3aaaa3a0501181530975fecf@mail.gmail.com> <3aaaa3a050120105459f7d015@mail.gmail.com> <3aaaa3a050120111777ada357@mail.gmail.com> <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 09:46:43 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 04:44:59PM -0500, Mike Jakubik wrote: > Paul Mather said: >=20 > > On Thu, 2005-01-20 at 19:17 +0000, Chris wrote: > >> what does -fno-strict-alias do? I cannot find it in man gcc > > > > It is a truncation of "-fno-strict-aliasing". The flag does not appear > > to be described in the gcc man page, but is documented in the gcc info > > page (search for "-fstrict-aliasing"). To quote the info page, > > -fstrict-aliasing "allows the compiler to assume the strictest aliasing > > rules applicable to the language being compiled. ..." >=20 > Wouldn't we want strict aliasing then? It's desirable, but a lot of ports contain bugs that are exposed by this option (the base system used to as well, but these are believed to all be fixed). Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8M93Wry0BWjoQKURAuaMAJ9Q1W69OTjjEtejPQxDVq1K7KnNrACgwClK aTiJpOuOTS1yY8Jfz3cIcOc= =EWlu -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 11:14:19 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28C9716A4CF for ; Fri, 21 Jan 2005 11:14:19 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 01F1743D4C for ; Fri, 21 Jan 2005 11:14:18 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 21 Jan 2005 11:14:16 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp022) with SMTP; 21 Jan 2005 12:14:16 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Fri, 21 Jan 2005 12:14:14 +0100 User-Agent: KMail/1.7.2 References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_HQO8B7C8ZC4Yjnp" Message-Id: <200501211214.15327.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: akiyama@jp.freebsd.org cc: bernd@bwct.de cc: Michal Mertl cc: freebsd-current@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 11:14:19 -0000 --Boundary-00=_HQO8B7C8ZC4Yjnp Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. This didn't apply cleanly against my -stable from today. Attached is a cleaned version (#define RSAQ_STATUS_CTS doesn't exist in -stable uplcom.c) for -stable which compiles for me. > > Michal --Boundary-00=_HQO8B7C8ZC4Yjnp Content-Type: text/x-diff; charset="iso-8859-15"; name="uplcom.c.2303x.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="uplcom.c.2303x.patch" --- sys/dev/usb/uplcom.c Fri Jan 21 10:49:09 2005 +++ sys/dev/usb/uplcom.c Fri Jan 21 11:01:33 2005 @@ -96,10 +96,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -112,29 +115,34 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define UPLCOM_SET_CRTSCTS_2303X 0x61 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -154,14 +162,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -297,6 +306,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -372,7 +382,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -615,7 +632,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, UPLCOM_SET_CRTSCTS_2303X); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -711,6 +731,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { /* XXX - shouldn't happen */ \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -741,7 +798,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --Boundary-00=_HQO8B7C8ZC4Yjnp-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 11:25:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5D0D16A4CE for ; Fri, 21 Jan 2005 11:25:53 +0000 (GMT) Received: from mail6.bluewin.ch (mail6.bluewin.ch [195.186.4.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B4A143D1D for ; Fri, 21 Jan 2005 11:25:53 +0000 (GMT) (envelope-from pietro@sdf.lonestar.org) Received: from [192.168.1.3] (83.79.85.32) by mail6.bluewin.ch (Bluewin AG 7.0.035) id 41E57ECE000BBD38 for freebsd-stable@freebsd.org; Fri, 21 Jan 2005 11:25:52 +0000 Message-ID: <41F0F4B2.5040808@sdf.lonestar.org> Date: Fri, 21 Jan 2005 12:25:22 +0000 From: Pietro Cerutti User-Agent: Mozilla Thunderbird 1.0 (X11/20041231) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 11:25:54 -0000 -------- Original Message -------- From: - Fri Jan 21 00:30:33 2005 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 Message-ID: <41F04D26.2060306@sdf.lonestar.org> Date: Fri, 21 Jan 2005 00:30:30 +0000 From: Pietro Cerutti User-Agent: Mozilla Thunderbird 1.0 (X11/20041231) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Imobach González Sosa Subject: Re: Realtek 8139 (rl) very poor performance References: <200501201630.04506.imobachgs@banot.net> In-Reply-To: <200501201630.04506.imobachgs@banot.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Imobach González Sosa wrote: > Hi all, Hi, > > I'm havin' a strange problem with my Realtek Network Adapter. There are many problems involving that card. I have the same card as yours on my FreeBSD-5.3 Release, and often got Watchgod Timeouts while cvsupping the port three. I sent an email to the author of the driver, but he never answered me. It seems that the problem's in the chipset, you've nothing to do about it... I solved the problem buying a new card. That's a shame, but that's it. Best Regards, -- Pietro Cerutti -- Powered by FreeBSD -- SDF Public Access UNIX System sdf.lonestar.org -- Pietro Cerutti -- Powered by FreeBSD -- SDF Public Access UNIX System sdf.lonestar.org From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 11:26:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D2A116A4F6 for ; Fri, 21 Jan 2005 11:26:06 +0000 (GMT) Received: from mail4.bluewin.ch (mail4.bluewin.ch [195.186.4.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2732843D4C for ; Fri, 21 Jan 2005 11:26:06 +0000 (GMT) (envelope-from pietro@sdf.lonestar.org) Received: from [192.168.1.3] (83.79.85.32) by mail4.bluewin.ch (Bluewin AG 7.0.035) id 41E5802C000D8C3A for freebsd-stable@freebsd.org; Fri, 21 Jan 2005 11:26:05 +0000 Message-ID: <41F0F4C1.60505@sdf.lonestar.org> Date: Fri, 21 Jan 2005 12:25:37 +0000 From: Pietro Cerutti User-Agent: Mozilla Thunderbird 1.0 (X11/20041231) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Realtek 8139 (rl) very poor performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 11:26:06 -0000 Imobach González Sosa wrote: > Hi all, Hi, > > I'm havin' a strange problem with my Realtek Network Adapter. There are many problems involving that card. I have the same card as yours on my FreeBSD-5.3 Release, and often got Watchgod Timeouts while cvsupping the port three. I sent an email to the author of the driver, but he never answered me. It seems that the problem's in the chipset, you've nothing to do about it... I solved the problem buying a new card. That's a shame, but that's it. Best Regards, -- Pietro Cerutti -- Powered by FreeBSD -- SDF Public Access UNIX System sdf.lonestar.org From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 12:06:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA63F16A4CE for ; Fri, 21 Jan 2005 12:06:55 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8219A43D41 for ; Fri, 21 Jan 2005 12:06:55 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0LC6f4H007616; Fri, 21 Jan 2005 07:06:41 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0LC6fm1007613; Fri, 21 Jan 2005 12:06:41 GMT (envelope-from robert@fledge.watson.org) Date: Fri, 21 Jan 2005 12:06:41 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Phillip Salzman In-Reply-To: <00b001c4fea0$7533d490$6745a8c0@MESE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: Very large directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 12:06:56 -0000 On Wed, 19 Jan 2005, Phillip Salzman wrote: > I have a pair of servers that act as SMTP/AV gateways. It seems that > even though we've told the AV software not to store messages, it is > anyway. > > They've been running for a little while now - and recently we've noticed > a lot of disk space disappearing. Shortly after that, a simple du into > our /var/spool returned a not so nice error: > > du: fts_read: Cannot allocate memory > > No matter what command I run on that directory, I just don't seem to > have enough available resources to show the files let alone delete them > (echo *, ls, find, rm -rf, etc.) > > I'm hoping someone else here might have a suggestion as to what I can do > to fix this. fts(3) is quite memory intensive--more though than strictly necessary for the functionality required by du(1). du is running into an administrative memory resource limit. Depending on the shell and login.conf configuration you're using, you may need to use the limits(1) command, limit(1), or tweak the user's class settings. I run into this on my boxes with 1,000,000 files or so in a directory, or with large directory trees (i.e., 7,000,000 files). Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 14:13:54 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05E4C16A4CE for ; Fri, 21 Jan 2005 14:13:54 +0000 (GMT) Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFB2943D31 for ; Fri, 21 Jan 2005 14:13:52 +0000 (GMT) (envelope-from k.joch@kmjeuro.com) Received: from sv03 (adsl.sbg.kmjeuro.com [62.99.198.46]) (authenticated bits=0)j0LEDfIw032925 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 21 Jan 2005 15:13:43 +0100 (CET) (envelope-from k.joch@kmjeuro.com) From: "Karl M. Joch" To: Date: Fri, 21 Jan 2005 15:13:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcT/w2XIuwo0ITXdQwOt4wdf+M1b9Q== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-CTS-CTSTZS-Mailserver-Information: please visit www.ctseuro.com for further instructions. Protected by www.ctseuro.com X-CTS-CTSTZS-Mailserver: Found to be clean X-CTS-CTSTZS-Mailserver-From: k.joch@kmjeuro.com Subject: gvinum - recovering from stale in multi user mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 14:13:54 -0000 Hello, build a few 5.3 boxes and found a problem which never occured before with vinum. when creating a new box (mirror only) the p1 plexes are stale till they are synced the first time. with gvinum when starting in multi user mode: usr.p1.s0 it cant be startet usr.p1 it starts and then gets a error filling the console very fast and i only can switch off the box. in single user mode with mounted and unmounted drives it works fine. is there any docu mentioning the differences in: creating gvinum volumes compared to vinum? recovering from stale comparing to vinum? the need for single user mode when recovering is very bad, because sometimes harddisk gets stale when read errors occured and there was a possibility to recover them till one arraived at the servers place. many thanks, karl From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 16:31:10 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19B4716A4CE for ; Fri, 21 Jan 2005 16:31:10 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E978F43D2D for ; Fri, 21 Jan 2005 16:31:09 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Fri, 21 Jan 2005 08:31:09 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B01855D08; Fri, 21 Jan 2005 08:31:06 -0800 (PST) To: Mark Kirkwood In-reply-to: Your message of "Fri, 21 Jan 2005 20:53:12 +1300." <41F0B4E8.9090507@paradise.net.nz> Date: Fri, 21 Jan 2005 08:31:06 -0800 From: "Kevin Oberman" Message-Id: <20050121163106.B01855D08@ptavv.es.net> cc: freebsd-stable@freebsd.org cc: "Jim C. Nasby" Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 16:31:10 -0000 > Date: Fri, 21 Jan 2005 20:53:12 +1300 > From: Mark Kirkwood > Sender: owner-freebsd-stable@freebsd.org > > Jim C. Nasby wrote: > > Question one: how do I disable write caching on IDE drives? I know the > > setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is > > FreeBSD 4.10, btw. > > > In /boot/loader.conf will do it. > > > Also, has any thought been given to making the default 0, like it is for > > SCSI devices? I'm honestly surprised and disappointed that the default > > is speed over data integrity. > I think it was trialled in 4.3 then changed for 4.4 (according to the > handbook, the performance hit was considered to be too high) Having been involved in the 4.x flip-flop, the performance cost on some systems can be HUGE! Backing up my laptop (40 GB) went from 40 minutes to five hours when the write cache was turned off. On the other hand, it is a real risk, especially when combined with softupdates. For servers that lack solid backup power (not a 10 minute UPS), I would probably turn it off. But for most systems it is probably worth the risks. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 16:32:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB00816A4CE; Fri, 21 Jan 2005 16:32:25 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C777443D41; Fri, 21 Jan 2005 16:32:24 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0LGWh7h025864; Fri, 21 Jan 2005 17:32:43 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <200501211214.15327.emanuel.strobl@gmx.net> References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> <200501211214.15327.emanuel.strobl@gmx.net> Content-Type: text/plain Date: Fri, 21 Jan 2005 17:32:19 +0100 Message-Id: <1106325139.754.6.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: akiyama@jp.freebsd.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 16:32:26 -0000 Emanuel Strobl wrote: > Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > > > I tested my patch for binary safety on CURRENT yesterday (dialed with > > ppp) and didn't notice any problem. > > > > I'm attaching my patch again because some recipients didn't probably > > receive it yesterday. > > This didn't apply cleanly against my -stable from today. > Attached is a cleaned version (#define RSAQ_STATUS_CTS doesn't exist in > -stable uplcom.c) for -stable which compiles for me. > Thank you. I found I can't run getty on the converter. I see some output on the remote computer but it stops pretty soon. If I issue "setty -f /dev/cuaU0 crtscts" I get some more output. It works really realiably in the other direction (running getty on real serial and connecting to it with cu through the converter). I will try to find out more. > > > > > Michal From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 16:35:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 624C716A4CE for ; Fri, 21 Jan 2005 16:35:39 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48D5643D39 for ; Fri, 21 Jan 2005 16:35:35 +0000 (GMT) (envelope-from ksatechnologies@comcast.net) Received: from 204.127.205.142 (unknown[204.127.205.160](misconfigured sender)) by comcast.net (sccrmhc13) with SMTP id <20050121163533016006sliqe>; Fri, 21 Jan 2005 16:35:33 +0000 Received: from [63.115.132.2] by 204.127.205.142; Fri, 21 Jan 2005 16:35:33 +0000 From: ksatechnologies@comcast.net To: freebsd-stable@freebsd.org Date: Fri, 21 Jan 2005 16:35:33 +0000 Message-Id: <012120051635.10041.41F12F52000C16330000273922070029539C0A070901040102080C0A9B0E9C05@comcast.net> X-Mailer: AT&T Message Center Version 1 (Dec 17 2004) X-Authenticated-Sender: a3NhdGVjaG5vbG9naWVzQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 16:35:39 -0000 I also have the same problem with the new 3ware drivers 9.1.5.2 in -STABLE but I am using the i386 platform with a Xeon 3.0Ghz processor. I have one RAID-1 array and one RAID-5 array on the 9500s controller. /var and /usr/local on the RAID-5 Following the FreeBSD instructions to build -STABLE make -j8 buildworld make buildkernel KERNCONF="mykernelconf" make installkernel KERNCONF="mykernelconf" reboot And it worked. All was fine. Then.... mergemaster -p make installworld mergemaster reboot Then I could not get to the server via SSH. Found that the console had the exactly the same symptoms describe in the thread. I rebooted and at the Daemon Logo I did a "boot kernel.old" which worked with no problem. The dmesgs are below. First, 3Ware 9.1.5.2 driver "kernel" and the second is the "kernel.old" boot. --------------/etc/make.conf------------------------------------- # -- use.perl generated deltas -- # # Created: Thu Nov 25 08:12:18 2004 # Setting to use base perl from ports: PERL_VER=5.8.5 PERL_VERSION=5.8.5 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo CPUTYPE=p4 CFLAGS= -O2 -pipe -funroll-loops -ffast-math #CFLAGS= -pipe -funroll-loops -ffast-math COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math ------------------Kernel With 3Ware 9.1.5.2-------------------- Copyright (c) 1992-2005 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 5.3-STABLE #0: Thu Jan 20 17:54:09 EST 2005 root@mail.barsproducts.com:/usr/obj/usr/src/sys/BarsMail ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1072562176 (1022 MB) avail memory = 1040035840 (991 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 em0: port 0xa000-0xa01f mem 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:11:2f:5a:7e:df em0: Speed:N/A Duplex:N/A pcib2: at device 28.0 on pci0 pci2: on pcib2 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff irq 27 at device 2.0 on pci2 twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: [GIANT-LOCKED] uhci0: port 0xd400-0xd41f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 pci3: at device 4.0 (no driver attached) em1: port 0xc400-0xc43f mem 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device 5.0 on pci3 em1: Ethernet address: 00:11:2f:5a:7e:e0 em1: Speed:N/A Duplex:N/A isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 SMP: AP CPU #1 Launched! -----------------Kernel.old pre 9.1.5.2 --------------------- Copyright (c) 1992-2004 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 5.3-STABLE #1: Mon Dec 27 10:27:38 EST 2004 root@:/usr/obj/usr/src/sys/BarsMail1 ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1072562176 (1022 MB) avail memory = 1044226048 (995 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 em0: port 0xa000-0xa01f mem 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:11:2f:5a:7e:df em0: Speed:N/A Duplex:N/A pcib2: at device 28.0 on pci0 pci2: on pcib2 3ware device driver for 9000 series storage controllers, version: 2.50.00.000 twa0: <3ware 9000 series Storage Controller> port 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff irq 27 at device 2.0 on pci2 twa0: [GIANT-LOCKED] twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 uhci0: port 0xd400-0xd41f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 pci3: at device 4.0 (no driver attached) em1: port 0xc400-0xc43f mem 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device 5.0 on pci3 em1: Ethernet address: 00:11:2f:5a:7e:e0 em1: Speed:N/A Duplex:N/A isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 da0 at twa0 bus 0 target 0 lun 0 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) da1 at twa0 bus 0 target 1 lun 0 da1: <3ware Logical Disk 01 1.00> Fixed Direct Access SCSI-0 device da1: 100.000MB/s transfers da1: 476816MB (976519168 512 byte sectors: 255H 63S/T 60785C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a em0: Link is up 10 Mbps Full Duplex em0: Link is Down em0: Link is up 1000 Mbps Full Duplex --------------------------------------------------------------------------------------------- Hope this information might help. Thanks, Kev From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 16:49:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F8C316A4CE for ; Fri, 21 Jan 2005 16:49:31 +0000 (GMT) Received: from av7-1-sn4.m-sp.skanova.net (av7-1-sn4.m-sp.skanova.net [81.228.10.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 865F943D31 for ; Fri, 21 Jan 2005 16:49:30 +0000 (GMT) (envelope-from ertr1013@student.uu.se) Received: by av7-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id BB5AD37E84; Fri, 21 Jan 2005 17:49:29 +0100 (CET) Received: from smtp4-2-sn4.m-sp.skanova.net (smtp4-2-sn4.m-sp.skanova.net [81.228.10.180]) by av7-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id ACD0637E42 for ; Fri, 21 Jan 2005 17:49:29 +0100 (CET) Received: from falcon.midgard.homeip.net (h201n1fls24o1048.bredband.comhem.se [212.181.162.201]) by smtp4-2-sn4.m-sp.skanova.net (Postfix) with SMTP id 7FC8E37E42 for ; Fri, 21 Jan 2005 17:49:29 +0100 (CET) Received: (qmail 50949 invoked by uid 1001); 21 Jan 2005 16:49:29 -0000 Date: Fri, 21 Jan 2005 17:49:29 +0100 From: Erik Trulsson To: Kevin Oberman Message-ID: <20050121164928.GA50279@falcon.midgard.homeip.net> Mail-Followup-To: Kevin Oberman , Mark Kirkwood , freebsd-stable@freebsd.org, "Jim C. Nasby" References: <41F0B4E8.9090507@paradise.net.nz> <20050121163106.B01855D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121163106.B01855D08@ptavv.es.net> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org cc: Mark Kirkwood cc: "Jim C. Nasby" Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 16:49:31 -0000 On Fri, Jan 21, 2005 at 08:31:06AM -0800, Kevin Oberman wrote: > > Date: Fri, 21 Jan 2005 20:53:12 +1300 > > From: Mark Kirkwood > > Sender: owner-freebsd-stable@freebsd.org > > > > Jim C. Nasby wrote: > > > Question one: how do I disable write caching on IDE drives? I know the > > > setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is > > > FreeBSD 4.10, btw. > > > > > In /boot/loader.conf will do it. > > > > > Also, has any thought been given to making the default 0, like it is for > > > SCSI devices? I'm honestly surprised and disappointed that the default > > > is speed over data integrity. > > I think it was trialled in 4.3 then changed for 4.4 (according to the > > handbook, the performance hit was considered to be too high) > > Having been involved in the 4.x flip-flop, the performance cost on some > systems can be HUGE! Backing up my laptop (40 GB) went from 40 minutes > to five hours when the write cache was turned off. > > On the other hand, it is a real risk, especially when combined with > softupdates. I don't see how softupdates can increase the risk. As I understand it the risks with IDE-write chaching is just as large with softupdates as without. It is just that all the safety and consistency guarantees that softupdates normally make go out of the window when write-caching is turned on. > For servers that lack solid backup power (not a 10 minute > UPS), I would probably turn it off. But for most systems it is probably > worth the risks. A 10 minute UPS should be plenty for that purpose. All that is needed to protect against the risks of write-caching is for the server to be able to make an orderly shutdown, which should not take more than a couple of minutes. (If you need constant uptime, you need better power backup, but that is a different issue.) -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 17:28:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF9816A4CE for ; Fri, 21 Jan 2005 17:28:39 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFCE43D41 for ; Fri, 21 Jan 2005 17:28:39 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Fri, 21 Jan 2005 09:28:38 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 2F80A5D08; Fri, 21 Jan 2005 09:28:37 -0800 (PST) To: Erik Trulsson In-reply-to: Your message of "Fri, 21 Jan 2005 17:49:29 +0100." <20050121164928.GA50279@falcon.midgard.homeip.net> Date: Fri, 21 Jan 2005 09:28:37 -0800 From: "Kevin Oberman" Message-Id: <20050121172837.2F80A5D08@ptavv.es.net> cc: freebsd-stable@freebsd.org cc: Mark Kirkwood cc: "Jim C. Nasby" Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 17:28:39 -0000 > Date: Fri, 21 Jan 2005 17:49:29 +0100 > From: Erik Trulsson > > On Fri, Jan 21, 2005 at 08:31:06AM -0800, Kevin Oberman wrote: > > > Date: Fri, 21 Jan 2005 20:53:12 +1300 > > > From: Mark Kirkwood > > > Sender: owner-freebsd-stable@freebsd.org > > > > > > Jim C. Nasby wrote: > > > > Question one: how do I disable write caching on IDE drives? I know the > > > > setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is > > > > FreeBSD 4.10, btw. > > > > > > > In /boot/loader.conf will do it. > > > > > > > Also, has any thought been given to making the default 0, like it is for > > > > SCSI devices? I'm honestly surprised and disappointed that the default > > > > is speed over data integrity. > > > I think it was trialled in 4.3 then changed for 4.4 (according to the > > > handbook, the performance hit was considered to be too high) > > > > Having been involved in the 4.x flip-flop, the performance cost on some > > systems can be HUGE! Backing up my laptop (40 GB) went from 40 minutes > > to five hours when the write cache was turned off. > > > > On the other hand, it is a real risk, especially when combined with > > softupdates. > > I don't see how softupdates can increase the risk. As I understand it > the risks with IDE-write chaching is just as large with softupdates as > without. It is just that all the safety and consistency guarantees > that softupdates normally make go out of the window when write-caching > is turned on. As I understand it (and I'll admit that I probably don't), softupdates makes some assumptions about the state of metadata vs. data that are not valid if the metadata is not actually written. I do know that a power outage can produce some very unpleasant softupdate data consistency errors when you re-boot the system. Whether the final result is worse than the errors when softupdates are not enabled, I can't say. > > For servers that lack solid backup power (not a 10 minute > > UPS), I would probably turn it off. But for most systems it is probably > > worth the risks. > > A 10 minute UPS should be plenty for that purpose. All that is needed > to protect against the risks of write-caching is for the server to be > able to make an orderly shutdown, which should not take more than a > couple of minutes. (If you need constant uptime, you need better power > backup, but that is a different issue.) 10 minutes (or even 1 minute) would be fine IF you have the system shutdown when the main power fails, but if the system is unattended and active and power goes out, it will simply keep going until the UPS dies and will still leave your disk in a bad state. The right answer is to run nut or other UPS monitor to shutdown the system when power fails. Or, better still, have generator backed power with about an hour of UPS to give the generator time to get up to speed and on-line. But that is still less than perfect. Generators fail, are often not tested regularly, and will eventually run out of fuel. It's always a trade-off of reliability vs. overhead and making the call as to exactly where the line should be is always open to second-guesses. I make my own calls for my local hardware and 5 hours for a backup is well over that line. You may have other opinions on the subject and should run your systems accordingly. I think a good discussion of the issue in the handbook and in tuning(7) might be a good idea, though. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 17:45:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7828916A4CE; Fri, 21 Jan 2005 17:45:53 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BF843D54; Fri, 21 Jan 2005 17:45:53 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id D69A23001109; Fri, 21 Jan 2005 18:45:51 +0100 (CET) Message-ID: <41F13FC5.4070106@uni-mainz.de> Date: Fri, 21 Jan 2005 18:45:41 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050102 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: ASUS A8N-SLI Deluxe supported by FreeBSD 5.3? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 17:45:53 -0000 Hello. Maybe this question is out of focus of this list, but maybe not. I wish to obtain a new AMD64 based system with PCIe and found the ASUS A8N-SLI/Deluxe mainboard based on NVidia NForce4-SLI chipset suitable. I would like to know whether this board or more precise, the chipset and its ATA II facilities are supported by FreeBSD 5.3-STABLE or oncoming FreeBSD 5.4-RELEASE. Furthermore I would like to equippt this system by a ATI Radeon X600 based PCIe graphics board and maybe someone is out here who can offer some bad or good experiences with this board. Thanks a lot. Oliver From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 17:52:22 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6897816A4CE for ; Fri, 21 Jan 2005 17:52:22 +0000 (GMT) Received: from stephanie.unixdaemons.com (stephanie.unixdaemons.com [67.18.111.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3BB043D4C for ; Fri, 21 Jan 2005 17:52:21 +0000 (GMT) (envelope-from bmilekic@technokratis.com) Received: from stephanie.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1])j0LHqKEQ009929; Fri, 21 Jan 2005 12:52:20 -0500 (EST) Received: (from bmilekic@localhost) by stephanie.unixdaemons.com (8.13.2/8.12.1/Submit) id j0LHqJxA009928; Fri, 21 Jan 2005 12:52:19 -0500 (EST) (envelope-from bmilekic@technokratis.com) X-Authentication-Warning: stephanie.unixdaemons.com: bmilekic set sender to bmilekic@technokratis.com using -f Date: Fri, 21 Jan 2005 12:52:19 -0500 From: Bosko Milekic To: Chris Message-ID: <20050121175219.GA9829@technokratis.com> References: <3aaaa3a0501060612502ce616@mail.gmail.com> <20050106223854.GA97444@technokratis.com> <3aaaa3a0501081243395726d2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0501081243395726d2@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: mbufs on 5.3-STABLE possible bug X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 17:52:22 -0000 Can you please give an update? -Bosko On Sat, Jan 08, 2005 at 08:43:53PM +0000, Chris wrote: > thanks I will try this out as soon as possible and report back. > > > On Thu, 6 Jan 2005 17:38:54 -0500, Bosko Milekic > wrote: > > > > Please try the attached patch. It's not exactly perfect but it might > > solve your problem. Let me know. > > > > -Bosko > > > > On Thu, Jan 06, 2005 at 02:12:33PM +0000, Chris wrote: > > > Hi > > > > > > After reading the release notes and upgrading my server's I had set > > > the following in my /boot/loader.conf. > > > > > > kern.ipc.nmbclusters="0" > > > > > > This is supposed to make the limit to unlimited as I understood from > > > the docs, but a user on one of my server's reported slow download > > > speeds he was testing with wget and fetch, so we compared with another > > > FreeBSD server (5.2.1) on the same network and sure enough there was a > > > massive difference (45mbit on the other server 5mbit on mine), I spent > > > ages checking all my tweaks and changes I made comparing between the 2 > > > server's and ended up checking my loader.conf and tried setting a > > > value and leaving it as auto, both of these changes fixed the download > > > speed issue but setting to "0" introduces the problem. > > > > > > Has anyone else noticed this? > > > > > > Chris > > > _______________________________________________ > > > 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" > > > > -- > > Bosko Milekic > > bmilekic@technokratis.com > > bmilekic@FreeBSD.org > > > > > > -- Bosko Milekic bmilekic@technokratis.com bmilekic@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 17:57:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B75E16A4CE for ; Fri, 21 Jan 2005 17:57:48 +0000 (GMT) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6D3643D4C for ; Fri, 21 Jan 2005 17:57:47 +0000 (GMT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1Cs32Z-0000ti-2a for freebsd-stable@freebsd.org; Fri, 21 Jan 2005 12:57:47 -0500 Date: Fri, 21 Jan 2005 12:57:46 -0500 From: Peter Radcliffe To: freebsd-stable@freebsd.org Message-ID: <20050121175746.GG1128@pir.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <41F13FC5.4070106@uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F13FC5.4070106@uni-mainz.de> User-Agent: Mutt/1.4.2i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Subject: Re: ASUS A8N-SLI Deluxe supported by FreeBSD 5.3? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:57:48 -0000 "O. Hartmann" probably said: > Furthermore I would like to equippt this system by a ATI Radeon X600 > based PCIe graphics board I had FreeBSD 4 on a machine with an X600 PCIe graphics card briefly. Worked ok as a text console but had no X support whatsoever. P. -- pir From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 18:17:30 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3EFD16A4CE for ; Fri, 21 Jan 2005 18:17:29 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80A7D43D46 for ; Fri, 21 Jan 2005 18:17:29 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0LIHPd4070805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 13:17:27 -0500 (EST) Message-ID: <41F1479C.90002@mac.com> Date: Fri, 21 Jan 2005 13:19:08 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Stein M. Sandbech" References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> <20050119213605.B26294@Denninger.Net> <20050120210923.GJ1168@manor.msen.com> In-Reply-To: X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 18:17:30 -0000 Stein M. Sandbech wrote: [ ... ] > I'm having problems with this disk just after startup, and it seem to me > its related to temperature. Occationally, when starting up with disk @ room > temperature I usually get a handfull of the checksum errors listed below. > If it been sitting in the car for a while and temp is down to 15C or below, > it wont start at all. Just giving a lot more of the CRC errors, and usually > a kernel panic. > > I sometimes heated the disk with a hairdryer ;-) This drive should be RMA'ed, looks like it has some major TCAL problems. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 18:56:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 572D416A4CE for ; Fri, 21 Jan 2005 18:56:25 +0000 (GMT) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B188A43D53 for ; Fri, 21 Jan 2005 18:56:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0LIuI2r015438 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 22 Jan 2005 05:56:19 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0LIuIxP072649; Sat, 22 Jan 2005 05:56:18 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0LIuIpB072648; Sat, 22 Jan 2005 05:56:18 +1100 (EST) (envelope-from pjeremy) Date: Sat, 22 Jan 2005 05:56:18 +1100 From: Peter Jeremy To: Kevin Oberman Message-ID: <20050121185618.GD68808@cirb503493.alcatel.com.au> References: <20050121164928.GA50279@falcon.midgard.homeip.net> <20050121172837.2F80A5D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121172837.2F80A5D08@ptavv.es.net> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 18:56:25 -0000 On Fri, 2005-Jan-21 09:28:37 -0800, Kevin Oberman wrote: >10 minutes (or even 1 minute) would be fine IF you have the system >shutdown when the main power fails, but if the system is unattended and >active and power goes out, it will simply keep going until the UPS dies >and will still leave your disk in a bad state. > >The right answer is to run nut or other UPS monitor to shutdown the >system when power fails. Agreed. ACPI helps enormously here. When implementing this, remember to ensure that things recover when mains power is restored in the interval between when the UPS says "I'm about to die, shutdown now" and when it actually dies. > Or, better still, have generator backed power >with about an hour of UPS to give the generator time to get up to speed >and on-line. Huh? Most generators take a lot less than an hour to get going. 15-30 seconds would be a typical value. If your backup generator takes an hour to start, it is probably overdue for servicing :-). > But that is still less than perfect. Generators fail, are >often not tested regularly, and will eventually run out of fuel. If this is important to you then it needs to be covered as part of your business continuity or disaster recovery plan. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 19:09:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502B516A4CE for ; Fri, 21 Jan 2005 19:09:15 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C77543D3F for ; Fri, 21 Jan 2005 19:09:15 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j0LJ91MC052960; Fri, 21 Jan 2005 11:09:05 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200501211909.j0LJ91MC052960@gw.catspoiler.org> Date: Fri, 21 Jan 2005 11:09:01 -0800 (PST) From: Don Lewis To: ertr1013@student.uu.se In-Reply-To: <20050121164928.GA50279@falcon.midgard.homeip.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: decibel@decibel.org cc: freebsd-stable@FreeBSD.org cc: markir@paradise.net.nz Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 19:09:15 -0000 On 21 Jan, Erik Trulsson wrote: > On Fri, Jan 21, 2005 at 08:31:06AM -0800, Kevin Oberman wrote: >> For servers that lack solid backup power (not a 10 minute >> UPS), I would probably turn it off. But for most systems it is probably >> worth the risks. > > A 10 minute UPS should be plenty for that purpose. All that is needed > to protect against the risks of write-caching is for the server to be > able to make an orderly shutdown, which should not take more than a > couple of minutes. (If you need constant uptime, you need better power > backup, but that is a different issue.) I guess that you haven't had as many UPS failures as I have had. The usual problem is sudden battery and unexpected battery death which brings the UPS runtime close to zero. The UPSes definitely help with the short hits to the power, but for anything important I pay the outrageously high premium for SCSI disks and turn off write caching. At least SCSI has working tagged command queuing that when used with softupdates avoids the performance hit caused by turning off write caching, at least for most workloads. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 19:22:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E293416A4CF for ; Fri, 21 Jan 2005 19:22:58 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C299A43D48 for ; Fri, 21 Jan 2005 19:22:57 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IAOLUD02.LQF; Fri, 21 Jan 2005 11:23:01 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005012111260412426 ; Fri, 21 Jan 2005 11:26:04 -0800 From: "Vinod Kashyap" To: ksatechnologies@comcast.net, freebsd-stable@freebsd.org Date: Fri, 21 Jan 2005 11:22:48 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=-------2ae260ef2ae260ef Message-ID: Subject: RE: twa breakage onAMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 19:22:59 -0000 This is a multi-part message in MIME format ---------2ae260ef2ae260ef Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Let me know if the attached patch works for you too. > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of > ksatechnologies@comcast.net > Sent: Friday, January 21, 2005 8:36 AM > To: freebsd-stable@freebsd.org > Subject: twa breakage on > AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit > = > = > I also have the same problem with the new 3ware drivers = > 9.1.5.2 in -STABLE but I am using the i386 platform with a = > Xeon 3.0Ghz processor. > I have one RAID-1 array and one RAID-5 array on the 9500s controller. > /var and /usr/local on the RAID-5 > = > Following the FreeBSD instructions to build -STABLE > = > make -j8 buildworld > make buildkernel KERNCONF=3D"mykernelconf" > make installkernel KERNCONF=3D"mykernelconf" > reboot > = > And it worked. All was fine. Then.... > = > mergemaster -p > make installworld > mergemaster > reboot > = > Then I could not get to the server via SSH. Found that the = > console had the exactly the same symptoms describe in the = > thread. I rebooted and at the Daemon Logo I did a "boot = > kernel.old" which worked with no problem. The dmesgs are = > below. First, 3Ware 9.1.5.2 driver "kernel" and the second = > is the "kernel.old" boot. > = > --------------/etc/make.conf------------------------------------- > # -- use.perl generated deltas -- # > # Created: Thu Nov 25 08:12:18 2004 > # Setting to use base perl from ports: > PERL_VER=3D5.8.5 > PERL_VERSION=3D5.8.5 > PERL_ARCH=3Dmach > NOPERL=3Dyo > NO_PERL=3Dyo > NO_PERL_WRAPPER=3Dyo > CPUTYPE=3Dp4 > CFLAGS=3D -O2 -pipe -funroll-loops -ffast-math > #CFLAGS=3D -pipe -funroll-loops -ffast-math > COPTFLAGS=3D -O2 -pipe -funroll-loops -ffast-math > = > = > ------------------Kernel With 3Ware 9.1.5.2-------------------- > Copyright (c) 1992-2005 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 5.3-STABLE #0: Thu Jan 20 17:54:09 EST 2005 > root@mail.barsproducts.com:/usr/obj/usr/src/sys/BarsMail > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > = > Features=3D0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory =3D 1072562176 (1022 MB) > avail memory =3D 1040035840 (991 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > em0: = > port 0xa000-0xa01f mem = > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device = > 1.0 on pci1 > em0: Ethernet address: 00:11:2f:5a:7e:df > em0: Speed:N/A Duplex:N/A > pcib2: at device 28.0 on pci0 > pci2: on pcib2 > 3ware device driver for 9000 series storage controllers, = > version: 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port = > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff = > irq 27 at device 2.0 on pci2 > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > twa0: [GIANT-LOCKED] > uhci0: port 0xd400-0xd41f irq = > 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq = > 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.5 = > (no driver attached) > pci0: at device 29.7 (no driver attached) > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > pci3: at device 4.0 (no driver attached) > em1: = > port 0xc400-0xc43f mem = > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device = > 5.0 on pci3 > em1: Ethernet address: 00:11:2f:5a:7e:e0 > em1: Speed:N/A Duplex:N/A > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port = > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port = > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem = > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem = > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: CDROM at ata0-master UDMA33 > SMP: AP CPU #1 Launched! > = > -----------------Kernel.old pre 9.1.5.2 --------------------- > Copyright (c) 1992-2004 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 5.3-STABLE #1: Mon Dec 27 10:27:38 EST 2004 > root@:/usr/obj/usr/src/sys/BarsMail1 > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > = > Features=3D0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory =3D 1072562176 (1022 MB) > avail memory =3D 1044226048 (995 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > em0: = > port 0xa000-0xa01f mem = > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device = > 1.0 on pci1 > em0: Ethernet address: 00:11:2f:5a:7e:df > em0: Speed:N/A Duplex:N/A > pcib2: at device 28.0 on pci0 > pci2: on pcib2 > 3ware device driver for 9000 series storage controllers, = > version: 2.50.00.000 > twa0: <3ware 9000 series Storage Controller> port = > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff = > irq 27 at device 2.0 on pci2 > twa0: [GIANT-LOCKED] > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > uhci0: port 0xd400-0xd41f irq = > 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq = > 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.5 = > (no driver attached) > pci0: at device 29.7 (no driver attached) > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > pci3: at device 4.0 (no driver attached) > em1: = > port 0xc400-0xc43f mem = > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device = > 5.0 on pci3 > em1: Ethernet address: 00:11:2f:5a:7e:e0 > em1: Speed:N/A Duplex:N/A > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port = > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port = > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem = > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem = > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: CDROM at ata0-master UDMA33 > da0 at twa0 bus 0 target 0 lun 0 > da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device > da0: 100.000MB/s transfers > da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) > da1 at twa0 bus 0 target 1 lun 0 > da1: <3ware Logical Disk 01 1.00> Fixed Direct Access SCSI-0 device > da1: 100.000MB/s transfers > da1: 476816MB (976519168 512 byte sectors: 255H 63S/T 60785C) > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > em0: Link is up 10 Mbps Full Duplex > em0: Link is Down > em0: Link is up 1000 Mbps Full Duplex > -------------------------------------------------------------- > ------------------------------- > = > Hope this information might help. > = > Thanks, > = > Kev > _______________________________________________ > 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" > ---------2ae260ef2ae260ef Content-Type: application/octet-stream; name="twa_patch3.diff" Content-Disposition: attachment; filename="twa_patch3.diff" Content-Transfer-Encoding: base64 SW5kZXg6IHR3YV9jYW0uYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3Ny Yy9zeXMvZGV2L3R3YS90d2FfY2FtLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMy4yLjEK ZGlmZiAtdSAtcjEuMy4yLjEgdHdhX2NhbS5jCi0tLSB0d2FfY2FtLmMJMTEgSmFuIDIwMDUg MDM6MDA6NDggLTAwMDAJMS4zLjIuMQorKysgdHdhX2NhbS5jCTIwIEphbiAyMDA1IDAzOjI2 OjM1IC0wMDAwCkBAIC00MDksOSArNDA5LDkgQEAKIAkJdHdhX2RiZ19kcHJpbnQoMywgc2Ms ICJYUFRfUEFUSF9JTlEgcmVxdWVzdCIpOwogCiAJCXBhdGhfaW5xLT52ZXJzaW9uX251bSA9 IDE7Ci0JCXBhdGhfaW5xLT5oYmFfaW5xdWlyeSA9IFBJX1dJREVfMTY7CisJCXBhdGhfaW5x LT5oYmFfaW5xdWlyeSA9IDA7CiAJCXBhdGhfaW5xLT50YXJnZXRfc3BydCA9IDA7Ci0JCXBh dGhfaW5xLT5oYmFfbWlzYyB8PSBQSU1fTk9CVVNSRVNFVDsKKwkJcGF0aF9pbnEtPmhiYV9t aXNjID0gMDsKIAkJcGF0aF9pbnEtPmhiYV9lbmdfY250ID0gMDsKIAkJcGF0aF9pbnEtPm1h eF90YXJnZXQgPSBUV0FfTUFYX1VOSVRTOwogCQlwYXRoX2lucS0+bWF4X2x1biA9IDA7Cklu ZGV4OiB0d2FfZnJlZWJzZC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMv c3JjL3N5cy9kZXYvdHdhL3R3YV9mcmVlYnNkLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEu Ny4yLjIKZGlmZiAtdSAtcjEuNy4yLjIgdHdhX2ZyZWVic2QuYwotLS0gdHdhX2ZyZWVic2Qu YwkxMSBKYW4gMjAwNSAwMzowMDo0OCAtMDAwMAkxLjcuMi4yCisrKyB0d2FfZnJlZWJzZC5j CTIwIEphbiAyMDA1IDAzOjI2OjM1IC0wMDAwCkBAIC0yNjEsMTUgKzI2MSw2IEBACiAJc2Mt PnR3YV9idXNfdGFnID0gcm1hbl9nZXRfYnVzdGFnKHNjLT50d2FfaW9fcmVzKTsKIAlzYy0+ dHdhX2J1c19oYW5kbGUgPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnR3YV9pb19yZXMpOwog Ci0JLyogSW5pdGlhbGl6ZSB0aGUgZHJpdmVyIGZvciB0aGlzIGNvbnRyb2xsZXIuICovCi0J aWYgKChlcnJvciA9IHR3YV9zZXR1cChzYykpKSB7Ci0JCXR3YV9mcmVlKHNjKTsKLQkJcmV0 dXJuKGVycm9yKTsKLQl9Ci0KLQkvKiBQcmludCBzb21lIGluZm9ybWF0aW9uIGFib3V0IHRo ZSBjb250cm9sbGVyIGFuZCBjb25maWd1cmF0aW9uLiAqLwotCXR3YV9kZXNjcmliZV9jb250 cm9sbGVyKHNjKTsKLQogCS8qIEFsbG9jYXRlIGFuZCBjb25uZWN0IG91ciBpbnRlcnJ1cHQu ICovCiAJcmVzX2lkID0gMDsKIAlpZiAoKHNjLT50d2FfaXJxX3JlcyA9IGJ1c19hbGxvY19y ZXNvdXJjZShzYy0+dHdhX2J1c19kZXYsIFNZU19SRVNfSVJRLApAQCAtMjg2LDYgKzI3Nywx NSBAQAogCQlyZXR1cm4oRU5YSU8pOwogCX0KIAorCS8qIEluaXRpYWxpemUgdGhlIGRyaXZl ciBmb3IgdGhpcyBjb250cm9sbGVyLiAqLworCWlmICgoZXJyb3IgPSB0d2Ffc2V0dXAoc2Mp KSkgeworCQl0d2FfZnJlZShzYyk7CisJCXJldHVybihlcnJvcik7CisJfQorCisJLyogUHJp bnQgc29tZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgY29udHJvbGxlciBhbmQgY29uZmlndXJh dGlvbi4gKi8KKwl0d2FfZGVzY3JpYmVfY29udHJvbGxlcihzYyk7CisKIAkvKiBDcmVhdGUg dGhlIGNvbnRyb2wgZGV2aWNlLiAqLwogCXNjLT50d2FfY3RybF9kZXYgPSBtYWtlX2Rldigm dHdhX2NkZXZzdywgZGV2aWNlX2dldF91bml0KHNjLT50d2FfYnVzX2RldiksCiAJCQkJCVVJ RF9ST09ULCBHSURfT1BFUkFUT1IsIFNfSVJVU1IgfCBTX0lXVVNSLApAQCAtNTQzLDYgKzU0 Myw3IEBACiB7CiAJc3RydWN0IHR3YV9yZXF1ZXN0CSp0cjsKIAlpbnQJCQlpOworCWludAkJ CWVycm9yOwogCiAJaWYgKChzYy0+dHdhX3JlcV9idWYgPSBtYWxsb2MobnVtX3JlcXMgKiBz aXplb2Yoc3RydWN0IHR3YV9yZXF1ZXN0KSwKIAkJCQkJVFdBX01BTExPQ19DTEFTUywgTV9O T1dBSVQpKSA9PSBOVUxMKQpAQCAtNTk1LDEwICs1OTYsMTIgQEAKIAkJcmV0dXJuKEVOT01F TSk7CiAJfQogCi0JYnVzX2RtYW1hcF9sb2FkKHNjLT50d2FfY21kX3RhZywgc2MtPnR3YV9j bWRfbWFwLAorCWlmICgoZXJyb3IgPSBidXNfZG1hbWFwX2xvYWQoc2MtPnR3YV9jbWRfdGFn LCBzYy0+dHdhX2NtZF9tYXAsCiAJCQkJc2MtPnR3YV9jbWRfcGt0X2J1ZiwKIAkJCQludW1f cmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX2NvbW1hbmRfcGFja2V0KSwKLQkJCQl0d2Ffc2V0 dXBfcmVxdWVzdF9kbWFtYXAsIHNjLCAwKTsKKwkJCQl0d2Ffc2V0dXBfcmVxdWVzdF9kbWFt YXAsIHNjLCBCVVNfRE1BX05PV0FJVCkpKSB7CisJCXR3YV9wcmludGYoc2MsICJidXNfZG1h bWFwX2xvYWQgcmV0dXJuZWQgJWRcbiIsIGVycm9yKTsKKwl9CiAJYnplcm8oc2MtPnR3YV9y ZXFfYnVmLCBudW1fcmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX3JlcXVlc3QpKTsKIAliemVy byhzYy0+dHdhX2NtZF9wa3RfYnVmLAogCQkJbnVtX3JlcXMgKiBzaXplb2Yoc3RydWN0IHR3 YV9jb21tYW5kX3BhY2tldCkpOwpAQCAtNzcwLDYgKzc3Myw4IEBACiAJc3RydWN0IHR3YV9z b2Z0Ywkqc2MgPSAoc3RydWN0IHR3YV9zb2Z0YyAqKWFyZzsKIAogCXR3YV9kYmdfZHByaW50 X2VudGVyKDEwLCBzYyk7CisJdHdhX2RiZ19kcHJpbnQoMywgc2MsICJlcnJvciA9ICVkLCBz ZWdzWzBdLmFkZHIgPSAlbHgsIGxlbiA9ICVseCIsCisJCWVycm9yLCBzZWdzWzBdLmRzX2Fk ZHIsIHNlZ3NbMF0uZHNfbGVuKTsKIAogCXNjLT50d2FfY21kX3BrdF9waHlzID0gc2Vnc1sw XS5kc19hZGRyOwogfQo= ---------2ae260ef2ae260ef-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 20:20:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2F8016A57E for ; Fri, 21 Jan 2005 20:20:15 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0387443D2D for ; Fri, 21 Jan 2005 20:20:13 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IAOOHT00.LMA; Fri, 21 Jan 2005 12:20:17 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005012112232713928 ; Fri, 21 Jan 2005 12:23:27 -0800 From: "Vinod Kashyap" To: ksatechnologies@comcast.net, freebsd-stable@freebsd.org Date: Fri, 21 Jan 2005 12:20:04 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: Subject: RE: twa breakageonAMD64with9.1.5.23wareversionand2005-01-1103:00:49UTCRELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 20:20:15 -0000 Can anyone please verify if they see similar problems on i386 RELENG_4/4.11RC3? I have tested that 4.11RC3 works fine, but just want to make sure... > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Vinod Kashyap > Sent: Friday, January 21, 2005 11:23 AM > To: ksatechnologies@comcast.net; freebsd-stable@freebsd.org > Subject: RE: twa > breakageonAMD64with9.1.5.23wareversionand2005-01-1103:00:49UTCRELENG_5 > commit > = > = > = > Let me know if the attached patch works for you too. > = > = > > -----Original Message----- > > From: owner-freebsd-stable@freebsd.org > > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of > > ksatechnologies@comcast.net > > Sent: Friday, January 21, 2005 8:36 AM > > To: freebsd-stable@freebsd.org > > Subject: twa breakage on > > AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit > > = > > = > > I also have the same problem with the new 3ware drivers = > > 9.1.5.2 in -STABLE but I am using the i386 platform with a = > > Xeon 3.0Ghz processor. > > I have one RAID-1 array and one RAID-5 array on the 9500s = > controller. > > /var and /usr/local on the RAID-5 > > = > > Following the FreeBSD instructions to build -STABLE > > = > > make -j8 buildworld > > make buildkernel KERNCONF=3D"mykernelconf" > > make installkernel KERNCONF=3D"mykernelconf" > > reboot > > = > > And it worked. All was fine. Then.... > > = > > mergemaster -p > > make installworld > > mergemaster > > reboot > > = > > Then I could not get to the server via SSH. Found that the = > > console had the exactly the same symptoms describe in the = > > thread. I rebooted and at the Daemon Logo I did a "boot = > > kernel.old" which worked with no problem. The dmesgs are = > > below. First, 3Ware 9.1.5.2 driver "kernel" and the second = > > is the "kernel.old" boot. > > = > > --------------/etc/make.conf------------------------------------- > > # -- use.perl generated deltas -- # > > # Created: Thu Nov 25 08:12:18 2004 > > # Setting to use base perl from ports: > > PERL_VER=3D5.8.5 > > PERL_VERSION=3D5.8.5 > > PERL_ARCH=3Dmach > > NOPERL=3Dyo > > NO_PERL=3Dyo > > NO_PERL_WRAPPER=3Dyo > > CPUTYPE=3Dp4 > > CFLAGS=3D -O2 -pipe -funroll-loops -ffast-math > > #CFLAGS=3D -pipe -funroll-loops -ffast-math > > COPTFLAGS=3D -O2 -pipe -funroll-loops -ffast-math > > = > > = > > ------------------Kernel With 3Ware 9.1.5.2-------------------- > > Copyright (c) 1992-2005 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 5.3-STABLE #0: Thu Jan 20 17:54:09 EST 2005 > > root@mail.barsproducts.com:/usr/obj/usr/src/sys/BarsMail > > ACPI APIC Table: > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > > = > > Features=3D0xbfebfbff P,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS > E2,SS,HTT,TM,PBE> > > Hyperthreading: 2 logical CPUs > > real memory =3D 1072562176 (1022 MB) > > avail memory =3D 1040035840 (991 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > ioapic0: Changing APIC ID to 4 > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 24-47 on motherboard > > npx0: [FAST] > > npx0: on motherboard > > npx0: INT 16 interface > > acpi0: on motherboard > > acpi0: Power Button (fixed) > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > > cpu0: on acpi0 > > cpu1: on acpi0 > > acpi_button0: on acpi0 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib1: at device 3.0 on pci0 > > pci1: on pcib1 > > em0: = > > port 0xa000-0xa01f mem = > > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device = > > 1.0 on pci1 > > em0: Ethernet address: 00:11:2f:5a:7e:df > > em0: Speed:N/A Duplex:N/A > > pcib2: at device 28.0 on pci0 > > pci2: on pcib2 > > 3ware device driver for 9000 series storage controllers, = > > version: 2.50.02.011 > > twa0: <3ware 9000 series Storage Controller> port = > > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff = > > irq 27 at device 2.0 on pci2 > > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > > twa0: [GIANT-LOCKED] > > uhci0: port 0xd400-0xd41f irq = > > 16 at device 29.0 on pci0 > > uhci0: [GIANT-LOCKED] > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: port 0xd000-0xd01f irq = > > 19 at device 29.1 on pci0 > > uhci1: [GIANT-LOCKED] > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub1: 2 ports with 2 removable, self powered > > pci0: at device 29.4 (no driver attached) > > pci0: at device 29.5 = > > (no driver attached) > > pci0: at device 29.7 (no driver attached) > > pcib3: at device 30.0 on pci0 > > pci3: on pcib3 > > pci3: at device 4.0 (no driver attached) > > em1: = > > port 0xc400-0xc43f mem = > > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device = > > 5.0 on pci3 > > em1: Ethernet address: 00:11:2f:5a:7e:e0 > > em1: Speed:N/A Duplex:N/A > > isab0: at device 31.0 on pci0 > > isa0: on isab0 > > atapci0: port = > > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > > 31.1 on pci0 > > ata0: channel #0 on atapci0 > > ata1: channel #1 on atapci0 > > pci0: at device 31.3 (no driver attached) > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > > drq 2 on acpi0 > > fdc0: [FAST] > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > > flags 0x10 on acpi0 > > sio0: type 16550A > > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > > sio1: type 16550A > > ppc0: port = > > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/9 bytes threshold > > ppbus0: on ppc0 > > lpt0: on ppbus0 > > lpt0: Interrupt-driven port > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > > atkbd0: irq 1 on atkbdc0 > > kbd0 at atkbd0 > > atkbd0: [GIANT-LOCKED] > > psm0: irq 12 on atkbdc0 > > psm0: [GIANT-LOCKED] > > psm0: model IntelliMouse Explorer, device ID 4 > > orm0: at iomem = > > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > > pmtimer0 on isa0 > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=3D0x300> > > vga0: at port 0x3c0-0x3df iomem = > > 0xa0000-0xbffff on isa0 > > Timecounters tick every 1.000 msec > > acd0: CDROM at ata0-master UDMA33 > > SMP: AP CPU #1 Launched! > > = > > -----------------Kernel.old pre 9.1.5.2 --------------------- > > Copyright (c) 1992-2004 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 5.3-STABLE #1: Mon Dec 27 10:27:38 EST 2004 > > root@:/usr/obj/usr/src/sys/BarsMail1 > > ACPI APIC Table: > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > > = > > Features=3D0xbfebfbff P,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS > E2,SS,HTT,TM,PBE> > > Hyperthreading: 2 logical CPUs > > real memory =3D 1072562176 (1022 MB) > > avail memory =3D 1044226048 (995 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > ioapic0: Changing APIC ID to 4 > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 24-47 on motherboard > > npx0: [FAST] > > npx0: on motherboard > > npx0: INT 16 interface > > acpi0: on motherboard > > acpi0: Power Button (fixed) > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > > cpu0: on acpi0 > > cpu1: on acpi0 > > acpi_button0: on acpi0 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib1: at device 3.0 on pci0 > > pci1: on pcib1 > > em0: = > > port 0xa000-0xa01f mem = > > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device = > > 1.0 on pci1 > > em0: Ethernet address: 00:11:2f:5a:7e:df > > em0: Speed:N/A Duplex:N/A > > pcib2: at device 28.0 on pci0 > > pci2: on pcib2 > > 3ware device driver for 9000 series storage controllers, = > > version: 2.50.00.000 > > twa0: <3ware 9000 series Storage Controller> port = > > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff = > > irq 27 at device 2.0 on pci2 > > twa0: [GIANT-LOCKED] > > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > > uhci0: port 0xd400-0xd41f irq = > > 16 at device 29.0 on pci0 > > uhci0: [GIANT-LOCKED] > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: port 0xd000-0xd01f irq = > > 19 at device 29.1 on pci0 > > uhci1: [GIANT-LOCKED] > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub1: 2 ports with 2 removable, self powered > > pci0: at device 29.4 (no driver attached) > > pci0: at device 29.5 = > > (no driver attached) > > pci0: at device 29.7 (no driver attached) > > pcib3: at device 30.0 on pci0 > > pci3: on pcib3 > > pci3: at device 4.0 (no driver attached) > > em1: = > > port 0xc400-0xc43f mem = > > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device = > > 5.0 on pci3 > > em1: Ethernet address: 00:11:2f:5a:7e:e0 > > em1: Speed:N/A Duplex:N/A > > isab0: at device 31.0 on pci0 > > isa0: on isab0 > > atapci0: port = > > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > > 31.1 on pci0 > > ata0: channel #0 on atapci0 > > ata1: channel #1 on atapci0 > > pci0: at device 31.3 (no driver attached) > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > > drq 2 on acpi0 > > fdc0: [FAST] > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > > flags 0x10 on acpi0 > > sio0: type 16550A > > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > > sio1: type 16550A > > ppc0: port = > > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/9 bytes threshold > > ppbus0: on ppc0 > > lpt0: on ppbus0 > > lpt0: Interrupt-driven port > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > > atkbd0: irq 1 on atkbdc0 > > kbd0 at atkbd0 > > atkbd0: [GIANT-LOCKED] > > psm0: irq 12 on atkbdc0 > > psm0: [GIANT-LOCKED] > > psm0: model IntelliMouse Explorer, device ID 4 > > orm0: at iomem = > > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > > pmtimer0 on isa0 > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=3D0x300> > > vga0: at port 0x3c0-0x3df iomem = > > 0xa0000-0xbffff on isa0 > > Timecounters tick every 1.000 msec > > acd0: CDROM at ata0-master UDMA33 > > da0 at twa0 bus 0 target 0 lun 0 > > da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device > > da0: 100.000MB/s transfers > > da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) > > da1 at twa0 bus 0 target 1 lun 0 > > da1: <3ware Logical Disk 01 1.00> Fixed Direct Access SCSI-0 device > > da1: 100.000MB/s transfers > > da1: 476816MB (976519168 512 byte sectors: 255H 63S/T 60785C) > > SMP: AP CPU #1 Launched! > > Mounting root from ufs:/dev/da0s1a > > em0: Link is up 10 Mbps Full Duplex > > em0: Link is Down > > em0: Link is up 1000 Mbps Full Duplex > > -------------------------------------------------------------- > > ------------------------------- > > = > > Hope this information might help. > > = > > Thanks, > > = > > Kev > > _______________________________________________ > > 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 Jan 21 20:34:52 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F8A516A4CE for ; Fri, 21 Jan 2005 20:34:52 +0000 (GMT) Received: from mail.tbd.ru (mail.tbd.ru [217.17.178.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D52A43D39 for ; Fri, 21 Jan 2005 20:34:49 +0000 (GMT) (envelope-from andreyns@tbd.ru) Received: from mail.tbd.ru (root@localhost) by mail.tbd.ru (8.12.9/8.12.3) with SMTP id j0LKYrKc097896 for ; Sat, 22 Jan 2005 01:34:53 +0500 (YEKT) (envelope-from andreyns@tbd.ru) Received: from Sc114.tbd.sld (Sc114.tbd.sld [192.168.15.114]) by mail.tbd.ru (8.12.9/8.12.3) with ESMTP id j0LKYqC1097891 for ; Sat, 22 Jan 2005 01:34:53 +0500 (YEKT) (envelope-from andreyns@tbd.ru) Date: Sat, 22 Jan 2005 01:32:58 +0500 From: Sukharew Andrew Nikolaevich X-Mailer: The Bat! (v3.0) Professional Organization: TBD X-Priority: 3 (Normal) Message-ID: <3910620926.20050122013258@tbd.ru> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Subject: freeBSD 5.3 Release to FreeBSD 5 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sukharew Andrew Nikolaevich List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 20:34:52 -0000 Hi! Help me, please! Sources upgrated 2 hours ago ! this is my sup-file *default host=cvsup2.ru.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5 delete use-rel-suffix compres src-all cd /usr/src make buildworld Before this... ** edit: HAVE_TCGETATTR 1 ** edit: HAVE_TERMIOS_H 1 ** edit: HAVE_TERMIO_H 0 ** edit: BROKEN_LINKER 0 mv -f term.h.new term.h cc -o make_keys -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c /usr/obj/usr/src/i386/usr/bin/ld: cannot find -lc *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What's wrong with that? PS Somebody speaking on Russian Language ??? If "YES" please write on Russian Thanks a lot! -- Ñ óâàæåíèåì, Ñóõàðåâ Àíäðåé Íèêîëàåâè÷ mailto: andreyns@tbd.ru From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 20:43:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D05B316A4CE for ; Fri, 21 Jan 2005 20:43:11 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50A9443D1D for ; Fri, 21 Jan 2005 20:43:11 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so115657rne for ; Fri, 21 Jan 2005 12:43:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=K+dbipe5rvVFZmoOX/CgKGxlgs4CqJB5rv/SfXgKk7Hwmb5mbG3XzXXzdgWxSx91Z/uLqsIeiGSS1n8uIKUrH5uJKuXqh0BvdpJGVHQNsjzgx54N9mjOqJyb0xHat74dFBtpiOX3Hc7qwA6vJkVQN53F6pQCou94NHQ3H7WCCj8= Received: by 10.38.149.2 with SMTP id w2mr319211rnd; Fri, 21 Jan 2005 12:43:10 -0800 (PST) Received: by 10.39.1.45 with HTTP; Fri, 21 Jan 2005 12:43:10 -0800 (PST) Message-ID: <3aaaa3a050121124314b6d041@mail.gmail.com> Date: Fri, 21 Jan 2005 20:43:10 +0000 From: Chris To: Bosko Milekic In-Reply-To: <20050121175219.GA9829@technokratis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3aaaa3a0501060612502ce616@mail.gmail.com> <20050106223854.GA97444@technokratis.com> <3aaaa3a0501081243395726d2@mail.gmail.com> <20050121175219.GA9829@technokratis.com> cc: freebsd-stable@freebsd.org Subject: Re: mbufs on 5.3-STABLE possible bug X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 20:43:11 -0000 I apologise I have yet to test the patch, but will try and do so as soon as possible by the end of the weekend. Chris On Fri, 21 Jan 2005 12:52:19 -0500, Bosko Milekic wrote: > > Can you please give an update? > > -Bosko > > On Sat, Jan 08, 2005 at 08:43:53PM +0000, Chris wrote: > > thanks I will try this out as soon as possible and report back. > > > > > > On Thu, 6 Jan 2005 17:38:54 -0500, Bosko Milekic > > wrote: > > > > > > Please try the attached patch. It's not exactly perfect but it might > > > solve your problem. Let me know. > > > > > > -Bosko > > > > > > On Thu, Jan 06, 2005 at 02:12:33PM +0000, Chris wrote: > > > > Hi > > > > > > > > After reading the release notes and upgrading my server's I had set > > > > the following in my /boot/loader.conf. > > > > > > > > kern.ipc.nmbclusters="0" > > > > > > > > This is supposed to make the limit to unlimited as I understood from > > > > the docs, but a user on one of my server's reported slow download > > > > speeds he was testing with wget and fetch, so we compared with another > > > > FreeBSD server (5.2.1) on the same network and sure enough there was a > > > > massive difference (45mbit on the other server 5mbit on mine), I spent > > > > ages checking all my tweaks and changes I made comparing between the 2 > > > > server's and ended up checking my loader.conf and tried setting a > > > > value and leaving it as auto, both of these changes fixed the download > > > > speed issue but setting to "0" introduces the problem. > > > > > > > > Has anyone else noticed this? > > > > > > > > Chris > > > > _______________________________________________ > > > > 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" > > > > > > -- > > > Bosko Milekic > > > bmilekic@technokratis.com > > > bmilekic@FreeBSD.org > > > > > > > > > > > -- > Bosko Milekic > bmilekic@technokratis.com > bmilekic@FreeBSD.org > From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 21:54:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8FC516A4CE for ; Fri, 21 Jan 2005 21:54:15 +0000 (GMT) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A6AD43D2D for ; Fri, 21 Jan 2005 21:54:15 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.1/8.13.1) with ESMTP id j0LLsDvx053445 for ; Fri, 21 Jan 2005 15:54:13 -0600 (CST) (envelope-from sean-freebsd@farley.org) Received: from localhost (localhost [127.0.0.1]) by thor.farley.org (8.13.1/8.13.1) with ESMTP id j0LLsH9T001387 for ; Fri, 21 Jan 2005 15:54:17 -0600 (CST) (envelope-from sean-freebsd@farley.org) Date: Fri, 21 Jan 2005 15:54:17 -0600 (CST) From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= To: freebsd-stable@freebsd.org Message-ID: <20050121154515.T1306@thor.farley.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-202172895-1106344457=:1378" Subject: initiate_write_inodeblock_ufs2() panic in 5-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 21:54:15 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-202172895-1106344457=:1378 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE This is a re-request for help on an occasional panic I have been getting on a 5-STABLE system. The PR URL: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/75368 Currently, the system is not being used. It will be used to replace my 4-STABLE system once I get the panics to stop. This is the perfect time for me to test patches on it. *hint, hint, nudge, nudge* :) Thank you. Se=E1n --=20 sean-freebsd@farley.org --0-202172895-1106344457=:1378-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 22:33:12 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC7616A4CE; Fri, 21 Jan 2005 22:33:12 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D3743D49; Fri, 21 Jan 2005 22:33:11 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id j0LMX8TA012526; Fri, 21 Jan 2005 17:33:11 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0LMX8Gk012525; Fri, 21 Jan 2005 17:33:08 -0500 (EST) (envelope-from wayne) Date: Fri, 21 Jan 2005 17:33:08 -0500 From: "Michael R. Wayne" To: freebsd stable , freebsd-amd64@freebsd.org Message-ID: <20050121223308.GN1168@manor.msen.com> Mail-Followup-To: freebsd stable , freebsd-amd64@freebsd.org References: <41EFB111.8010906@michaelmeltzer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: twa breakage on AMD64 with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 22:33:12 -0000 Hmm, this might be my problem as well. I'm running -STABLE from November: FreeBSD 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 but when I build a current kernel, I can't even boot! At this point I am reluctant to upgrade anything until the problem is determined - breaking production servers isn't a good plan. >From my (working) dmesg: 3ware device driver for 9000 series storage controllers, version: 2.50.00.000 twa0: <3ware 9000 series Storage Controller> port 0x3000-0x30ff mem 0xfd800000-0xfdffffff,0xfd020000-0xfd0200ff irq 26 at device 2.0 on pci2 twa0: [GIANT-LOCKED] twa0: 4 ports, Firmware FE9X 2.04.00.003, BIOS BE9X 2.03.01.047 The box failed with: Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 23:18:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1868216A4CE for ; Fri, 21 Jan 2005 23:18:04 +0000 (GMT) Received: from eskimo.tundraware.com (eskimo.tundraware.com [64.2.229.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C04543D31 for ; Fri, 21 Jan 2005 23:18:01 +0000 (GMT) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by eskimo.tundraware.com (8.13.1/8.13.1) with ESMTP id j0LNHvNw044703 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Jan 2005 17:17:58 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <41F18DA5.2090808@tundraware.com> Date: Fri, 21 Jan 2005 17:17:57 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41ED98E9.10401@tundraware.com> In-Reply-To: <41ED98E9.10401@tundraware.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner: Found to be clean X-MailScanner-From: tundra@tundraware.com Subject: Re: Possible Problem w/4.10-stable And SMBFS? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: tundra@tundraware.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:18:04 -0000 Ronald Klop wrote: | | Do you have any statistics about memory consumption/swapping? | top/vmstat/netstat -m | What is the cpu usage? | What is the number of open files in your system? I'll focus on machine 'xyz' for now since its the one I care most about: Dell PowerEdge 1750 w/Dual 3Ghz Xeons and 3G of memory. This thing idles most of the time as a mailserver for less than 150 users (both UW-Imap and SquirrelMail/Apache). CPU is typically less than 5% busy and top shows most of the memory inactive or free the majority of the time. 'Sorry I do not have stats as of the time of the failure... Don't have number of open files should be negligible (just *how* do you get an exact count - I don't recall). Output of netstat -m follows. Thanks! - ------------------------------------------- Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree ~ 16 1532 260 4736 1280 0 ~ 32 375 137 162252 640 0 ~ 64 3299 23197 184848 320 2614 ~ 128 1798 26 8648 160 0 ~ 256 2139 5 1109884 80 0 ~ 512 55 9 608 40 0 ~ 1K 41 63 5574 20 91 ~ 2K 21 127 323 10 113 ~ 4K 16 1 235 5 0 ~ 8K 14 0 58 5 0 ~ 16K 6 0 95 5 0 ~ 32K 13 0 60 5 0 128K 3 0 15 5 0 256K 1 0 1 5 0 512K 7 0 7 5 0 Memory usage type by bucket size Size Type(s) ~ 16 SMBSTR, SMBIOD, uc_devlist, nexusdev, SMBFS data, SMBFS nname, atexit, ICONV, USB, proc-args, UFS dirhash, p1003.1b, kld, routetbl, ether_multi, vnodes, mount, pcb, soname, shm, MD disk, ATA generic, rman, bus, sysctloid, sysctl, temp, devbuf ~ 32 SMBTEMP, NETSMBDEV, atkbddev, SMBFS nname, USB, proc-args, UFS dirhash, dirrem, mkdir, diradd, freefile, freefrag, indirdep, bmsafemap, newblk, sigio, kld, in_multi, routetbl, ether_multi, ifaddr, BPF, vnodes, cluster_save buffer, pcb, soname, ATAPI generic, taskqueue, SWAP, eventhandler, bus, sysctloid, sysctl, uidinfo, subproc, pgrp, temp, devbuf ~ 64 SMBTEMP, SMBSTR, SMBFS data, SMBFS nname, ICONV, isadev, USB, proc-args, UFS dirhash, allocindir, allocdirect, pagedep, file, routetbl, ether_multi, ifaddr, vnodes, cluster_save buffer, vfscache, pcb, soname, rman, eventhandler, bus, sysctloid, subproc, session, temp, devbuf, lockf ~ 128 SMBTEMP, SMBRQ, SMBIOD, SMB conn, SMBFS node, zombie, USBdev, USB, ZONE, proc-args, UFS dirhash, freeblks, inodedep, dev_t, timecounter, kld, routetbl, vnodes, mount, vfscache, soname, ttys, ATAPI generic, bus, cred, temp, devbuf ~ 256 SMBTEMP, SMBRQ, SMB conn, SMBFS data, ICONV data, USB, proc-args, FFS node, newblk, kqueue, file desc, NFS daemon, routetbl, ifaddr, vnodes, ttys, ACD driver, bus, subproc, temp, devbuf ~ 512 USBdev, UFS dirhash, UFS mount, file desc, mount, BIO buffer, ptys, ATA generic, msg, ioctlops, bus, temp, devbuf ~ 1K kqueue, file desc, NQNFS Lease, shm, MD disk, sem, ioctlops, bus, uidinfo, temp, devbuf ~ 2K uc_devlist, UFS mount, file desc, ifaddr, BIO buffer, pcb, ACD driver, bus, devbuf ~ 4K memdesc, SMBFS data, UFS mount, sem, msg, kobj, bus, proc, temp, devbuf ~ 8K UFS mount, syncache, bus, devbuf ~ 16K mbuf, indirdep, shm, msg, bus, temp, devbuf ~ 32K UFS mount, bus, devbuf 128K VM pgdata, pagedep, bus, temp 256K MSDOSFS mount 512K SMBFS hash, UFS ihash, inodedep, NFS hash, vfscache, ISOFS mount, SWAP Memory statistics by type Type Kern ~ Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ~ SMBTEMP 1 1K 1K102400K 19 0 0 32,64,128,256 ~ SMBSTR 6 1K 1K102400K 8 0 0 16,64 ~ SMBRQ 0 0K 1K102400K 1105216 0 0 128,256 ~ SMBIOD 1 1K 1K102400K 2 0 0 16,128 ~ NETSMBDEV 0 0K 1K102400K 1 0 0 32 ~ SMB conn 2 1K 1K102400K 2 0 0 128,256 ~ atkbddev 2 1K 1K102400K 2 0 0 32 ~ uc_devlist 30 3K 3K102400K 30 0 0 16,2K ~ nexusdev 11 1K 1K102400K 11 0 0 16 ~ memdesc 1 4K 4K102400K 1 0 0 4K ~ mbuf 1 12K 12K102400K 1 0 0 16K ~ SMBFS hash 1 512K 512K102400K 1 0 0 512K ~ SMBFS data 1 4K 6K102400K 1515 0 0 16,64,256,4K ~ SMBFS nname 29 2K 2K102400K 30 0 0 16,32,64 ~ SMBFS node 29 4K 4K102400K 30 0 0 128 ~ atexit 1 1K 1K102400K 1 0 0 16 ~ zombie 0 0K 1K102400K 731 0 0 128 ~ ICONV data 2 1K 1K102400K 2 0 0 256 ~ ICONV 4 1K 1K102400K 4 0 0 16,64 ~ isadev 25 2K 2K102400K 25 0 0 64 ~ USBdev 1 1K 2K102400K 4 0 0 128,512 ~ USB 12 2K 2K102400K 12 0 0 16,32,64,128,256 ~ ZONE 16 2K 2K102400K 16 0 0 128 ~ VM pgdata 1 128K 128K102400K 1 0 0 128K ~ proc-args 34 2K 3K102400K 1066 0 0 16,32,64,128,256 ~ UFS dirhash 66 13K 13K102400K 66 0 0 16,32,64,128,512 ~ UFS mount 9 48K 48K102400K 9 0 0 512,2K,4K,8K,32K ~ UFS ihash 1 512K 512K102400K 1 0 0 512K ~ FFS node 1825 457K 458K102400K 2242 0 0 256 ~ dirrem 0 0K 1K102400K 452 0 0 32 ~ mkdir 0 0K 1K102400K 20 0 0 32 ~ diradd 0 0K 1K102400K 471 0 0 32 ~ freefile 0 0K 1K102400K 249 0 0 32 ~ freeblks 0 0K 2K102400K 62 0 0 128 ~ freefrag 2 1K 3K102400K 99 0 0 32 ~ allocindir 3 1K 1470K102400K 158554 0 0 64 ~ indirdep 1 1K 81K102400K 90 0 0 32,16K ~ allocdirect 0 0K 2K102400K 242 0 0 64 ~ bmsafemap 0 0K 1K102400K 135 0 0 32 ~ newblk 1 1K 1K102400K 158797 0 0 32,256 ~ inodedep 1 512K 518K102400K 323 0 0 128,512K ~ pagedep 3 129K 129K102400K 97 0 0 64,128K ~ p1003.1b 1 1K 1K102400K 1 0 0 16 ~ kqueue 4 4K 7K102400K 281 0 0 256,1K ~ sigio 1 1K 1K102400K 1 0 0 32 ~ file 136 9K 11K102400K 16145 0 0 64 ~ file desc 77 30K 30K102400K 857 0 0 256,512,1K,2K ~ dev_t 912 114K 114K102400K 912 0 0 128 ~ timecounter 5 1K 1K102400K 5 0 0 128 ~ kld 4 1K 1K102400K 35 0 0 16,32,128 ~ NFS hash 1 512K 512K102400K 1 0 0 512K ~ NQNFS Lease 1 1K 1K102400K 1 0 0 1K ~ NFS daemon 1 1K 1K102400K 1 0 0 256 ~ syncache 1 8K 8K102400K 1 0 0 8K ~ in_multi 2 1K 1K102400K 2 0 0 32 ~ routetbl 40 6K 6K102400K 52 0 0 16,32,64,128,256 ~ ether_multi 7 1K 1K102400K 7 0 0 16,32,64 ~ ifaddr 24 4K 4K102400K 24 0 0 32,64,256,2K ~ BPF 3 1K 1K102400K 3 0 0 32 MSDOSFS mount 1 256K 256K102400K 1 0 0 256K ~ vnodes 26 7K 7K102400K 380 0 0 16,32,64,128,256 ~ mount 5 3K 3K102400K 7 0 0 16,128,512 cluster_save buffer 0 0K 1K102400K 161 0 0 32,64 ~ vfscache 2668 1202K 1202K102400K 4683 0 0 64,128,512K ~ BIO buffer 4 8K 264K102400K 246 0 0 512,2K ~ pcb 20 5K 5K102400K 287 0 0 16,32,64,2K ~ soname 7 1K 1K102400K 1624 0 0 16,32,64,128 ~ ptys 3 2K 2K102400K 3 0 0 512 ~ ttys 491 63K 63K102400K 1466 0 0 128,256 ~ ISOFS mount 1 512K 512K102400K 1 0 0 512K ~ shm 12 23K 23K102400K 12 0 0 16,1K,16K ~ MD disk 2 2K 2K102400K 2 0 0 16,1K ~ ATA generic 2 1K 1K102400K 2 0 0 16,512 ~ sem 3 6K 6K102400K 3 0 0 1K,4K ~ ACD driver 2 3K 3K102400K 2 0 0 256,2K ATAPI generic 1 1K 1K102400K 2 0 0 32,128 ~ msg 4 25K 25K102400K 4 0 0 512,4K,16K ~ rman 62 4K 4K102400K 457 0 0 16,64 ~ ioctlops 0 0K 1K102400K 6 0 0 512,1K ~ taskqueue 2 1K 1K102400K 2 0 0 32 ~ SWAP 2 1641K 1641K102400K 2 0 0 32,512K ~ kobj 1 4K 4K102400K 1 0 0 4K ~ eventhandler 13 1K 1K102400K 13 0 0 32,64 ~ bus 938 114K 190K102400K 2652 0 0 16,32,64,128,256,512,1K,2K,4K,8K,16K,32K,128K ~ sysctloid 8 1K 1K102400K 8 0 0 16,32,64 ~ sysctl 0 0K 1K102400K 143 0 0 16,32 ~ uidinfo 6 2K 2K102400K 89 0 0 32,1K ~ cred 21 3K 4K102400K 3187 0 0 128 ~ subproc 140 11K 11K102400K 1664 0 0 32,64,256 ~ proc 2 8K 8K102400K 2 0 0 4K ~ session 25 2K 2K102400K 93 0 0 64 ~ pgrp 28 1K 1K102400K 289 0 0 32 ~ temp 425 136K 166K102400K 7130 0 0 16,32,64,128,256,512,1K,4K,16K,128K ~ devbuf 1035 563K 595K102400K 1532 0 0 16,32,64,128,256,512,1K,2K,4K,8K,16K,32K ~ lockf 19 2K 2K102400K 2221 0 0 64 Memory Totals: In Use Free Requests ~ 7630K 1789K 1477346 ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 02:38:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D8F116A4CE for ; Sat, 22 Jan 2005 02:38:08 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB4B43D5C for ; Sat, 22 Jan 2005 02:38:05 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 3F2A862D8E for ; Sat, 22 Jan 2005 02:38:04 +0000 (WET) From: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= To: freebsd-stable@freebsd.org Date: Sat, 22 Jan 2005 02:37:49 +0000 User-Agent: KMail/1.7.91 References: <41F0F4C1.60505@sdf.lonestar.org> In-Reply-To: <41F0F4C1.60505@sdf.lonestar.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501220237.49782.imobachgs@banot.net> Subject: AAAA queries (was: Realtek 8139 (rl) very poor performance) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 02:38:08 -0000 Thank you all for your responses and your support. However, I changed the=20 network card and it didn't work (I have now a Davicom 9102). Well, anyway, after playing around with ethereal and tcpdump, I think that = the=20 problem have to do with IPv6. Well, not exactly. I found that when I try to= =20 make an HTTP connection (for example, with lynx), my machine sends an AAAA= =20 query and my DNS server doesn't seems to handle it properly. So, I'd like the software stop doing such queries... what can I start for?= =20 Must I recompile aplications? I've get out "INET6" support from the kernel,= =20 but it's not sufficient. Ideas? A link to documentation about it? Thank you! =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 04:39:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE78B16A4CE for ; Sat, 22 Jan 2005 04:39:49 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7583743D2D for ; Sat, 22 Jan 2005 04:39:49 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Fri, 21 Jan 2005 20:39:48 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9FA005D04; Fri, 21 Jan 2005 20:39:48 -0800 (PST) To: Imobach =?iso-8859-1?q?Gonz=E1lez_Sosa?= In-reply-to: Your message of "Sat, 22 Jan 2005 02:37:49 GMT." <200501220237.49782.imobachgs@banot.net> Date: Fri, 21 Jan 2005 20:39:48 -0800 From: "Kevin Oberman" Message-Id: <20050122043948.9FA005D04@ptavv.es.net> cc: freebsd-stable@freebsd.org Subject: Re: AAAA queries (was: Realtek 8139 (rl) very poor performance) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 04:39:49 -0000 > From: Imobach =?iso-8859-1?q?González_Sosa?= > Date: Sat, 22 Jan 2005 02:37:49 +0000 > Sender: owner-freebsd-stable@freebsd.org > > Thank you all for your responses and your support. However, I changed the > network card and it didn't work (I have now a Davicom 9102). > > Well, anyway, after playing around with ethereal and tcpdump, I think that > the > problem have to do with IPv6. Well, not exactly. I found that when I try to > make an HTTP connection (for example, with lynx), my machine sends an AAAA > query and my DNS server doesn't seems to handle it properly. > > So, I'd like the software stop doing such queries... what can I start for? > Must I recompile aplications? I've get out "INET6" support from the kernel, > but it's not sufficient. > > Ideas? A link to documentation about it? Have you used dig(1) or other diagnostic tools to confirm that your DNS server is really not handling AAAA queries? This is really a a sign that the DNS server is seriously broken. AAAA has been a standard for years and any server that does not understand it is probably in very bad shape. Having (or not having) INET6 support is not relevant as the problem is in the resolver. the queries may be sent as either INET6 or INET, but either will ask for AAAA records. The problem is that any application that is INET6 aware will make a call to the resolver for INET6 (AAAA) resolution. Other than modifying the code or using an option to use only INET, I'm afraid you are stuck. Many applications (finger, ssh, telnet, ...) have a -4 option to restrict the operation to INET. But you really need to either get the nameserver fixed or find another nameserver. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 06:36:00 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B486516A4CE; Sat, 22 Jan 2005 06:36:00 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7446243D5A; Sat, 22 Jan 2005 06:36:00 +0000 (GMT) (envelope-from decibel@decibel.org) Received: by flake.decibel.org (Postfix, from userid 1001) id EB4791C8FE; Sat, 22 Jan 2005 00:35:59 -0600 (CST) Date: Sat, 22 Jan 2005 00:35:59 -0600 From: "Jim C. Nasby" To: Don Lewis Message-ID: <20050122063559.GJ67721@decibel.org> Mail-Followup-To: "Jim C. Nasby" , Don Lewis , ertr1013@student.uu.se, freebsd-stable@FreeBSD.org, markir@paradise.net.nz References: <20050121164928.GA50279@falcon.midgard.homeip.net> <200501211909.j0LJ91MC052960@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501211909.j0LJ91MC052960@gw.catspoiler.org> X-Operating-System: FreeBSD 4.10-RELEASE-p3 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i cc: freebsd-stable@FreeBSD.org cc: markir@paradise.net.nz Subject: Re: Disabling write-behind on IDE drives, and SMART X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 06:36:00 -0000 On Fri, Jan 21, 2005 at 11:09:01AM -0800, Don Lewis wrote: > On 21 Jan, Erik Trulsson wrote: > > On Fri, Jan 21, 2005 at 08:31:06AM -0800, Kevin Oberman wrote: > > >> For servers that lack solid backup power (not a 10 minute > >> UPS), I would probably turn it off. But for most systems it is probably > >> worth the risks. > > > > A 10 minute UPS should be plenty for that purpose. All that is needed > > to protect against the risks of write-caching is for the server to be > > able to make an orderly shutdown, which should not take more than a > > couple of minutes. (If you need constant uptime, you need better power > > backup, but that is a different issue.) > > I guess that you haven't had as many UPS failures as I have had. The > usual problem is sudden battery and unexpected battery death which > brings the UPS runtime close to zero. > > The UPSes definitely help with the short hits to the power, but for > anything important I pay the outrageously high premium for SCSI disks > and turn off write caching. At least SCSI has working tagged command > queuing that when used with softupdates avoids the performance hit > caused by turning off write caching, at least for most workloads. Does SATA support an equivalent to tagged queuing? -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 13:11:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4114516A4CE for ; Sat, 22 Jan 2005 13:11:29 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96AFC43D2D for ; Sat, 22 Jan 2005 13:11:28 +0000 (GMT) (envelope-from ksatechnologies@comcast.net) Received: from adamsmain8391 (pcp01189955pcs.waldlk01.mi.comcast.net[68.60.67.98]) by comcast.net (sccrmhc11) with SMTP id <2005012213112701100cd7rde>; Sat, 22 Jan 2005 13:11:27 +0000 From: "KSA Technologies" To: "'Vinod Kashyap'" , Date: Sat, 22 Jan 2005 08:09:27 -0500 Message-ID: <000001c50083$9a48df70$c701a8c0@adamsmain8391> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5commit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 13:11:29 -0000 Vinod, That patch worked. Received a clean buildkernel, installkernel and boot with the patch you supplied. Thanks, Kev -----Original Message----- From: Vinod Kashyap [mailto:vkashyap@amcc.com]=20 Sent: Friday, January 21, 2005 2:23 PM To: ksatechnologies@comcast.net; freebsd-stable@freebsd.org Subject: RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit Let me know if the attached patch works for you too. > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of > ksatechnologies@comcast.net > Sent: Friday, January 21, 2005 8:36 AM > To: freebsd-stable@freebsd.org > Subject: twa breakage on > AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit >=20 >=20 > I also have the same problem with the new 3ware drivers=20 > 9.1.5.2 in -STABLE but I am using the i386 platform with a=20 > Xeon 3.0Ghz processor. > I have one RAID-1 array and one RAID-5 array on the 9500s controller. > /var and /usr/local on the RAID-5 >=20 > Following the FreeBSD instructions to build -STABLE >=20 > make -j8 buildworld > make buildkernel KERNCONF=3D"mykernelconf" > make installkernel KERNCONF=3D"mykernelconf" > reboot >=20 > And it worked. All was fine. Then.... >=20 > mergemaster -p > make installworld > mergemaster > reboot >=20 > Then I could not get to the server via SSH. Found that the=20 > console had the exactly the same symptoms describe in the=20 > thread. I rebooted and at the Daemon Logo I did a "boot=20 > kernel.old" which worked with no problem. The dmesgs are=20 > below. First, 3Ware 9.1.5.2 driver "kernel" and the second=20 > is the "kernel.old" boot. >=20 > --------------/etc/make.conf------------------------------------- > # -- use.perl generated deltas -- # > # Created: Thu Nov 25 08:12:18 2004 > # Setting to use base perl from ports: > PERL_VER=3D5.8.5 > PERL_VERSION=3D5.8.5 > PERL_ARCH=3Dmach > NOPERL=3Dyo > NO_PERL=3Dyo > NO_PERL_WRAPPER=3Dyo > CPUTYPE=3Dp4 > CFLAGS=3D -O2 -pipe -funroll-loops -ffast-math > #CFLAGS=3D -pipe -funroll-loops -ffast-math > COPTFLAGS=3D -O2 -pipe -funroll-loops -ffast-math >=20 >=20 > ------------------Kernel With 3Ware 9.1.5.2-------------------- > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,=20 > 1993, 1994 > The Regents of the University of California. All=20 > rights reserved. > FreeBSD 5.3-STABLE #0: Thu Jan 20 17:54:09 EST 2005 > root@mail.barsproducts.com:/usr/obj/usr/src/sys/BarsMail > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > =20 > Features=3D0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory =3D 1072562176 (1022 MB) > avail memory =3D 1040035840 (991 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > em0: =20 > port 0xa000-0xa01f mem=20 > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device=20 > 1.0 on pci1 > em0: Ethernet address: 00:11:2f:5a:7e:df > em0: Speed:N/A Duplex:N/A > pcib2: at device 28.0 on pci0 > pci2: on pcib2 > 3ware device driver for 9000 series storage controllers,=20 > version: 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port=20 > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff=20 > irq 27 at device 2.0 on pci2 > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > twa0: [GIANT-LOCKED] > uhci0: port 0xd400-0xd41f irq=20 > 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq=20 > 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.5=20 > (no driver attached) > pci0: at device 29.7 (no driver attached) > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > pci3: at device 4.0 (no driver attached) > em1: =20 > port 0xc400-0xc43f mem=20 > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device=20 > 5.0 on pci3 > em1: Ethernet address: 00:11:2f:5a:7e:e0 > em1: Speed:N/A Duplex:N/A > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port=20 > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device=20 > 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6=20 > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4=20 > flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port=20 > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem=20 > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem=20 > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: CDROM at ata0-master UDMA33 > SMP: AP CPU #1 Launched! >=20 > -----------------Kernel.old pre 9.1.5.2 --------------------- > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,=20 > 1993, 1994 > The Regents of the University of California. All=20 > rights reserved. > FreeBSD 5.3-STABLE #1: Mon Dec 27 10:27:38 EST 2004 > root@:/usr/obj/usr/src/sys/BarsMail1 > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf34 Stepping =3D 4 > =20 > Features=3D0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory =3D 1072562176 (1022 MB) > avail memory =3D 1044226048 (995 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > em0: =20 > port 0xa000-0xa01f mem=20 > 0xf1000000-0xf101ffff,0xf1020000-0xf103ffff irq 18 at device=20 > 1.0 on pci1 > em0: Ethernet address: 00:11:2f:5a:7e:df > em0: Speed:N/A Duplex:N/A > pcib2: at device 28.0 on pci0 > pci2: on pcib2 > 3ware device driver for 9000 series storage controllers,=20 > version: 2.50.00.000 > twa0: <3ware 9000 series Storage Controller> port=20 > 0xb000-0xb0ff mem 0xf3000000-0xf37fffff,0xf3800000-0xf38000ff=20 > irq 27 at device 2.0 on pci2 > twa0: [GIANT-LOCKED] > twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > uhci0: port 0xd400-0xd41f irq=20 > 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq=20 > 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.5=20 > (no driver attached) > pci0: at device 29.7 (no driver attached) > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > pci3: at device 4.0 (no driver attached) > em1: =20 > port 0xc400-0xc43f mem=20 > 0xf6020000-0xf603ffff,0xf6000000-0xf601ffff irq 16 at device=20 > 5.0 on pci3 > em1: Ethernet address: 00:11:2f:5a:7e:e0 > em1: Speed:N/A Duplex:N/A > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port=20 > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device=20 > 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6=20 > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4=20 > flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port=20 > 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem=20 > 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem=20 > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: CDROM at ata0-master UDMA33 > da0 at twa0 bus 0 target 0 lun 0 > da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device > da0: 100.000MB/s transfers > da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) > da1 at twa0 bus 0 target 1 lun 0 > da1: <3ware Logical Disk 01 1.00> Fixed Direct Access SCSI-0 device > da1: 100.000MB/s transfers > da1: 476816MB (976519168 512 byte sectors: 255H 63S/T 60785C) > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > em0: Link is up 10 Mbps Full Duplex > em0: Link is Down > em0: Link is up 1000 Mbps Full Duplex > -------------------------------------------------------------- > ------------------------------- >=20 > Hope this information might help. >=20 > Thanks, >=20 > Kev > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to=20 > "freebsd-stable-unsubscribe@freebsd.org" >=20 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 16:51:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D139616A4CE for ; Fri, 21 Jan 2005 16:51:05 +0000 (GMT) Received: from hotmail.com (bay103-dav11.bay103.hotmail.com [65.54.174.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A36AA43D31 for ; Fri, 21 Jan 2005 16:51:05 +0000 (GMT) (envelope-from radomil@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 21 Jan 2005 08:51:02 -0800 Message-ID: Received: from 194.205.123.7 by BAY103-DAV11.phx.gbl with DAV; Fri, 21 Jan 2005 16:50:26 +0000 X-Originating-IP: [194.205.123.7] X-Originating-Email: [radomil@hotmail.com] X-Sender: radomil@hotmail.com From: "Rad Ricka" To: Date: Fri, 21 Jan 2005 16:50:24 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 21 Jan 2005 16:51:02.0643 (UTC) FILETIME=[64263C30:01C4FFD9] X-Mailman-Approved-At: Sat, 22 Jan 2005 13:15:54 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: VMWare Workstation - burncd/DMA Mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Jan 2005 16:51:06 -0000 Hi, I'm having trouble burning CD's from FreeBSD 5.3 guest through WinXP = host on VMWare Workstation 4.5.2=20 My VMWare workstation is complaining about DMA mode when I run: "burncd -s 10 -f /dev/acd0 data test.iso fixate" The error message from VMWare I get is: "Your virtual machine has sent an ATAPI (CD-ROM) command that is only = supported when programming the drive via DMA. You will need to = configure your guest operating system to use DMA when communicating with = DVD/CD-ROM devices. Note that some operating systems will report DMA is available without = actually using it. In those cases, normal CD-ROM operations will still = be available, but special features will only be available if you = re-configure the virtual device as a SCSI device." FreeBSD gives the follwing: "burncd: ioctl(CDRIOCINITTRACK): Input/output error" I have the following lines in my loader.conf: hw.ata.atapi_dma=3D"1" hw.ata.ata_dma=3D"1" and have also tried configuring dma when system is up by running: atacontrol mode 1 udma4 udma4 Any Ideas? Many thanks in advance, Radster From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 14:23:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32B3B16A4CE for ; Sat, 22 Jan 2005 14:23:27 +0000 (GMT) Received: from sdf.lonestar.org (mx.freeshell.org [192.94.73.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB40743D39 for ; Sat, 22 Jan 2005 14:23:26 +0000 (GMT) (envelope-from nunotex@freeshell.org) Received: from nunotex.local (adslsapo-b4-17-29.telepac.pt [81.193.17.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0MEMtMt027021 for ; Sat, 22 Jan 2005 14:22:56 GMT Received: by nunotex.local (Postfix, from userid 1001) id D0CA24101; Sat, 22 Jan 2005 14:23:14 +0000 (WET) Date: Sat, 22 Jan 2005 14:23:14 +0000 From: Nuno Teixeira To: freebsd-stable@freebsd.org Message-ID: <20050122142314.GA574@nunotex.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i Subject: 5.3 stack overflow on a old cyrix p200+ 32MB RAM? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 14:23:27 -0000 Hello to all, I'm trying to install 5.3 in a old pc (p200+ 32MB) but it stops booting from cd with a "stack overflow". I have installed NetBSD 2.0 without problems just as a workaround. I've googled and I saw lot with people with the same problem with old pcs. I have not tryed 4.10 yet. Any opinions? Does FreeBSD no more "old computers" compatible? Yours, NUno Teixeira -- SDF Public Access UNIX System - http://sdf.lonestar.org From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 14:52:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C9B516A4CE; Sat, 22 Jan 2005 14:52:41 +0000 (GMT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E9043D45; Sat, 22 Jan 2005 14:52:41 +0000 (GMT) (envelope-from akiyama@jp.FreeBSD.org) Received: from localhost (castle.jp.FreeBSD.org [2001:218:422:1::15]) ESMTP/inet6 id j0MEqa866008; Sat, 22 Jan 2005 23:52:37 +0900 (JST) (envelope-from akiyama@jp.FreeBSD.org) Date: Sat, 22 Jan 2005 23:52:33 +0900 From: Shunsuke Akiyama To: Michal Mertl In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/mixed; boundary="Multipart_Sat_Jan_22_23:52:33_2005-1" Message-Id: <20050122235234K.akiyama@jp.FreeBSD.org> X-Dispatcher: imput version 20040704(IM147) Lines: 216 cc: Emanuel Strobl cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 14:52:41 -0000 --Multipart_Sat_Jan_22_23:52:33_2005-1 Content-Type: text/plain; charset=US-ASCII At Thu, 20 Jan 2005 14:18:30 +0100, Michal Mertl wrote: > > I wrote: > > Emanuel Strobl wrote: > > > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > > > Dear experts, > > > > > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > > > the other one not (I hate to say it but both are working under win). > > > > > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > > > ucom0, also I can receive signal but not transmit. > > > > > > > > [skip] > > > > > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > > > > > It can break old (working) PL2303 chip, but it works for me with newer > > > > > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > > > also breakes the 2.02 version :( > > > > > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > > > this information (akiyama?)? > > > > > > Thanks a lot, > > > > I've just recently been looking into this too. I used the mentioned > > patch and also linux driver source and have come with the attached > > patch. It contains one more change but I don't know if it's correct. It > > works for both chips on CURRENT for serial console. It detects if the > > chip is rev 3.00 and aplies the patch only for it. > > > > The author of the patch mentions it isn't binary safe - sometimes the > > chip stops working. I planned to test it with binary transfers (ppp) > > today, check if it's working and submit it (with some cleanup) for > > inclusion in FreeBSD. > > > > Michal Mertl > > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. > > Michal Good work! I've updated your patch. If attached patch works correctly with new revision chip, I'll commit this. Please test attached patch, and tell me the result. Regards, -- Shunsuke Akiyama akiyama@jp.FreeBSD.org akiyama@FreeBSD.org --Multipart_Sat_Jan_22_23:52:33_2005-1 Content-Type: application/octet-stream Content-Disposition: attachment; filename="uplcom.c-diff" Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 22 Jan 2005 14:39:45 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -138,6 +141,9 @@ #define RSAQ_STATUS_DSR 0x02 #define RSAQ_STATUS_DCD 0x01 +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 + struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,6 +162,8 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + + int sc_chiptype; /* Type of chip */ }; /* @@ -293,6 +301,7 @@ USB_ATTACH_START(uplcom, sc, uaa); usbd_device_handle dev = uaa->device; struct ucom_softc *ucom; + usb_device_descriptor_t *udd; usb_config_descriptor_t *cdesc; usb_interface_descriptor_t *id; usb_endpoint_descriptor_t *ed; @@ -320,6 +329,16 @@ DPRINTF(("uplcom attach: sc = %p\n", sc)); + /* determine chip type */ + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) >= 0x300) { + DPRINTF(("uplcom_attach: chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("uplcom_attach: chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } + /* initialize endpoints */ ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; sc->sc_intr_number = -1; @@ -521,6 +540,54 @@ return (0); } +struct pl2303x_init { + uint8_t req_type; + uint8_t request; + uint16_t value; + uint16_t index; + uint16_t length; +}; + +Static const struct pl2303x_init pl2303x[] = { + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x0404, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8383, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x0404, 1, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8383, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0, 1, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 1, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 2, 0x44, 0 } +}; + +Static usbd_status +uplcom_pl2303x_init(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i; + + for (i = 0; i < 11; i++) { + req.bmRequestType = pl2303x[i].req_type; + req.bRequest = pl2303x[i].request; + USETW(req.wValue, pl2303x[i].value); + USETW(req.wIndex, pl2303x[i].index); + USETW(req.wLength, pl2303x[i].length); + + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); + if (err) { + printf("%s: uplcom_pl2303x_init: %d: %s\n", + USBDEVNAME(sc->sc_ucom.sc_dev), i, + usbd_errstr(err)); + return (EIO); + } + } + + return (0); +} + Static void uplcom_set_line_state(struct uplcom_softc *sc) { @@ -617,7 +684,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, 0x61); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -744,6 +814,9 @@ } } + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_pl2303x_init(sc)); + return (0); } --Multipart_Sat_Jan_22_23:52:33_2005-1-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 15:52:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9252D16A4CE for ; Sat, 22 Jan 2005 15:52:24 +0000 (GMT) Received: from mail.efacilitas.de (efacilitas.de [213.133.110.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A3743D3F for ; Sat, 22 Jan 2005 15:52:24 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.alpha-tierchen.de (port-212-202-169-228.dynamic.qsc.de [212.202.169.228]) by mail.efacilitas.de (Postfix) with ESMTP id D476E123B75 for ; Sat, 22 Jan 2005 16:52:03 +0100 (CET) Received: from localhost (localhost.local [127.0.0.1]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 6D1C7CCD81E for ; Sat, 22 Jan 2005 16:51:40 +0100 (CET) Received: from mail.alpha-tierchen.de ([127.0.0.1]) by localhost (mail.efacilitas.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28109-08 for ; Sat, 22 Jan 2005 16:51:38 +0100 (CET) Received: from [192.168.1.2] (alpha.local [192.168.1.2]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 55EBBCCD81D for ; Sat, 22 Jan 2005 16:51:38 +0100 (CET) Message-ID: <41F276CD.8020907@cs.tu-berlin.de> Date: Sat, 22 Jan 2005 16:52:45 +0100 From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050120) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at alpha-tierchen.de Subject: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 15:52:24 -0000 I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. > setenv LANG de_DE.ISO8859-1 > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ÚWXYÝ] > setenv LANG de_DE.ISO-8859-1 > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF UVWXYZ > perl perl: warning: Setting locale failed. [lot of indignation about locale settings] I am suspicious that de_DE.UTF-8 would work correct with most software. Is it the only solution to don't use localization currently at all or should it be my ambition to fix this? What should be the correct value? I would prefer the notation "ISO-8859-1", but even the almighty perl does not. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 16:41:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A784316A4CE for ; Sat, 22 Jan 2005 16:41:34 +0000 (GMT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661B043D1D for ; Sat, 22 Jan 2005 16:41:34 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.36.56) by smtp01.syd.iprimus.net.au (7.0.036) id 41A76DD90186949B; Sun, 23 Jan 2005 03:41:28 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 3103A433F; Sun, 23 Jan 2005 03:41:42 +1100 (EST) Date: Sun, 23 Jan 2005 03:41:42 +1100 From: Tim Robbins To: Bj?rn K?nig Message-ID: <20050122164142.GA79245@cat.robbins.dropbear.id.au> References: <41F276CD.8020907@cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F276CD.8020907@cs.tu-berlin.de> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 16:41:34 -0000 On Sat, Jan 22, 2005 at 04:52:45PM +0100, Bj?rn K?nig wrote: > I am a bit confused. Neither de_DE.ISO-8859-1 nor > de_DE.ISO8859-1 work properly in all cases. > > > setenv LANG de_DE.ISO8859-1 > > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' > ABCDEF ?WXY?] For better or worse, this is not the correct way to perform case conversion in non-ASCII locales on FreeBSD 5 and later. See the COMPATIBILITY section of the tr(1) manpage for more information. > > > setenv LANG de_DE.ISO-8859-1 > > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' > ABCDEF UVWXYZ > > perl > perl: warning: Setting locale failed. > [lot of indignation about locale settings] FreeBSD uses the name de_DE.ISO8859-1 instead of de_DE.ISO-8859-1. Most base system utilities don't complain if LANG or the related LC_* variables are invalid. > > I am suspicious that de_DE.UTF-8 would work correct > with most software. Is it the only solution to don't > use localization currently at all or should it be my > ambition to fix this? What should be the correct > value? I would prefer the notation "ISO-8859-1", but > even the almighty perl does not. Setting LANG to de_DE.ISO8859-1 should work. The alternative is UTF-8, which is understood by most text-processing utilities in the base system (ls, wc, grep, sed, ...). However, at this stage neither sh nor vi work correctly with UTF-8, so you would need to replace these with (for example) bash and vim. Tim From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 17:09:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FACB16A4CE for ; Sat, 22 Jan 2005 17:09:37 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3402B43D39 for ; Sat, 22 Jan 2005 17:09:36 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 22 Jan 2005 17:09:34 -0000 Received: from p3EE26C32.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.108.50) by mail.gmx.net (mp027) with SMTP; 22 Jan 2005 18:09:34 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id j0MH7v0Z092736 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 22 Jan 2005 18:08:09 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Sat, 22 Jan 2005 18:07:40 +0100 User-Agent: KMail/1.7.2 References: <41F276CD.8020907@cs.tu-berlin.de> In-Reply-To: <41F276CD.8020907@cs.tu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2475791.EgKh8slqY5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501221807.48299.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: =?iso-8859-15?q?Bj=F6rn_K=F6nig?= Subject: Re: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 17:09:37 -0000 --nextPart2475791.EgKh8slqY5 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday, 22. January 2005 16:52, Bj=F6rn K=F6nig wrote: > I am a bit confused. Neither de_DE.ISO-8859-1 nor > de_DE.ISO8859-1 work properly in all cases. > > > setenv LANG de_DE.ISO8859-1 > > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' > > ABCDEF =DAWXY=DD] This is the correct locale name, but don't use tr like that, you can't rely= on=20 that to work correctly with charsets which aren't symmetric in=20 lower&uppercase characters (it used to work at some point for the ISO8859-1 [5] locales but ceased after a POSIX related modification to tr). Use tr [:lower:] [:upper:] instead. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2475791.EgKh8slqY5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB8ohkXhc68WspdLARArXqAJ4isHSLx4STYycxDXYSzzhjdMXg7ACgpzlB bCtmD56+d1q/9D36UcFDGOs= =c2Cl -----END PGP SIGNATURE----- --nextPart2475791.EgKh8slqY5-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 17:14:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B694216A4CE; Sat, 22 Jan 2005 17:14:05 +0000 (GMT) Received: from mail.efacilitas.de (efacilitas.de [213.133.110.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F95343D2D; Sat, 22 Jan 2005 17:14:05 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.alpha-tierchen.de (port-212-202-169-228.dynamic.qsc.de [212.202.169.228]) by mail.efacilitas.de (Postfix) with ESMTP id 64EFA1239E3; Sat, 22 Jan 2005 18:13:45 +0100 (CET) Received: from localhost (localhost.local [127.0.0.1]) by mail.alpha-tierchen.de (Postfix) with ESMTP id DEF05CCD81E; Sat, 22 Jan 2005 18:13:21 +0100 (CET) Received: from mail.alpha-tierchen.de ([127.0.0.1]) by localhost (mail.efacilitas.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91639-03; Sat, 22 Jan 2005 18:13:20 +0100 (CET) Received: from [192.168.1.2] (alpha.local [192.168.1.2]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 3DE0FCCD81D; Sat, 22 Jan 2005 18:13:20 +0100 (CET) Message-ID: <41F289F4.5040100@cs.tu-berlin.de> Date: Sat, 22 Jan 2005 18:14:28 +0100 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050120) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Tim Robbins References: <41F276CD.8020907@cs.tu-berlin.de> <20050122164142.GA79245@cat.robbins.dropbear.id.au> In-Reply-To: <20050122164142.GA79245@cat.robbins.dropbear.id.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at alpha-tierchen.de cc: freebsd-stable@freebsd.org Subject: Re: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 17:14:05 -0000 Tim Robbins wrote: >For better or worse, this is not the correct way to perform case conversion >in non-ASCII locales on FreeBSD 5 and later. See the COMPATIBILITY section >of the tr(1) manpage for more information. > Thanks a lot for this hint. I will pay more attention to this section. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 17:29:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07A0E16A4CE for ; Sat, 22 Jan 2005 17:29:23 +0000 (GMT) Received: from mail.efacilitas.de (efacilitas.de [213.133.110.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B385643D45 for ; Sat, 22 Jan 2005 17:29:22 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.alpha-tierchen.de (port-212-202-169-228.dynamic.qsc.de [212.202.169.228]) by mail.efacilitas.de (Postfix) with ESMTP id A220B1239E3; Sat, 22 Jan 2005 18:28:52 +0100 (CET) Received: from localhost (localhost.local [127.0.0.1]) by mail.alpha-tierchen.de (Postfix) with ESMTP id 75936CCD81E; Sat, 22 Jan 2005 18:28:23 +0100 (CET) Received: from mail.alpha-tierchen.de ([127.0.0.1]) by localhost (mail.efacilitas.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91644-06; Sat, 22 Jan 2005 18:28:20 +0100 (CET) Received: from [192.168.1.2] (alpha.local [192.168.1.2]) by mail.alpha-tierchen.de (Postfix) with ESMTP id AB3EFCCD81D; Sat, 22 Jan 2005 18:28:20 +0100 (CET) Message-ID: <41F28D79.8080102@cs.tu-berlin.de> Date: Sat, 22 Jan 2005 18:29:29 +0100 From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050120) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <41F276CD.8020907@cs.tu-berlin.de> <200501221807.48299.michaelnottebrock@gmx.net> In-Reply-To: <200501221807.48299.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at alpha-tierchen.de cc: freebsd-stable@freebsd.org Subject: Re: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 17:29:23 -0000 Michael Nottebrock schrieb: > >Use tr [:lower:] [:upper:] instead. > I was wondering about a third-party script which always worked for years with Solaris. I just didn't realized that this issue concerns a difference between SysV and BSD. I tried to set another LANG string and it worked, but now I see that it will work this way with an arbitrary string, because it's invalid. ;-) Björn From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 18:45:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFA0D16A4CE for ; Sat, 22 Jan 2005 18:45:59 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFD1043D49 for ; Sat, 22 Jan 2005 18:45:58 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id j0MIjw01009896 for ; Sat, 22 Jan 2005 20:45:58 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <41F29F69.1040509@he.iki.fi> Date: Sat, 22 Jan 2005 20:46:01 +0200 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: hang at fxp0 with RELENG_5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 18:45:59 -0000 I upgraded a dual xeon from 5.3 to RELENG_5 a few days ago and the boot hangs after probing fxp0. Should I compile kernel debugger in and look for a stack trace or is there a known issue? This on intel 7505 board. Pete From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 19:02:35 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC09C16A4CE for ; Sat, 22 Jan 2005 19:02:35 +0000 (GMT) Received: from smtp.rol.ru (smtp.rol.ru [194.67.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id E636543D1D for ; Sat, 22 Jan 2005 19:02:34 +0000 (GMT) (envelope-from peterp@online.ru) Received: from ts12-a241.Spb.dial.rol.ru ([212.46.202.241]:63237 "EHLO [212.46.202.241]" smtp-auth: "peterp@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by gnome06.net.rol.ru with ESMTPSA id S33723AbVAVTCc (ORCPT ); Sat, 22 Jan 2005 22:02:32 +0300 Message-ID: <41F2A378.1090301@online.ru> Date: Sat, 22 Jan 2005 22:03:20 +0300 From: Petr Panteleyev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: LAN over Bluetooth failure with 5.3-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 19:02:35 -0000 I'm trying to connect WinXP with 5.3-STABLE via Bluetooth using USB dongles. I followed Handbook, set up and started rc.bluetooth, hcsecd, sdpd and rfcomm_pppd. My dongle is recognized, pairing goes well. Connection from WinXP to FreeBSD can be always established but when I'm trying to send any data over this connection, it drops very soon with the following diagnostics: Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond last message repeated 3 times Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond last message repeated 2 times Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:46 elrond kernel: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 Jan 22 21:47:46 elrond kernel: ng_l2cap_l2ca_receive: ubt0l2cap - unexpected L2CAP data packet. Invalid channel state, cid=75, state=5 I tried to reduce MTU and MRU for ppp down to 512. It helped a bit - connection was alive a bit longer. Then again, connection dropped with the above diagnostics. Just have no idea where to dig further. Regards, Petr From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 19:07:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB00216A4CE for ; Sat, 22 Jan 2005 19:07:53 +0000 (GMT) Received: from smtp.banot.net (95.Red-80-36-245.pooles.rima-tde.net [80.36.245.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 669F943D2D for ; Sat, 22 Jan 2005 19:07:52 +0000 (GMT) (envelope-from imobachgs@banot.net) Received: from gofio (unknown [192.168.1.31]) by smtp.banot.net (Postfix) with ESMTP id 6268211E7 for ; Sat, 22 Jan 2005 19:07:49 +0000 (WET) Resent-From: Imobach =?iso-8859-15?q?Gonz=E1lez_Sosa?= Resent-To: freebsd-stable@freebsd.org Resent-Date: Sat, 22 Jan 2005 19:07:19 +0000 Resent-Message-ID: <200501221907.19062.imobachgs@banot.net> From: Imobach =?iso-8859-15?q?Gonz=E1lez_Sosa?= To: "Kevin Oberman" Date: Sat, 22 Jan 2005 18:43:44 +0000 User-Agent: KMail/1.7.91 References: <20050122043948.9FA005D04@ptavv.es.net> In-Reply-To: <20050122043948.9FA005D04@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501221843.45324.imobachgs@banot.net> Subject: Re: AAAA queries (was: Realtek 8139 (rl) very poor performance) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 19:07:53 -0000 > Have you used dig(1) or other diagnostic tools to confirm that your DNS > server is really not handling AAAA queries? This is really a a sign that > the DNS server is seriously broken. AAAA has been a standard for years > and any server that does not understand it is probably in very bad > shape. Thanks for your answer. I followed your advice, and that are the facts: Using "dig hostname @my-isp-dnsserver A" seems to work pretty fine. However= ,=20 if I type: "dig hostname @my-isp-dnsserver AAAA" sometimes miss (timeout)=20 and, when it works, I get different results (no ip address, only pointer to= =20 an authoritative DNS server). I've also done some tests using lynx (ipv6) and links (only ipv4). When I u= se=20 links, it always works: it performs and "A" query and gets a result back.=20 Then, the HTTP conversation starts. However, using lynx, it performs first of all an AAAA query. When it works= =20 (not always do), I get a response but no IP address into that response. The= n,=20 sometimes it tries again with an A query, and then works. However, timeouts= =20 are killin' my patience :/ I've tested this issue with two different name servers. Could I confirm tha= t=20 is a DNS server's fault? Is my fault? Does exist any workaround about it? Thank you. =2D-=20 Imobach Gonz=E1lez Sosa imobachgs en banot punto net osoh en jabber.org From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 20:24:51 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A5FA16A50C for ; Sat, 22 Jan 2005 20:24:51 +0000 (GMT) Received: from osiris.itlegion.ru (osiris.itlegion.ru [84.21.226.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73F4143D2D for ; Sat, 22 Jan 2005 20:24:50 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: from artem ([192.168.0.12]) by osiris.itlegion.ru (8.13.1/8.13.1) with SMTP id j0MKOeBp088357 for ; Sat, 22 Jan 2005 23:24:40 +0300 (MSK) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 63706, updated: 22.01.2005] Message-ID: <000901c500c1$01e5c250$0c00a8c0@artem> From: "Artem Kuchin" To: Date: Sat, 22 Jan 2005 23:28:58 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Cannot build kernel with options WITNESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 20:24:51 -0000 I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys /kern/subr_witness.c /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/OMNI2. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. THE KERNEL CONFIG FILE : machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions #options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device em device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da # FireWire support device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10000 options IPFIREWALL_DEFAULT_TO_ACCEPT device snp device speaker #options DDB #options KDB #options BREAK_TO_DEBUGGER options INVARIANT_SUPPORT options INVARIANTS options WITNESS options WITNESS_KDB options WITNESS_SKIPSPIN #options ADAPTIVE_GIANT # Giant mutex is adaptive. Regards, Artem Kuchin IT Legion Ltd. Russia, Moscow www.itlegion.ru matrix@itlegion.ru +7 095 232-0338 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 20:39:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED88116A4CE for ; Sat, 22 Jan 2005 20:39:55 +0000 (GMT) Received: from onyx.hysteria.sk (onyx.hysteria.sk [195.168.3.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E231843D3F for ; Sat, 22 Jan 2005 20:39:54 +0000 (GMT) (envelope-from fofo@hysteria.sk) Received: (qmail 10245 invoked by uid 0); 22 Jan 2005 20:39:48 -0000 Received: from unknown (HELO [192.168.1.33]) ([62.168.75.5]) (envelope-sender ) by c0re.hysteria.sk (qmail-ldap-1.03) with SMTP for ; 22 Jan 2005 20:39:48 -0000 Message-ID: <41F2BA0F.4020008@hysteria.sk> Date: Sat, 22 Jan 2005 21:39:43 +0100 From: Michal Kapalka User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: Artem Kuchin References: <000901c500c1$01e5c250$0c00a8c0@artem> In-Reply-To: <000901c500c1$01e5c250$0c00a8c0@artem> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on onyx.hysteria.sk X-Spam-Status: No, hits=-4.9 required=5.0 cc: freebsd-stable@freebsd.org Subject: Re: Cannot build kernel with options WITNESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fofo@hysteria.sk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:39:56 -0000 look in /usr/src/UPDATING *** 20040710: A revamp of the debugging code in the kernel with some visible changes beyond just the debugging experience: o The DDB option is now specific to the DDB debugger backend and should not be used any more for conditional compilation of debugging code for when debugging is enabled. Use the KDB option for this. o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED respectively. This is in line with the first bullet. o The remote GDB support has been untangled from DDB and needs to be enabled separately now. Use the GDB option for this. o The GDB_REMOTE_CHAT option has been removed. Support for this homegrown feature is discontinued. The GDB remote protocol supports console output and it makes sense to use that. o The DDB_NOKLDSYM option has been removed. The DDB debugger now supports both direct symbol table lookups as well as KLD symbol lookups through the linker. *** Best Regards fofo > I cvssed just an hour ago. 5.3-STABLE and cannot build > kernel with WITNES. It complains: > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -W > missing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -st > d=c99 -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/contrib/dev/acpica -I/us > r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf > -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd > -I/usr/sr > c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > -finline-limit=8 > 000 --param inline-unit-growth=100 --param large-function-growth=1000 > -mno-alig > n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror > /usr/src/sys > /kern/subr_witness.c > /usr/src/sys/kern/subr_witness.c:1737: warning: > 'witness_proc_has_locks' defined > but not used > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/OMNI2. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > THE KERNEL CONFIG FILE : > > > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident OMNI2 > > options SMP > > options QUOTA > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > #options MD_ROOT # MD is a potential root device > #options NFSCLIENT # Network Filesystem Client > #options NFSSERVER # Network Filesystem Server > #options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time > extensions > #options KBD_INSTALL_CDEV # install a CDEV entry in /dev > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device da # Direct Access (disks) > device pass # Passthrough device (direct SCSI access) > device twe # 3ware ATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > #device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > > device miibus # MII bus support > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > device em > > > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > #device gif # IPv6 and IPv4 tunneling > #device faith # IPv6-to-IPv4 relaying (translation) > > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > > > # FireWire support > device firewire # FireWire bus code > #device sbp # SCSI over FireWire (Requires scbus and da) > #device fwe # Ethernet over FireWire (non-standard!) > > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10000 > options IPFIREWALL_DEFAULT_TO_ACCEPT > > device snp > device speaker > > #options DDB > #options KDB > #options BREAK_TO_DEBUGGER > options INVARIANT_SUPPORT > options INVARIANTS > options WITNESS > options WITNESS_KDB > options WITNESS_SKIPSPIN > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > > Regards, > Artem Kuchin > IT Legion Ltd. > Russia, Moscow > www.itlegion.ru > matrix@itlegion.ru > +7 095 232-0338 > > _______________________________________________ > 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 Jan 22 21:16:40 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96D5716A4CF for ; Sat, 22 Jan 2005 21:16:40 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B3F843D55 for ; Sat, 22 Jan 2005 21:16:40 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0MLGNvx035639; Sat, 22 Jan 2005 16:16:23 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0MLGJrm035635; Sat, 22 Jan 2005 21:16:23 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 22 Jan 2005 21:16:19 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Artem Kuchin In-Reply-To: <000901c500c1$01e5c250$0c00a8c0@artem> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Cannot build kernel with options WITNESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 21:16:40 -0000 On Sat, 22 Jan 2005, Artem Kuchin wrote: > I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with > WITNES. It complains: This occurs when building WITNESS without DDB in the kernel, which was not a tested build case when I added "show alllocks", and apparently is a relatively uncommon configuration as you're the first person to bump into it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't fix the problem for you. Thanks! Robert N M Watson > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W > missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st > d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us > r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf > -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr > c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 > 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig > n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys > /kern/subr_witness.c > /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined > but not used > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/OMNI2. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > THE KERNEL CONFIG FILE : > > > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident OMNI2 > > options SMP > > options QUOTA > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > #options MD_ROOT # MD is a potential root device > #options NFSCLIENT # Network Filesystem Client > #options NFSSERVER # Network Filesystem Server > #options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > #options KBD_INSTALL_CDEV # install a CDEV entry in /dev > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device da # Direct Access (disks) > device pass # Passthrough device (direct SCSI access) > device twe # 3ware ATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > #device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > > device miibus # MII bus support > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > device em > > > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > #device gif # IPv6 and IPv4 tunneling > #device faith # IPv6-to-IPv4 relaying (translation) > > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > > > # FireWire support > device firewire # FireWire bus code > #device sbp # SCSI over FireWire (Requires scbus and da) > #device fwe # Ethernet over FireWire (non-standard!) > > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10000 > options IPFIREWALL_DEFAULT_TO_ACCEPT > > device snp > device speaker > > #options DDB > #options KDB > #options BREAK_TO_DEBUGGER > options INVARIANT_SUPPORT > options INVARIANTS > options WITNESS > options WITNESS_KDB > options WITNESS_SKIPSPIN > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > > Regards, > Artem Kuchin > IT Legion Ltd. > Russia, Moscow > www.itlegion.ru > matrix@itlegion.ru > +7 095 232-0338 > > _______________________________________________ > 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 Jan 22 22:22:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3286216A4CE; Sat, 22 Jan 2005 22:22:18 +0000 (GMT) Received: from osiris.itlegion.ru (osiris.itlegion.ru [84.21.226.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7151C43D48; Sat, 22 Jan 2005 22:22:17 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: from artem ([192.168.0.12]) by osiris.itlegion.ru (8.13.1/8.13.1) with SMTP id j0MMM7cQ088843; Sun, 23 Jan 2005 01:22:07 +0300 (MSK) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 63706, updated: 22.01.2005] Message-ID: <002801c500d1$6a711d50$0c00a8c0@artem> From: "Artem Kuchin" To: "Robert Watson" References: Date: Sun, 23 Jan 2005 01:26:26 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-stable@freebsd.org Subject: Re: Cannot build kernel with options WITNESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 22:22:18 -0000 > On Sat, 22 Jan 2005, Artem Kuchin wrote: > >> I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with >> WITNES. It complains: > > This occurs when building WITNESS without DDB in the kernel, which was not > a tested build case when I added "show alllocks", and apparently is a > relatively uncommon configuration as you're the first person to bump into > it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and > subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't > fix the problem for you. > It fixed the problem. I am actually stuggling with unpredictable weird lock ups, when the host can be pinged but i cannot connect via ssh/telnet or httpd or anything else. It happens w/o any visible reason. I am running several jails with mysql and apache in each and canot make the whole system stable yet. Regards, Artem Kuchin IT Legion Ltd. Russia, Moscow www.itlegion.ru matrix@itlegion.ru +7 095 232-0338 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 22:29:01 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0448216A4CE for ; Sat, 22 Jan 2005 22:29:01 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8436143D2D for ; Sat, 22 Jan 2005 22:29:00 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0MMSh5B036648; Sat, 22 Jan 2005 17:28:43 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0MMShhl036645; Sat, 22 Jan 2005 22:28:43 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 22 Jan 2005 22:28:43 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Artem Kuchin In-Reply-To: <002801c500d1$6a711d50$0c00a8c0@artem> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Cannot build kernel with options WITNESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 22:29:01 -0000 On Sun, 23 Jan 2005, Artem Kuchin wrote: > > On Sat, 22 Jan 2005, Artem Kuchin wrote: > > > >> I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with > >> WITNES. It complains: > > > > This occurs when building WITNESS without DDB in the kernel, which was not > > a tested build case when I added "show alllocks", and apparently is a > > relatively uncommon configuration as you're the first person to bump into > > it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and > > subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't > > fix the problem for you. > > It fixed the problem. I am actually stuggling with unpredictable weird > lock ups, when the host can be pinged but i cannot connect via > ssh/telnet or httpd or anything else. It happens w/o any visible reason. > I am running several jails with mysql and apache in each and canot make > the whole system stable yet. This is typically a sign of one of two problems: - The system is live locked due to very high load, so the ithread, netisrs, etc, in the kernel run fine, but user processes don't get a chance to run. - The system is dead locked due to user space processes getting wedged on common locks, but the kernel ithreads and netisrs can keep on responding. I generally assume that it's a deadlock as opposed to a live lock. I'd compile a kernel with DDB, KDB, WITNESS, and BREAK_TO_DEBUGGER. When the system appears to wedge, break into the debugger using a console or serial break (FYI: serial break is more reliable, and you get the benefit of being able to easily copy and paste debugging output using the serial console for DDB). Use "show alllocks" and "show lockedvnods" to examine most of the system's locking state. Changes are, either all the interesting processes are stacked up on VFS or VM locks, since those kinds of deadlocks produce the exact symptoms you describe: ping works fine because it only hits the netisr, but when you open TCP connections, the sshd (etc) block on VM or VFS locks attempting to fork new children or access a file in the file system name space. At first, the TCP connections will establish but there will be no application data; after a bit, they will not even return a SYN/ACK because the listen queue for the listen socket has filled. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sat Jan 22 22:52:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75B3C16A4CE for ; Sat, 22 Jan 2005 22:52:49 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D008843D4C for ; Sat, 22 Jan 2005 22:52:48 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.99] (i-99.forrie.net. [192.168.1.99]) (authenticated bits=0) by forrie.com with ESMTP id j0MMqhFj089160verify=NO) for ; Sat, 22 Jan 2005 17:52:44 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <41F2D93C.60503@forrie.com> Date: Sat, 22 Jan 2005 17:52:44 -0500 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 1.0 (Windows/20050120) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: PF rule statistics (hits) on individual rules.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 22 Jan 2005 22:52:49 -0000 I'm migrating one of my systems to PF from IPFW. In so doing and planning, I've reviewed the manpages and some online docs. I've become dependent upon "ipfw -t" to determine hits on various spam rules I've implemented - some of them large lists of /24's. I've not been able to determine that there is an equivalent in PF - though I imagine there must be some method to accomplish this. I'd appreciate if someone could help point in the right direction. Thanks.....