From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 00:04:24 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D60A106567C for ; Sun, 29 Jun 2008 00:04:24 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id 5CD608FC0C for ; Sun, 29 Jun 2008 00:04:23 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from laptop.deepcore.dk (laptop.deepcore.dk [192.168.0.138]) by deepcore.dk (8.14.2/8.13.8) with ESMTP id m5T03tPD090574; Sun, 29 Jun 2008 02:03:56 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) Message-Id: From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: Garrett Cooper In-Reply-To: <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v924) Date: Sun, 29 Jun 2008 02:03:55 +0200 References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <4863B968.4040805@clearchain.com> <7d6fde3d0806262004u171bf9dx179564be5a76d9c7@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> X-Mailer: Apple Mail (2.924) Cc: ed@80386.nl, current@FreeBSD.ORG, Derek Ragona Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 00:04:24 -0000 On 28Jun, 2008, at 23:10 , Garrett Cooper wrote: > > FWIW (I've discovered this through personal experience and reading a > lot of docs), the only way to get "hardware RAID" with iir and the > ICH9R chipset is through the Matrix Manager (either by creating one at > the BIOS level console or Windows -- bleh). FreeBSD spotted it as a > single drive (/dev/ar0), so at that point it was being managed by the > southbridge. OK, if you have and ICH9 you *do not and can not* use the IIR driver, =20= the IIR driver is for HW based RAID cards from Intel (the devices show =20= up as CAM disks). I wonder where you got the impression that the IIR =20 driver was in use ? The ICHXX are all just plain (S)ATA devices, with =20= the versions ending in 'R' having a different PCI ID so the BIOS can =20 tell if you paid extra to get the software RAID "option" . Its all =20 just marketing rubbish... This is the essential piece of info here. > Performance sucks, the array rebuild takes eons (16 hours for adding a > 1TB drive to an existing 4 x 750GB drive array with an Core 2 E6700 > with 2GB RAM under Vista x64) and the rebuild console is _only_ > available under Windows =3D(. > > At least it's keeping the filesystem intact though, long enough for me > to make a redundant copy of the data then move all this junk over to > another safe place while I grab DVD+R/W's and wait for my 3ware card > to come in the mail.. I hate to bring this to you, but you will not have an intact =20 filesystem when the rebuild is done, you have no parity data to =20 rebuild from, just as the docs states. -S=F8ren From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 02:41:07 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A03C5106567B; Sun, 29 Jun 2008 02:41:07 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 67C248FC19; Sun, 29 Jun 2008 02:41:07 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T2f4Kj096032; Sat, 28 Jun 2008 22:41:05 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T2f4fo054956; Sat, 28 Jun 2008 22:41:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B1CAE73039; Sat, 28 Jun 2008 22:41:04 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629024104.B1CAE73039@freebsd-current.sentex.ca> Date: Sat, 28 Jun 2008 22:41:04 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 02:41:07 -0000 TB --- 2008-06-29 01:26:31 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 01:26:31 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-06-29 01:26:31 - cleaning the object tree TB --- 2008-06-29 01:26:57 - cvsupping the source tree TB --- 2008-06-29 01:26:57 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-06-29 01:27:03 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 01:27:03 - cd /src TB --- 2008-06-29 01:27:03 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 01:27:06 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 02:34:56 UTC 2008 TB --- 2008-06-29 02:34:56 - generating LINT kernel config TB --- 2008-06-29 02:34:56 - cd /src/sys/powerpc/conf TB --- 2008-06-29 02:34:56 - /usr/bin/make -B LINT TB --- 2008-06-29 02:34:56 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 02:34:56 - cd /src TB --- 2008-06-29 02:34:56 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 02:34:56 UTC 2008 >>> 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 [...] /src/sys/netinet6/in6_rmx.c:337: error: 'rtq_timeout6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:337: error: (Each undeclared identifier is reported only once /src/sys/netinet6/in6_rmx.c:337: error: for each function it appears in.) /src/sys/netinet6/in6_rmx.c:373: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:373: error: 'timer6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c: In function 'in6_inithead': /src/sys/netinet6/in6_rmx.c:472: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:472: error: 'timer6' undeclared (first use in this function) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 02:41:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 02:41:04 - ERROR: failed to build lint kernel TB --- 2008-06-29 02:41:04 - tinderbox aborted TB --- 3325.43 user 397.12 system 4473.12 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 03:11:20 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87F131065673 for ; Sun, 29 Jun 2008 03:11:20 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 0DAF68FC18 for ; Sun, 29 Jun 2008 03:11:19 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so634415fgb.35 for ; Sat, 28 Jun 2008 20:11:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=dQ2TTB3EzME9oobySYXNPp63D+4V8QkyA450TwM/uGU=; b=u3BHckGqedeIQ/GjeTiLXfiAN3GiQNaqeJd4cUQXWT7sU1kkUdNjIQ8uRHnp/oeTBe utWU1i8mXnUoHR+DCmD0PKnR1NpxN3EbuueQVXm4tI88Ptp+2aQUNijPWrVujFLrs8yk s+BajpW9Napoj20/xVL4Q6QVYYWOIkNejAMQE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XML3/W1reseCugUXkczt8vjrgo1Ey+uuUb3QdD/h1tUckOJaaJi7uPSZ5QqyrErxVY 25WobBAJsmBd2fLjYMdGRHITaAAro8yCwIbNS+lV9zRpZmsoI2IxB0/X8CDDMp6N5+BT WYLRqMzOkcp8h4SAPY7Vej25v8Cg0eNvHFrjU= Received: by 10.86.57.9 with SMTP id f9mr4245857fga.66.1214709078719; Sat, 28 Jun 2008 20:11:18 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sat, 28 Jun 2008 20:11:18 -0700 (PDT) Message-ID: <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> Date: Sat, 28 Jun 2008 20:11:18 -0700 From: "Garrett Cooper" To: "=?ISO-8859-1?Q?S=F8ren_Schmidt?=" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> Cc: ed@80386.nl, current@freebsd.org, Derek Ragona Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 03:11:20 -0000 On Sat, Jun 28, 2008 at 5:03 PM, S=F8ren Schmidt wrote: > > On 28Jun, 2008, at 23:10 , Garrett Cooper wrote: > >> >> FWIW (I've discovered this through personal experience and reading a >> lot of docs), the only way to get "hardware RAID" with iir and the >> ICH9R chipset is through the Matrix Manager (either by creating one at >> the BIOS level console or Windows -- bleh). FreeBSD spotted it as a >> single drive (/dev/ar0), so at that point it was being managed by the >> southbridge. > > OK, if you have and ICH9 you *do not and can not* use the IIR driver, the > IIR driver is for HW based RAID cards from Intel (the devices show up as = CAM > disks). I wonder where you got the impression that the IIR driver was in = use > ? The ICHXX are all just plain (S)ATA devices, with the versions ending i= n > 'R' having a different PCI ID so the BIOS can tell if you paid extra to g= et > the software RAID "option" . Its all just marketing rubbish... > > This is the essential piece of info here. > >> Performance sucks, the array rebuild takes eons (16 hours for adding a >> 1TB drive to an existing 4 x 750GB drive array with an Core 2 E6700 >> with 2GB RAM under Vista x64) and the rebuild console is _only_ >> available under Windows =3D(. >> >> At least it's keeping the filesystem intact though, long enough for me >> to make a redundant copy of the data then move all this junk over to >> another safe place while I grab DVD+R/W's and wait for my 3ware card >> to come in the mail.. > > I hate to bring this to you, but you will not have an intact filesystem w= hen > the rebuild is done, you have no parity data to rebuild from, just as the > docs states. > > -S=F8ren Just as you predicted, the disk(s) are unreadable still, even after the rebuild (and I hope to hell that it didn't destroy/disturb any data on the surviving members). I may just have to get it sent off for recovery (after I dd the remaining members because there's still some usable data there -- bloody 2.7TB ... grr) -- apart from that I don't think I have a choice. Oh, where's this "document" of which you speak all the time? I don't see anything about parity support not being available in either the geom or iir manpage, or the iir sourcecode. If someone needs a helping hand inserting that logic into the kernel, I'll gladly assist so others don't follow my footsteps and fsck up their data. For once I wish I had been running Linux or Windows (at least) :(... Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 03:28:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 239D41065671; Sun, 29 Jun 2008 03:28:48 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id DE94E8FC16; Sun, 29 Jun 2008 03:28:47 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T3SicY091475; Sat, 28 Jun 2008 23:28:44 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T3SiCK080713; Sat, 28 Jun 2008 23:28:44 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 84E9873039; Sat, 28 Jun 2008 23:28:44 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629032844.84E9873039@freebsd-current.sentex.ca> Date: Sat, 28 Jun 2008 23:28:44 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 03:28:48 -0000 TB --- 2008-06-29 02:18:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 02:18:18 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-06-29 02:18:18 - cleaning the object tree TB --- 2008-06-29 02:18:47 - cvsupping the source tree TB --- 2008-06-29 02:18:47 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-06-29 02:18:54 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 02:18:54 - cd /src TB --- 2008-06-29 02:18:54 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 02:18:58 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 03:22:04 UTC 2008 TB --- 2008-06-29 03:22:04 - generating LINT kernel config TB --- 2008-06-29 03:22:04 - cd /src/sys/sparc64/conf TB --- 2008-06-29 03:22:04 - /usr/bin/make -B LINT TB --- 2008-06-29 03:22:04 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 03:22:04 - cd /src TB --- 2008-06-29 03:22:04 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 03:22:04 UTC 2008 >>> 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 [...] /src/sys/netinet6/in6_rmx.c:337: error: 'rtq_timeout6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:337: error: (Each undeclared identifier is reported only once /src/sys/netinet6/in6_rmx.c:337: error: for each function it appears in.) /src/sys/netinet6/in6_rmx.c:373: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:373: error: 'timer6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c: In function 'in6_inithead': /src/sys/netinet6/in6_rmx.c:472: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:472: error: 'timer6' undeclared (first use in this function) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 03:28:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 03:28:44 - ERROR: failed to build lint kernel TB --- 2008-06-29 03:28:44 - tinderbox aborted TB --- 3150.33 user 392.81 system 4225.42 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 03:48:12 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B60F01065673; Sun, 29 Jun 2008 03:48:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 7B1B88FC1D; Sun, 29 Jun 2008 03:48:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T3mAtg092799; Sat, 28 Jun 2008 23:48:10 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T3mAnn080055; Sat, 28 Jun 2008 23:48:10 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4E8C773039; Sat, 28 Jun 2008 23:48:10 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629034810.4E8C773039@freebsd-current.sentex.ca> Date: Sat, 28 Jun 2008 23:48:10 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 03:48:13 -0000 TB --- 2008-06-29 02:41:04 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 02:41:04 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-06-29 02:41:04 - cleaning the object tree TB --- 2008-06-29 02:41:29 - cvsupping the source tree TB --- 2008-06-29 02:41:29 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-06-29 02:41:36 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 02:41:36 - cd /src TB --- 2008-06-29 02:41:36 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 02:41:37 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 03:42:42 UTC 2008 TB --- 2008-06-29 03:42:42 - generating LINT kernel config TB --- 2008-06-29 03:42:42 - cd /src/sys/sun4v/conf TB --- 2008-06-29 03:42:42 - /usr/bin/make -B LINT TB --- 2008-06-29 03:42:42 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 03:42:42 - cd /src TB --- 2008-06-29 03:42:42 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 03:42:42 UTC 2008 >>> 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 [...] /src/sys/netinet6/in6_rmx.c:337: error: 'rtq_timeout6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:337: error: (Each undeclared identifier is reported only once /src/sys/netinet6/in6_rmx.c:337: error: for each function it appears in.) /src/sys/netinet6/in6_rmx.c:373: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:373: error: 'timer6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c: In function 'in6_inithead': /src/sys/netinet6/in6_rmx.c:472: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:472: error: 'timer6' undeclared (first use in this function) *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 03:48:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 03:48:10 - ERROR: failed to build lint kernel TB --- 2008-06-29 03:48:10 - tinderbox aborted TB --- 3146.26 user 386.34 system 4025.56 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 05:14:12 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83D71106564A for ; Sun, 29 Jun 2008 05:14:12 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 068748FC1B for ; Sun, 29 Jun 2008 05:14:11 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m5T5DfOf022660; Sun, 29 Jun 2008 09:13:41 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 29 Jun 2008 09:13:41 +0400 (MSD) From: Dmitry Morozovsky To: Garrett Cooper In-Reply-To: <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> Message-ID: <20080629091151.H89957@woozle.rinet.ru> References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sun, 29 Jun 2008 09:13:42 +0400 (MSD) Cc: ed@80386.nl, current@freebsd.org, Derek Ragona , =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 05:14:12 -0000 On Sat, 28 Jun 2008, Garrett Cooper wrote: [snip all] GC> Oh, where's this "document" of which you speak all the time? I don't GC> see anything about parity support not being available in either the GC> geom or iir manpage, or the iir sourcecode. If someone needs a helping GC> hand inserting that logic into the kernel, I'll gladly assist so GC> others don't follow my footsteps and fsck up their data. It seems that you constantly mixing ata and iir, which you think you have. Have you any kernel logs available? Can you show us the lines about disks and arrays? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 05:35:44 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F5BB106564A; Sun, 29 Jun 2008 05:35:44 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 44BA68FC1A; Sun, 29 Jun 2008 05:35:44 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T5ZfKx000109; Sun, 29 Jun 2008 01:35:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T5ZfBa051751; Sun, 29 Jun 2008 01:35:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2E35673039; Sun, 29 Jun 2008 01:35:41 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629053541.2E35673039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 01:35:41 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 05:35:44 -0000 TB --- 2008-06-29 03:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 03:50:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-29 03:50:00 - cleaning the object tree TB --- 2008-06-29 03:50:52 - cvsupping the source tree TB --- 2008-06-29 03:50:52 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-29 03:50:59 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 03:50:59 - cd /src TB --- 2008-06-29 03:50:59 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 03:51:01 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Jun 29 05:27:19 UTC 2008 TB --- 2008-06-29 05:27:19 - generating LINT kernel config TB --- 2008-06-29 05:27:19 - cd /src/sys/amd64/conf TB --- 2008-06-29 05:27:19 - /usr/bin/make -B LINT TB --- 2008-06-29 05:27:19 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 05:27:19 - cd /src TB --- 2008-06-29 05:27:19 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 05:27:19 UTC 2008 >>> 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 [...] /src/sys/netinet6/in6_rmx.c:337: error: 'rtq_timeout6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:337: error: (Each undeclared identifier is reported only once /src/sys/netinet6/in6_rmx.c:337: error: for each function it appears in.) /src/sys/netinet6/in6_rmx.c:373: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:373: error: 'timer6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c: In function 'in6_inithead': /src/sys/netinet6/in6_rmx.c:472: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:472: error: 'timer6' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 05:35:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 05:35:40 - ERROR: failed to build lint kernel TB --- 2008-06-29 05:35:40 - tinderbox aborted TB --- 4732.38 user 603.80 system 6340.09 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 06:09:20 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFA3B106566B; Sun, 29 Jun 2008 06:09:20 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id A79C28FC16; Sun, 29 Jun 2008 06:09:20 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T69IOO003371; Sun, 29 Jun 2008 02:09:18 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T69IQq092464; Sun, 29 Jun 2008 02:09:18 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E5E5573039; Sun, 29 Jun 2008 02:09:17 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629060917.E5E5573039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 02:09:17 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 06:09:20 -0000 TB --- 2008-06-29 04:53:55 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 04:53:55 - starting HEAD tinderbox run for i386/i386 TB --- 2008-06-29 04:53:55 - cleaning the object tree TB --- 2008-06-29 04:54:33 - cvsupping the source tree TB --- 2008-06-29 04:54:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/i386/supfile TB --- 2008-06-29 04:54:39 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 04:54:39 - cd /src TB --- 2008-06-29 04:54:39 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 04:54:41 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 06:00:52 UTC 2008 TB --- 2008-06-29 06:00:52 - generating LINT kernel config TB --- 2008-06-29 06:00:52 - cd /src/sys/i386/conf TB --- 2008-06-29 06:00:52 - /usr/bin/make -B LINT TB --- 2008-06-29 06:00:52 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 06:00:52 - cd /src TB --- 2008-06-29 06:00:52 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 06:00:52 UTC 2008 >>> 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 [...] ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet6/ip6_output.c ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet6/ip6_ipsec.c /src/sys/netinet6/ip6_ipsec.c: In function 'ip6_ipsec_fwd': /src/sys/netinet6/ip6_ipsec.c:131: error: 'ip6stat' undeclared (first use in this function) /src/sys/netinet6/ip6_ipsec.c:131: error: (Each undeclared identifier is reported only once /src/sys/netinet6/ip6_ipsec.c:131: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 06:09:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 06:09:16 - ERROR: failed to build lint kernel TB --- 2008-06-29 06:09:16 - tinderbox aborted TB --- 3384.45 user 415.38 system 4521.01 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 06:50:05 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA638106567C; Sun, 29 Jun 2008 06:50:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id C17188FC0C; Sun, 29 Jun 2008 06:50:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T6o2ke004892; Sun, 29 Jun 2008 02:50:02 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T6o2sk080738; Sun, 29 Jun 2008 02:50:02 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E2DD773039; Sun, 29 Jun 2008 02:50:00 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629065000.E2DD773039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 02:50:00 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 06:50:06 -0000 TB --- 2008-06-29 05:35:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 05:35:41 - starting HEAD tinderbox run for i386/pc98 TB --- 2008-06-29 05:35:41 - cleaning the object tree TB --- 2008-06-29 05:36:11 - cvsupping the source tree TB --- 2008-06-29 05:36:11 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/pc98/supfile TB --- 2008-06-29 05:36:17 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 05:36:17 - cd /src TB --- 2008-06-29 05:36:17 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 05:36:20 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 06:42:21 UTC 2008 TB --- 2008-06-29 06:42:21 - generating LINT kernel config TB --- 2008-06-29 06:42:21 - cd /src/sys/pc98/conf TB --- 2008-06-29 06:42:21 - /usr/bin/make -B LINT TB --- 2008-06-29 06:42:21 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 06:42:21 - cd /src TB --- 2008-06-29 06:42:21 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 06:42:21 UTC 2008 >>> 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 [...] ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet6/ip6_output.c ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet6/ip6_ipsec.c /src/sys/netinet6/ip6_ipsec.c: In function 'ip6_ipsec_fwd': /src/sys/netinet6/ip6_ipsec.c:131: error: 'ip6stat' undeclared (first use in this function) /src/sys/netinet6/ip6_ipsec.c:131: error: (Each undeclared identifier is reported only once /src/sys/netinet6/ip6_ipsec.c:131: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 06:50:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 06:50:00 - ERROR: failed to build lint kernel TB --- 2008-06-29 06:50:00 - tinderbox aborted TB --- 3317.08 user 418.06 system 4459.65 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 07:36:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 876621065670; Sun, 29 Jun 2008 07:36:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5EDE98FC17; Sun, 29 Jun 2008 07:36:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T7ZwYh008496; Sun, 29 Jun 2008 03:35:58 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T7ZwDH018084; Sun, 29 Jun 2008 03:35:58 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 49BD173039; Sun, 29 Jun 2008 03:35:58 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629073558.49BD173039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 03:35:58 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 07:36:00 -0000 TB --- 2008-06-29 06:09:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 06:09:18 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-06-29 06:09:18 - cleaning the object tree TB --- 2008-06-29 06:09:53 - cvsupping the source tree TB --- 2008-06-29 06:09:53 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-06-29 06:09:59 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 06:09:59 - cd /src TB --- 2008-06-29 06:09:59 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 06:10:02 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 07:27:13 UTC 2008 TB --- 2008-06-29 07:27:13 - generating LINT kernel config TB --- 2008-06-29 07:27:13 - cd /src/sys/ia64/conf TB --- 2008-06-29 07:27:13 - /usr/bin/make -B LINT TB --- 2008-06-29 07:27:13 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 07:27:13 - cd /src TB --- 2008-06-29 07:27:13 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 07:27:13 UTC 2008 >>> 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 [...] ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/netinet6/ip6_output.c ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/netinet6/ip6_ipsec.c /src/sys/netinet6/ip6_ipsec.c: In function 'ip6_ipsec_fwd': /src/sys/netinet6/ip6_ipsec.c:131: error: 'ip6stat' undeclared (first use in this function) /src/sys/netinet6/ip6_ipsec.c:131: error: (Each undeclared identifier is reported only once /src/sys/netinet6/ip6_ipsec.c:131: error: for each function it appears in.) *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 07:35:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 07:35:58 - ERROR: failed to build lint kernel TB --- 2008-06-29 07:35:58 - tinderbox aborted TB --- 3871.62 user 416.45 system 5200.12 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 08:04:55 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F3EC1065670; Sun, 29 Jun 2008 08:04:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 363F98FC13; Sun, 29 Jun 2008 08:04:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T84qYU009882; Sun, 29 Jun 2008 04:04:52 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T84qfl035057; Sun, 29 Jun 2008 04:04:52 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3B4DA73039; Sun, 29 Jun 2008 04:04:52 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629080452.3B4DA73039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 04:04:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 08:04:55 -0000 TB --- 2008-06-29 06:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 06:50:00 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-06-29 06:50:02 - cleaning the object tree TB --- 2008-06-29 06:50:22 - cvsupping the source tree TB --- 2008-06-29 06:50:22 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-06-29 06:50:29 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 06:50:29 - cd /src TB --- 2008-06-29 06:50:29 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 06:50:31 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 07:58:36 UTC 2008 TB --- 2008-06-29 07:58:36 - generating LINT kernel config TB --- 2008-06-29 07:58:36 - cd /src/sys/powerpc/conf TB --- 2008-06-29 07:58:36 - /usr/bin/make -B LINT TB --- 2008-06-29 07:58:36 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 07:58:36 - cd /src TB --- 2008-06-29 07:58:36 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 07:58:36 UTC 2008 >>> 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 [...] ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/netinet6/ip6_output.c ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/netinet6/ip6_ipsec.c /src/sys/netinet6/ip6_ipsec.c: In function 'ip6_ipsec_fwd': /src/sys/netinet6/ip6_ipsec.c:131: error: 'ip6stat' undeclared (first use in this function) /src/sys/netinet6/ip6_ipsec.c:131: error: (Each undeclared identifier is reported only once /src/sys/netinet6/ip6_ipsec.c:131: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 08:04:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 08:04:51 - ERROR: failed to build lint kernel TB --- 2008-06-29 08:04:51 - tinderbox aborted TB --- 3332.37 user 394.81 system 4490.05 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 08:46:58 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB190106566B; Sun, 29 Jun 2008 08:46:58 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8298B8FC18; Sun, 29 Jun 2008 08:46:58 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T8kuCT011996; Sun, 29 Jun 2008 04:46:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m5T8kuxG054975; Sun, 29 Jun 2008 04:46:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D36B173039; Sun, 29 Jun 2008 04:46:55 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080629084655.D36B173039@freebsd-current.sentex.ca> Date: Sun, 29 Jun 2008 04:46:55 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 08:46:58 -0000 TB --- 2008-06-29 07:35:58 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 07:35:58 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-06-29 07:35:58 - cleaning the object tree TB --- 2008-06-29 07:36:15 - cvsupping the source tree TB --- 2008-06-29 07:36:15 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-06-29 07:36:21 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 07:36:21 - cd /src TB --- 2008-06-29 07:36:21 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 07:36:23 UTC 2008 >>> 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 >>> World build completed on Sun Jun 29 08:39:56 UTC 2008 TB --- 2008-06-29 08:39:56 - generating LINT kernel config TB --- 2008-06-29 08:39:56 - cd /src/sys/sparc64/conf TB --- 2008-06-29 08:39:56 - /usr/bin/make -B LINT TB --- 2008-06-29 08:39:56 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 08:39:56 - cd /src TB --- 2008-06-29 08:39:56 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 08:39:57 UTC 2008 >>> 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 [...] ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/netinet6/ip6_output.c ${NORMAL_CTFCONVERT} expands to empty string cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/netinet6/ip6_ipsec.c /src/sys/netinet6/ip6_ipsec.c: In function 'ip6_ipsec_fwd': /src/sys/netinet6/ip6_ipsec.c:131: error: 'ip6stat' undeclared (first use in this function) /src/sys/netinet6/ip6_ipsec.c:131: error: (Each undeclared identifier is reported only once /src/sys/netinet6/ip6_ipsec.c:131: error: for each function it appears in.) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 08:46:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 08:46:55 - ERROR: failed to build lint kernel TB --- 2008-06-29 08:46:55 - tinderbox aborted TB --- 3154.70 user 389.63 system 4257.27 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 11:09:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42C4E106568E for ; Sun, 29 Jun 2008 11:09:55 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F3528FC1A for ; Sun, 29 Jun 2008 11:09:54 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48676D80.9010409@FreeBSD.org> Date: Sun, 29 Jun 2008 13:09:52 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 11:09:55 -0000 I am frequently getting this when trying to minidump on amd64: Physical memory: 8168 MB Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 1062 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 806 790 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 534 518 502 486 470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt to write outside dump device boundaries. ** DUMP FAILED (ERROR 6) ** = 0 Kris From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 11:22:49 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 693001065676 for ; Sun, 29 Jun 2008 11:22:49 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id 414C08FC1B for ; Sun, 29 Jun 2008 11:22:47 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from laptop.deepcore.dk (laptop.deepcore.dk [192.168.0.138]) by deepcore.dk (8.14.2/8.13.8) with ESMTP id m5TBMOex057703; Sun, 29 Jun 2008 13:22:27 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) Message-Id: <5AAEE9BE-4A44-46EE-9913-16BEC21802D2@FreeBSD.ORG> From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: "Garrett Cooper" In-Reply-To: <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v924) Date: Sun, 29 Jun 2008 13:22:24 +0200 References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> X-Mailer: Apple Mail (2.924) Cc: ed@80386.nl, current@FreeBSD.ORG, Derek Ragona Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 11:22:49 -0000 On 29Jun, 2008, at 5:11 , Garrett Cooper wrote: >> >> I hate to bring this to you, but you will not have an intact =20 >> filesystem when >> the rebuild is done, you have no parity data to rebuild from, just =20= >> as the >> docs states. >> >> -S=F8ren > > Just as you predicted, the disk(s) are unreadable still, even after > the rebuild (and I hope to hell that it didn't destroy/disturb any > data on the surviving members). > > I may just have to get it sent off for recovery (after I dd the > remaining members because there's still some usable data there -- > bloody 2.7TB ... grr) -- apart from that I don't think I have a > choice. You wont get anything from that except a huge bill for nothing. > Oh, where's this "document" of which you speak all the time? I don't > see anything about parity support not being available in either the > geom or iir manpage, or the iir sourcecode. If someone needs a helping > hand inserting that logic into the kernel, I'll gladly assist so > others don't follow my footsteps and fsck up their data. > Would you please try to read what I write to you ? You still insist in mixing up ATA and IIR, it is two distinct drivers =20= for different HW and with very different properties. For ATA docs just use "man ata" and it will show you the way. Shortcut to the raid part is "man ataraid". > For once I wish I had been running Linux or Windows (at least) :(... Oooohhh, that one is soooo tempting..... 8^) -S=F8ren From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 11:24:16 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 344F71065672 for ; Sun, 29 Jun 2008 11:24:16 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.freebsd.org (Postfix) with ESMTP id 879E58FC0A for ; Sun, 29 Jun 2008 11:24:15 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 8270 invoked by uid 89); 29 Jun 2008 10:57:33 -0000 Received: by simscan 1.1.0 ppid: 8250, pid: 8256, t: 3.9494s scanners: attach: 1.1.0 clamav: 0.88.7/m:44/d:4673 spam: 3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by bsd.ultra-secure.de with (AES128-SHA encrypted) SMTP; 29 Jun 2008 10:57:29 -0000 In-Reply-To: <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Rainer Duffner Date: Sun, 29 Jun 2008 12:57:20 +0200 To: Garrett Cooper X-Mailer: Apple Mail (2.753.1) Cc: current@freebsd.org Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 11:24:16 -0000 Am 29.06.2008 um 05:11 schrieb Garrett Cooper: > > Just as you predicted, the disk(s) are unreadable still, even after > the rebuild (and I hope to hell that it didn't destroy/disturb any > data on the surviving members). > > I may just have to get it sent off for recovery (after I dd the > remaining members because there's still some usable data there -- > bloody 2.7TB ... grr) -- apart from that I don't think I have a > choice. If the data was worth so much that it values recovery.... > > Oh, where's this "document" of which you speak all the time? I don't > see anything about parity support not being available in either the > geom or iir manpage, or the iir sourcecode. If someone needs a helping > hand inserting that logic into the kernel, I'll gladly assist so > others don't follow my footsteps and fsck up their data. > On our HP DL320G5s, FreeBSD7 didn't even detect the MatrixRAID array (RAID1). Even the Windoze-guys tell us that they don't trust it. So we settled for RAID1 via gmirror. MatrixRAID is a scam, if you ask me - like all the other BIOS-RAIDs we have had the displeasure to see over the years. I really thought it was common knowledge. But now that you mention it, I can't find a reference to this in the FreeBSD docs (at least not with a quick look). The handbook-example uses RAID1, though. Rainer -- Rainer Duffner CISSP, LPI, MCSE rainer@ultra-secure.de From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 11:55:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44384106567F; Sun, 29 Jun 2008 11:55:39 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id F0BE68FC19; Sun, 29 Jun 2008 11:55:38 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from [87.242.97.68] (port=63329 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1KCut4-000HN8-Pl; Sun, 29 Jun 2008 11:16:06 +0000 Date: Sun, 29 Jun 2008 15:15:47 +0400 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20080629111547.GC58634@edoofus.dev.vega.ru> References: <48676D80.9010409@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48676D80.9010409@FreeBSD.org> Cc: FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 11:55:39 -0000 On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: > I am frequently getting this when trying to minidump on amd64: > > Physical memory: 8168 MB > Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 1958 > 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 1734 > 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 1510 > 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 1286 > 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 1062 > 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 806 790 > 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 534 518 502 > 486 470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 > 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt to write outside > dump device boundaries. > > ** DUMP FAILED (ERROR 6) ** > = 0 > Yes, it happens most often on SMP machines. Previously it could overwrite data on your disk (in our case it destroyed GEOM mirrors). Now the attempt is logged and prevented. What's your question? ;) Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 12:06:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E58B11065675; Sun, 29 Jun 2008 12:06:44 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3D45B8FC14; Sun, 29 Jun 2008 12:06:44 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48677AD2.7030002@FreeBSD.org> Date: Sun, 29 Jun 2008 14:06:42 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Ruslan Ermilov References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> In-Reply-To: <20080629111547.GC58634@edoofus.dev.vega.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 12:06:45 -0000 Ruslan Ermilov wrote: > On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >> I am frequently getting this when trying to minidump on amd64: >> >> Physical memory: 8168 MB >> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 1958 >> 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 1734 >> 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 1510 >> 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 1286 >> 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 1062 >> 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 806 790 >> 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 534 518 502 >> 486 470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 >> 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt to write outside >> dump device boundaries. >> >> ** DUMP FAILED (ERROR 6) ** >> = 0 >> > Yes, it happens most often on SMP machines. Previously it could > overwrite data on your disk (in our case it destroyed GEOM mirrors). > Now the attempt is logged and prevented. > > What's your question? ;) I'd have thought it was obvious: "why?" Kris From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 12:35:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A6B51065672 for ; Sun, 29 Jun 2008 12:35:51 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id D6DAC8FC16 for ; Sun, 29 Jun 2008 12:35:50 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m5TCKko0030550; Sun, 29 Jun 2008 16:20:46 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 29 Jun 2008 16:20:46 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <48677AD2.7030002@FreeBSD.org> Message-ID: <20080629162016.P89957@woozle.rinet.ru> References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sun, 29 Jun 2008 16:20:46 +0400 (MSD) Cc: FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 12:35:51 -0000 On Sun, 29 Jun 2008, Kris Kennaway wrote: KK> > > 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt to write outside KK> > > dump device boundaries. KK> > > KK> > > ** DUMP FAILED (ERROR 6) ** KK> > > = 0 KK> > > KK> > Yes, it happens most often on SMP machines. Previously it could KK> > overwrite data on your disk (in our case it destroyed GEOM mirrors). KK> > Now the attempt is logged and prevented. KK> > KK> > What's your question? ;) KK> KK> I'd have thought it was obvious: "why?" Or, more prcise: "How?!" to ru@: ;-P Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 13:06:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 198811065670; Sun, 29 Jun 2008 13:06:08 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id C89BB8FC12; Sun, 29 Jun 2008 13:06:07 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.216.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 747D88A0F85; Sun, 29 Jun 2008 14:42:45 +0200 (CEST) Message-ID: <48678334.9070500@bsdforen.de> Date: Sun, 29 Jun 2008 14:42:28 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.14 (X11/20080607) MIME-Version: 1.0 To: Kris Kennaway References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> In-Reply-To: <48677AD2.7030002@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Ruslan Ermilov Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 13:06:08 -0000 Kris Kennaway wrote: > Ruslan Ermilov wrote: >> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>> I am frequently getting this when trying to minidump on amd64: >>> >>> Physical memory: 8168 MB >>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 >>> 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 >>> 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 >>> 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 >>> 1062 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 >>> 806 790 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 >>> 534 518 502 486 470 454 438 422 406 390 374 358 342 326 310 294 278 >>> 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt >>> to write outside dump device boundaries. >>> >>> ** DUMP FAILED (ERROR 6) ** >>> = 0 >>> >> Yes, it happens most often on SMP machines. Previously it could >> overwrite data on your disk (in our case it destroyed GEOM mirrors). >> Now the attempt is logged and prevented. >> >> What's your question? ;) > > I'd have thought it was obvious: "why?" > > Kris Not enough swap space? From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 13:13:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B96B1065671; Sun, 29 Jun 2008 13:13:42 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DB8198FC1F; Sun, 29 Jun 2008 13:13:40 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48678A82.50002@FreeBSD.org> Date: Sun, 29 Jun 2008 15:13:38 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Dominic Fandrey References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> <48678334.9070500@bsdforen.de> In-Reply-To: <48678334.9070500@bsdforen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Ruslan Ermilov Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 13:13:42 -0000 Dominic Fandrey wrote: > Kris Kennaway wrote: >> Ruslan Ermilov wrote: >>> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>>> I am frequently getting this when trying to minidump on amd64: >>>> >>>> Physical memory: 8168 MB >>>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 >>>> 1750 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 >>>> 1542 1526 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 >>>> 1334 1318 1302 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 >>>> 1126 1110 1094 1078 1062 1046 1030 1014 998 982 966 950 934 918 902 >>>> 886 870 854 838 822 806 790 774 758 742 726 710 694 678 662 646 630 >>>> 614 598 582 566 550 534 518 502 486 470 454 438 422 406 390 374 358 >>>> 342 326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 >>>> 70 54 38 22 6Attempt to write outside dump device boundaries. >>>> >>>> ** DUMP FAILED (ERROR 6) ** >>>> = 0 >>>> >>> Yes, it happens most often on SMP machines. Previously it could >>> overwrite data on your disk (in our case it destroyed GEOM mirrors). >>> Now the attempt is logged and prevented. >>> >>> What's your question? ;) >> >> I'd have thought it was obvious: "why?" >> >> Kris > > Not enough swap space? > > No, I have 16GB Kris From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 14:01:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9D6A106567E for ; Sun, 29 Jun 2008 14:01:59 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 88BEC8FC2C for ; Sun, 29 Jun 2008 14:01:59 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: by wf-out-1314.google.com with SMTP id 24so1042944wfg.7 for ; Sun, 29 Jun 2008 07:01:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=M8M/8rBOw9GUWLkADk/phGIWg9ZTBzAvKbbWjDkq/qU=; b=TDU7WlxcGP4XXBfq441GJAFSng3nuzDw2XuiirZKsvQqkvpshLOxV34I1yk3w1rhoH FYez6dbxQxURNxloc98iTxtbEsywQF5WyC44U5dIXYUhCPE9JryptNYAbF7/SkvaeNmb bUpH7pBB8CL2S2Ejx+DiXzgLg/dE0VWtdUQ+s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=oVxabczpChB9I1HMS4Bo+6CUMDf8Qw3LegvpNPCyYzdtJ3mD9KuN3SWqueptmGwxMV azFsltG/2cpFIJEybAvqnxwhu8ZMoQpcD12LPF5EhVt/JnNkfdu26T4evUwSlG6aox5o gm9iJbUzub27HtgcT100BqJbgGzcMSu4bCobo= Received: by 10.143.8.10 with SMTP id l10mr1376218wfi.340.1214746634097; Sun, 29 Jun 2008 06:37:14 -0700 (PDT) Received: by 10.142.155.21 with HTTP; Sun, 29 Jun 2008 06:37:14 -0700 (PDT) Message-ID: Date: Sun, 29 Jun 2008 15:37:14 +0200 From: "Vincent Barus" To: "Dimitry Andric" In-Reply-To: <48666CD7.9020706@andric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080607035911.GD4565@cdnetworks.co.kr> <484BC9FB.2040605@andric.com> <20080609012657.GD12521@cdnetworks.co.kr> <484D215A.7050700@andric.com> <20080609123206.GF12521@cdnetworks.co.kr> <484D25CC.9050106@andric.com> <20080610050550.GB17874@cdnetworks.co.kr> <484E9377.2050609@andric.com> <20080611005814.GA3529@cdnetworks.co.kr> <48666CD7.9020706@andric.com> Cc: freebsd-current@freebsd.org Subject: Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 14:01:59 -0000 On Sat, Jun 28, 2008 at 6:54 PM, Dimitry Andric wrote: > On 2008-06-11 02:58, Pyun YongHyeon wrote: >> > This seems to work better, although it still takes quite some time >> > (~10s) for the interfaces to go up at boot time. I haven't yet been >> > able to get them "stuck", however, so that's good. :) >> Hmm, that's interesting. Can you spot where re(4) spends its time? >> Did RELENG_7 also have this issue? > > Apparently it's experiencing timeouts, I usually get these: > > re0: link state changed to DOWN > re0: watchdog timeout > re0: 3 link states coalesced > re0: link state changed to UP > re1: link state changed to DOWN > > I've been running all tests under RELENG_7, btw. Note also, these > delays don't always happen, in some cases the interfaces react very > quickly. In rare cases, they don't work at all, until you manually > ifconfig down and up them a few times. > > What's funny though, is that the interfaces seem to start in DOWN mode: > > [...booting...] > Mounting local file systems:. > Setting hostname: tensor.andric.com. > re0: link state changed to DOWN > re1: link state changed to DOWN > lo0: flags=8049 metric 0 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 > inet 127.0.0.1 netmask 0xff000000 > re0: flags=8843 metric 0 mtu 1500 > options=399b > ether 00:30:18:a6:f1:a8 > inet6 fe80::230:18ff:fea6:f1a8%re0 prefixlen 64 tentative scopeid 0x1 > inet 87.251.56.140 netmask 0xffffffc0 broadcast 87.251.56.191 > media: Ethernet autoselect (none) > status: no carrier > re1: flags=8843 metric 0 mtu 1500 > options=399b > ether 00:30:18:a6:f1:a9 > inet6 fe80::230:18ff:fea6:f1a9%re1 prefixlen 64 tentative scopeid 0x2 > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (none) > status: no carrier > [...more initialization...] > net.inet6.ip6.forwarding: 0 -> 1 > net.inet6.ip6.accept_rtadv: 0 -> 0 > re0: link state changed to UP > re1: link state changed to UP > > and only then do they "really" go up... :) > > Do you have any good suggestions on where I could put some debug > printfs in re to find out what it's timing out on? > > >> Plugging/unplugging UTP cable to ethernet controller during boot >> change the long delay? How about disabling WOL before system >> shutdown?(e.g. ifconfig re0 -wol) > > Plugging/unplugging the cable doesn't seem to make much difference, and > neither does disabling WOL before shutdown (or altogether)... > > _______________________________________________ > 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" > Hi Dimitry, what happens if you load the if_re module after you logged in instead of loading it while boot time? I get a watchdog every time with a boot time loaded if_re, so maybe this is not affecting you too. Regards, vb From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 14:13:50 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0443F1065672; Sun, 29 Jun 2008 14:13:50 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id 4C6108FC20; Sun, 29 Jun 2008 14:13:49 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjsFAC8zZ0h5La3N/2dsb2JhbACBW6x5 X-IronPort-AV: E=Sophos;i="4.27,722,1204464600"; d="scan'208";a="138033144" Received: from ppp121-45-173-205.lns11.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.173.205]) by ipmail01.adl6.internode.on.net with ESMTP; 29 Jun 2008 23:43:45 +0930 Received: from [192.168.155.234] (taurus.internal.clearchain.com [192.168.155.234]) (authenticated bits=0) by mail.clearchain.com (8.14.2/8.14.2) with ESMTP id m5TEDhDU025471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Jun 2008 23:43:43 +0930 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <48679898.3000905@clearchain.com> Date: Sun, 29 Jun 2008 23:43:44 +0930 From: Benjamin Close User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Rainer Duffner References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.1, clamav-milter version 0.93.1 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.clearchain.com [192.168.154.1]); Sun, 29 Jun 2008 23:43:44 +0930 (CST) Cc: Garrett Cooper , current@freebsd.org, sos@freebsd.org Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 14:13:50 -0000 Rainer Duffner wrote: > > Am 29.06.2008 um 05:11 schrieb Garrett Cooper: > >> >> Just as you predicted, the disk(s) are unreadable still, even after >> the rebuild (and I hope to hell that it didn't destroy/disturb any >> data on the surviving members). >> >> I may just have to get it sent off for recovery (after I dd the >> remaining members because there's still some usable data there -- >> bloody 2.7TB ... grr) -- apart from that I don't think I have a >> choice. > > > > If the data was worth so much that it values recovery.... > > >> >> Oh, where's this "document" of which you speak all the time? I don't >> see anything about parity support not being available in either the >> geom or iir manpage, or the iir sourcecode. If someone needs a helping >> hand inserting that logic into the kernel, I'll gladly assist so >> others don't follow my footsteps and fsck up their data. >> > > > On our HP DL320G5s, FreeBSD7 didn't even detect the MatrixRAID array > (RAID1). > Even the Windoze-guys tell us that they don't trust it. > > So we settled for RAID1 via gmirror. > > MatrixRAID is a scam, if you ask me - like all the other BIOS-RAIDs we > have had the displeasure to see over the years. > I really thought it was common knowledge. But now that you mention > it, I can't find a reference to this in the FreeBSD docs (at least not > with a quick look). > The handbook-example uses RAID1, though. Perhaps a lesson as developers we should take from this, is to put a warning in ata about raid5. It's fooled Garret into believing he had a raid5, how many others are also using ata believing their raid5 is a raid5. We should warn people in the future rather than just saying 'its in the docs'. A kernel warning at attach is much more visible. Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 14:43:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C4F51065676; Sun, 29 Jun 2008 14:43:02 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 69A858FC1F; Sun, 29 Jun 2008 14:43:01 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1214749482; x=1215354282; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=GY6uTPVC9tp4Whuy0iOcc 3MTgFEdEjLNOosPgNx6mhw=; b=nR5TuAXM7FzswsdXZwHTF5TS9UCUaNNoKi0rB K2R8UZPG+Un3yz0QlwpVDh5BGR0u7oHYz60XZ2BP0qFK+zav+O9GYEwiqbdMGyME UZfCATgvdh0XRBsI6YnnUnpYRZAdYVWtUx1llkP+/TcpOg/9O7HuqyggWqyglZxA BzPgG0= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50005838617.msg; Sun, 29 Jun 2008 15:24:40 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=10663a81d7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: "Benjamin Close" , "Rainer Duffner" References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <48679898.3000905@clearchain.com> Date: Sun, 29 Jun 2008 15:24:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 15:24:41 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 15:24:42 +0100 Cc: Garrett Cooper , current@freebsd.org, sos@freebsd.org Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 14:43:02 -0000 ----- Original Message ----- From: "Benjamin Close" > Perhaps a lesson as developers we should take from this, is to put a > warning in ata about raid5. It's fooled Garret into believing he had a > raid5, how many others are also using ata believing their raid5 is a > raid5. We should warn people in the future rather than just saying 'its > in the docs'. A kernel warning at attach is much more visible. Although it is more visible, personally I would prefer it to just fail instead of proceeding. RAID5 is not RAID5 without parity so why even allow it to continue and hence risk such an unrecoverable situation? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 15:02:31 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A2F21065670; Sun, 29 Jun 2008 15:02:31 +0000 (UTC) (envelope-from ru@freebsd.org) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id D52948FC1C; Sun, 29 Jun 2008 15:02:30 +0000 (UTC) (envelope-from ru@freebsd.org) Received: from [87.242.97.68] (port=52132 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1KCyQ8-0009oP-Jm; Sun, 29 Jun 2008 15:02:28 +0000 Date: Sun, 29 Jun 2008 19:02:09 +0400 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20080629150209.GB78422@edoofus.dev.vega.ru> References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48677AD2.7030002@FreeBSD.org> Cc: FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 15:02:31 -0000 On Sun, Jun 29, 2008 at 02:06:42PM +0200, Kris Kennaway wrote: > Ruslan Ermilov wrote: > > On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: > >> I am frequently getting this when trying to minidump on amd64: > >> > >> Physical memory: 8168 MB > >> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 1958 > >> 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 1734 > >> 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 1510 > >> 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 1286 > >> 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 1062 > >> 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 806 790 > >> 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 534 518 502 > >> 486 470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 > >> 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt to write outside > >> dump device boundaries. > >> > >> ** DUMP FAILED (ERROR 6) ** > >> = 0 > >> > > Yes, it happens most often on SMP machines. Previously it could > > overwrite data on your disk (in our case it destroyed GEOM mirrors). > > Now the attempt is logged and prevented. > > > > What's your question? ;) > > I'd have thought it was obvious: "why?" > http://lists.freebsd.org/pipermail/freebsd-current/2008-January/082752.html Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 16:09:47 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E855C10656AF for ; Sun, 29 Jun 2008 16:09:47 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id A653E8FC15 for ; Sun, 29 Jun 2008 16:09:47 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m5TG9jR9021194; Sun, 29 Jun 2008 11:09:45 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Sun, 29 Jun 2008 11:09:45 -0500 (CDT) From: "Sean C. Farley" To: Rainer Duffner In-Reply-To: Message-ID: References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.farley.org Cc: current@FreeBSD.org Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 16:09:48 -0000 On Sun, 29 Jun 2008, Rainer Duffner wrote: *snip* > On our HP DL320G5s, FreeBSD7 didn't even detect the MatrixRAID array > (RAID1). Even the Windoze-guys tell us that they don't trust it. > > So we settled for RAID1 via gmirror. > > MatrixRAID is a scam, if you ask me - like all the other BIOS-RAIDs we > have had the displeasure to see over the years. I have been using the Intel MatrixRAID (ICH9R) with RAID1 successfully. Already, I have had to replace one drive, and the rebuild worked. The only reason I used it instead of gmirror, which I use on another system (FreeBSD-only), is that it allows the whole drive to be mirrored regardless of what other OS's I have installed. What other inexpensive (cheap! :)) and reliable (assuming MatrixRAID counts) whole-disk (SATA) mirroring solutions exist? The cheapest I found on NewEgg is Syba ($12). Personally, I have never heard of the brand. Is what you can get in the $12-30 range any better than MatrixRAID? Would they be any faster? Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 16:09:50 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2352F1065680 for ; Sun, 29 Jun 2008 16:09:50 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id 11B578FC14 for ; Sun, 29 Jun 2008 16:09:48 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from laptop.deepcore.dk (laptop.deepcore.dk [192.168.0.138]) by deepcore.dk (8.14.2/8.13.8) with ESMTP id m5TG9WKr075736; Sun, 29 Jun 2008 18:09:35 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: Steven Hartland In-Reply-To: X-Priority: 3 References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <48679898.3000905@clearchain.com> Message-Id: <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v924) Date: Sun, 29 Jun 2008 18:09:31 +0200 X-Mailer: Apple Mail (2.924) Cc: Garrett Cooper , Benjamin Close , current@FreeBSD.ORG, Rainer Duffner Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 16:09:50 -0000 On 29Jun, 2008, at 16:24 , Steven Hartland wrote: > > ----- Original Message ----- From: "Benjamin Close" = > > >> Perhaps a lesson as developers we should take from this, is to put =20= >> a warning in ata about raid5. It's fooled Garret into believing he =20= >> had a raid5, how many others are also using ata believing their =20 >> raid5 is a raid5. We should warn people in the future rather than =20 >> just saying 'its in the docs'. A kernel warning at attach is much =20 >> more visible. > > Although it is more visible, personally I would prefer it to just fail > instead of proceeding. RAID5 is not RAID5 without parity so why even > allow it to continue and hence risk such an unrecoverable situation? Well, this has been rehashed many times before, it has been disabled, =20= put a warning in the boot log, warning in the docs, all 3 was the =20 favorite at the time it was done. I'm all ears for what the decision might be this time, just get =20 consensus and I'll flip the right switch. -S=F8ren From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 17:01:26 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F40C106567B for ; Sun, 29 Jun 2008 17:01:26 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 855608FC14 for ; Sun, 29 Jun 2008 17:01:25 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:59300 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1KD02Z-0000Wy-4U for current@FreeBSD.org; Sun, 29 Jun 2008 18:46:15 +0200 Received: (qmail 45299 invoked from network); 29 Jun 2008 18:39:31 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 29 Jun 2008 18:39:31 +0200 Received: (qmail 21500 invoked by uid 1001); 29 Jun 2008 18:39:31 +0200 Date: Sun, 29 Jun 2008 18:39:31 +0200 From: Erik Trulsson To: "Sean C. Farley" Message-ID: <20080629163931.GA21334@owl.midgard.homeip.net> References: <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1KD02Z-0000Wy-4U. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1KD02Z-0000Wy-4U 70bda1c1897b67553e795258628bd474 Cc: current@FreeBSD.org, Rainer Duffner Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 17:01:26 -0000 On Sun, Jun 29, 2008 at 11:09:45AM -0500, Sean C. Farley wrote: > On Sun, 29 Jun 2008, Rainer Duffner wrote: > > *snip* > > > On our HP DL320G5s, FreeBSD7 didn't even detect the MatrixRAID array > > (RAID1). Even the Windoze-guys tell us that they don't trust it. > > > > So we settled for RAID1 via gmirror. > > > > MatrixRAID is a scam, if you ask me - like all the other BIOS-RAIDs we > > have had the displeasure to see over the years. > > I have been using the Intel MatrixRAID (ICH9R) with RAID1 successfully. > Already, I have had to replace one drive, and the rebuild worked. The > only reason I used it instead of gmirror, which I use on another system > (FreeBSD-only), is that it allows the whole drive to be mirrored > regardless of what other OS's I have installed. > > What other inexpensive (cheap! :)) and reliable (assuming MatrixRAID > counts) whole-disk (SATA) mirroring solutions exist? The cheapest I > found on NewEgg is Syba ($12). Personally, I have never heard of the > brand. Is what you can get in the $12-30 range any better than > MatrixRAID? Would they be any faster? The really cheap stuff will not be any better than MatrixRAID - most of them will be worse. All the cheap RAID solutions (which includes just about all of them that are included on motherboards as well as standalone cards) is just software RAID, where the OS and the CPU has to do all the real work. The only thing they provide over a standard non-RAID controller is that they have a BIOS that understands the RAID format and thus allows you to boot from a RAID volume (and sometimes can rebuild it from within the BIOS.) (For simple mirroring it is not even necessary that the BIOS understands the metadata on the disk to boot from it since both disks are identical and can be used as a normal stand-alone bootdisk.) As for speed and reliability there is no real difference between the different controllers as far as RAID is concerned, since once the OS has started running they are really just standard harddisk controllers. (There are some differences between the controller chips used on different controllers, but most manufacturers don't tell you which chips they are using, so you will have to look at the card to find that out. (Most of the really cheap cards use chips from Silicon Image, which does not have the best reputation in the world for quality.)) When using FreeBSD the ataraid(4) driver understands the metadata used by several of the firmware-based RAID implementations and is what you will have to use if you want to use one of those formats. As has been noted several times it does not support RAID5 though, so if you want that you will have some other solution. One big disadvantage of using any RAID-card (software or hardware-based) is that the metadata on the disks are specific to that brand of controllers. If you move the disks to some other controller it will probably not recognize them as a RAID-array and you will be forced to reinstall from backups. For hardware-based RAID controllers this disadvantage is usually more than offset by extra performance and (especially for the good cards with battery-backed chaches) extra reliability. Such cards are rarely cheap though. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 17:02:50 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E0241065678; Sun, 29 Jun 2008 17:02:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 29C128FC0C; Sun, 29 Jun 2008 17:02:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5FF2146C27; Sun, 29 Jun 2008 13:02:49 -0400 (EDT) Date: Sun, 29 Jun 2008 18:02:49 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: net@FreeBSD.org, current@FreeBSD.org In-Reply-To: <20080524111715.T64552@fledge.watson.org> Message-ID: <20080629180126.F90836@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 17:02:50 -0000 On Sat, 24 May 2008, Robert Watson wrote: > Just as a reminder, we've just about reached the one month date before > IFF_NEEDSGIANT drivers are disabled in the build. You can find a > description of the general problem and list of specific drivers below. > > As USB work is on-going, I will *not* disable the USB drivers at this time, > but all other drivers in the list below will be disabled on 26 June. They > will remain in the tree, easily accessible for patch distribution and > re-enabling, until October, when any remaining non-MPSAFE drivers will be > deleted in 8.x. FreeBSD 8.0 will not ship with compatibility shims to > support non-MPSAFE network device drivers. An FYI on the state of things here: in the last month, John has updated a number of device drivers to be MPSAFE, and the USB work remains in-flight. I'm holding fire a bit on disabling IFF_NEEDSGIANT while things settle and I catch up on driver state, and will likely send out an update next week regarding which device drivers remain on the kill list, and generally what the status of this project is. Robert N M Watson Computer Laboratory University of Cambridge > > Robert N M Watson Computer Laboratory University of Cambridge > > ---------- Forwarded message ---------- > Date: Sun, 3 Feb 2008 20:59:05 +0000 (GMT) > From: Robert Watson > To: arch@FreeBSD.org > Subject: 8.0 network stack MPsafety goals (fwd) > > > Only a few days after predicted, this is a reminder that IFF_NEEDSGIANT > network drivers are going to stop working in the forseeable future. Please > review the attached driver list, and if you depend on or care about a > Giant-dependent device driver, take action to make sure it doesn't remain on > the list in a month's time! > > (As far as I'm aware, the list has not changed since my December posting.) > > Robert N M Watson > Computer Laboratory > University of Cambridge > > ---------- Forwarded message ---------- > Date: Mon, 24 Dec 2007 10:43:28 +0000 (GMT) > From: Robert Watson > To: arch@FreeBSD.org > Subject: 8.0 network stack MPsafety goals > > > Dear all: > > With the 7.0 release around the corner, many developers are starting to think > about (and in quite a few cases, work on) their goals for 8.0. One of our > on-going kernel projects has been the elimination of the Giant lock, and that > project has transformed into one of optimizating behavior on increasing > numbers of processors. > > In 7.0, despite the noteworth accomplishment of eliminating debug.mpsasfenet > and conditional network stack Gian acquisition, we were unable to fully > eliminate the IFF_NEEDSGIANT flag, which controls the conditional acquisition > of the Giant lock around non-MPSAFE network device drivers. Primarily these > drivers are aging ISA network device drivers, although there are some > exceptions, such as the USB stack. > > This e-mail proposes the elimination of the IFF_NEEDSGIANT flag and > associated infrastructure in FreeBSD 8.0, meaning that all network device > drivers must be able to operate without the Giant lock (largely the case > already). Remaining drivers using the IFF_NEEDSGIANT flag must either be > updated, or less ideally, removed. I propose the following schedule: > > Date Goals > ---- ----- > 26 Dec 2007 Post proposed schedule for flag and infrastructure removal > Post affected driver list > > 26 Jan 2008 Repost proposed schedule for flag and infrastructure removal > Post updated affected driver list > > 26 Feb 2008 Adjust boot-time printf for affect drivers to generate a loud > warning. > Post updated affected driver list > > 26 May 2008 Post HEADS UP of impending driver disabling > Post updated affected driver list > > 26 Jun 2008 Disable build of all drivers requiring IFF_NEEDSGIANT > Post updated affected driver list > > 26 Sep 2008 Post HEADS up of impending driver removal > Post updated affected driver list > > 26 Oct 2008 Delete source of all drivers requiring IFF_NEEDSGIANT > Remove flag and infrastructure > > Here is a list of potentially affected drivers: > > Name Bus Man page description > --- --- -------------------- > ar ISA/PCI synchronous Digi/Arnet device driver > arl ISA Aironet Arlan 655 wireless network adapter driver > awi PCCARD AMD PCnetMobile IEEE 802.11 PCMCIA wireless network > driver > axe USB ASIX Electronics AX88172 USB Ethernet driver > cdce USB USB Communication Device Class Ethernet driver > cnw PCCARD Netwave AirSurfer wireless network driver > cs ISA/PCCARD Ethernet device driver > cue USB CATC USB-EL1210A USB Ethernet driver > ex ISA/PCCARD Ethernet device driver for the Intel EtherExpress > Pro/10 and Pro/10+ > fe CBUS/ISA/PCCARD Fujitsu MB86960A/MB86965A based Ethernet adapters > ic I2C I2C bus system > ie ISA Ethernet device driver > kue USB Kawasaki LSI KL5KUSB101B USB Ethernet driver > oltr ISA/PCI Olicom Token Ring device driver > plip PPBUS printer port Internet Protocol driver > ppp TTY point to point protocol network interface > ray PCCARD Raytheon Raylink/Webgear Aviator PCCard driver > rue USB RealTek RTL8150 USB to Fast Ethernet controller > driver > rum USB Ralink Technology USB IEEE 802.11a/b/g wireless > network device > sbni ISA/PCI Granch SBNI12 leased line modem driver > sbsh PCI Granch SBNI16 SHDSL modem device driver > sl TTY slip network interface > snc ISA/PCCARD National Semiconductor DP8393X SONIC Ethernet adapter > driver > sr ISA/PCI synchronous RISCom/N2 / WANic 400/405 device driver > udav USB Davicom DM9601 USB Ethernet driver > ural USB Ralink Technology RT2500USB IEEE 802.11 driver > xe PCCARD Xircom PCMCIA Ethernet device driver > zyd USB ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless > network device > > In some cases, the requirement for Giant is a property of a subsystem the > driver depends on as the driver itself; for example, the tty subsystem for > SLIP and PPP, and the USB subsystem for a number of USB ethernet and wireless > drivers. With most of a year before to go on the proposed schedule, my hope > is that we will have lots of time to address these issues, but wanted to get > a roadmap out from a network protocol stack architecture perspective so that > device driver and subsystem authors could have a schedule in mind. > > FYI, the following drivers also reference IFF_NEEDSGIANT, but only in order > to provide their own conditional MPSAFEty, which can be removed without > affecting device driver functionality (I believe): > > Name Bus Man page description > --- --- -------------------- > ce PCI driver for synchronous Cronyx Tau-PCI/32 WAN adapters > cp PCI driver for synchronous Cronyx Tau-PCI WAN adapters > ctau ISA driver for synchronous Cronyx Tau WAN adapters > cx ISA driver for synchronous/asynchronous Cronyx Sigma WAN > adapters > > Developers and users of the above drivers are heavily encouraged to update > the drivers to remove dependence on Giant, and/or make other contingency > plans. > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 17:08:04 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D3171065682; Sun, 29 Jun 2008 17:08:04 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id D89BC8FC14; Sun, 29 Jun 2008 17:08:03 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1214759118; x=1215363918; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=IxVb7ZdPJPxAPK8dEVIbl 8q6RSgCSWf+GahOBYks7gQ=; b=GWH9CXkGBGeKz9Yhk6pz6C6WCiEocFhUOTvFp 11WRFtQM/r+Df4Dbu+SoVgu8lNLzSPTUlGf5viyha9OXfBEMHrBnf25e9Byjb9VG +8qwu5h9fZNvGexUo1oGVpGuzY8mFhPqUHWM0eNkMyMn3QL8Y9tF/A7dHGb6reAz WC3vO0= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50005838890.msg; Sun, 29 Jun 2008 18:05:16 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=10663a81d7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com><48679898.3000905@clearchain.com> <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> Date: Sun, 29 Jun 2008 18:05:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 18:05:17 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 18:05:18 +0100 Cc: Garrett Cooper , Benjamin Close , current@FreeBSD.ORG, Rainer Duffner Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 17:08:04 -0000 ----- Original Message ----- From: "Søren Schmidt" >> Although it is more visible, personally I would prefer it to just fail >> instead of proceeding. RAID5 is not RAID5 without parity so why even >> allow it to continue and hence risk such an unrecoverable situation? > > Well, this has been rehashed many times before, it has been disabled, put a warning in the boot log, warning in the docs, all 3 > was the favorite at the time it was done. > > I'm all ears for what the decision might be this time, just get consensus and I'll flip the right switch. As a small expansion to this, a good compromise might be to disable it unless a sysctl flag is explicitly set. Similar to how the sysctl kern.geom.debugflags=16 works? Then for those that know the implications they can still have the functionality but prevents someone stumbling into a nasty situation without being aware of the issues. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 17:31:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEFCF1065671 for ; Sun, 29 Jun 2008 17:31:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6D66D8FC0A for ; Sun, 29 Jun 2008 17:31:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:3428:783b:bb0b:47bd] (unknown [IPv6:2001:7b8:3a7:0:3428:783b:bb0b:47bd]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 285723C; Sun, 29 Jun 2008 19:31:14 +0200 (CEST) Message-ID: <4867C6E1.5070205@andric.com> Date: Sun, 29 Jun 2008 19:31:13 +0200 From: Dimitry Andric User-Agent: Thunderbird 2.0.0.16pre (Windows/20080628) MIME-Version: 1.0 To: Vincent Barus References: <20080607035911.GD4565@cdnetworks.co.kr> <484BC9FB.2040605@andric.com> <20080609012657.GD12521@cdnetworks.co.kr> <484D215A.7050700@andric.com> <20080609123206.GF12521@cdnetworks.co.kr> <484D25CC.9050106@andric.com> <20080610050550.GB17874@cdnetworks.co.kr> <484E9377.2050609@andric.com> <20080611005814.GA3529@cdnetworks.co.kr> <48666CD7.9020706@andric.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 17:31:15 -0000 On 2008-06-29 15:37, Vincent Barus wrote: > what happens if you load the if_re module after you logged in instead > of loading it while boot time? It was never a module, it's statically linked into the kernel (both in GENERIC and my custom kernel configuration file). I don't see what kind of difference it would make? > I get a watchdog every time with a boot time loaded if_re, so maybe > this is not affecting you too. If that is really the case, it is a bug that should be fixed, not worked around. :) From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:30:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 546FE106567B for ; Sun, 29 Jun 2008 19:30:38 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outL.internet-mail-service.net (outl.internet-mail-service.net [216.240.47.235]) by mx1.freebsd.org (Postfix) with ESMTP id 3C1698FC1E for ; Sun, 29 Jun 2008 19:30:38 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id C57B3246D; Sun, 29 Jun 2008 12:30:39 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 9C56C2D600D; Sun, 29 Jun 2008 12:30:37 -0700 (PDT) Message-ID: <4867E2EE.3070008@elischer.org> Date: Sun, 29 Jun 2008 12:30:54 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Dominic Fandrey References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> <48678334.9070500@bsdforen.de> In-Reply-To: <48678334.9070500@bsdforen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Kris Kennaway , FreeBSD Current , Ruslan Ermilov Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:30:38 -0000 Dominic Fandrey wrote: > Kris Kennaway wrote: >> Ruslan Ermilov wrote: >>> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>>> I am frequently getting this when trying to minidump on amd64: >>>> >>>> Physical memory: 8168 MB >>>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 >>>> 1750 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 >>>> 1542 1526 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 >>>> 1334 1318 1302 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 >>>> 1126 1110 1094 1078 1062 1046 1030 1014 998 982 966 950 934 918 902 >>>> 886 870 854 838 822 806 790 774 758 742 726 710 694 678 662 646 630 >>>> 614 598 582 566 550 534 518 502 486 470 454 438 422 406 390 374 358 >>>> 342 326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 >>>> 70 54 38 22 6Attempt to write outside dump device boundaries. >>>> >>>> ** DUMP FAILED (ERROR 6) ** >>>> = 0 >>>> >>> Yes, it happens most often on SMP machines. Previously it could >>> overwrite data on your disk (in our case it destroyed GEOM mirrors). >>> Now the attempt is logged and prevented. >>> >>> What's your question? ;) >> >> I'd have thought it was obvious: "why?" >> >> Kris > > Not enough swap space? It used to check that before starting.. did that check get removed? > _______________________________________________ > 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" From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:30:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 622081065677 for ; Sun, 29 Jun 2008 19:30:56 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 8E81B8FC13 for ; Sun, 29 Jun 2008 19:30:55 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so772237fgb.35 for ; Sun, 29 Jun 2008 12:30:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=QlXikIyYXZPj5GJuFrVFavDZauCGdQmFGTJI3SLXhDY=; b=C3j8GlAl92Sbj2jsoJMgwq7OO+E5Q7HqSqQw/HMjzoXdPOaCXfcebY9WGJ6vyA02o5 p+wG83zVXaMQagnNlkD3oIb1voWmPh1rklmBmgWsyiz2NJVO+BEU8wONkbtF/1+kMWQs NtebAnwlAVjVfehjJxNLUhfpM65kOeqC8U+FE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fuwbnGwu4TLiTgF+oNhKE9gy2Ra/mnoJv1cr8cVW4qNHQEqFxgzn/DWGFgsFnYdcZ6 uzTXt/V677RqWheurKE7eDVl7/KbTJs4LABp8w56xVDuaPOXcWGORtewEmhbM1Ptonr8 rDl088cSG7m0MTdYT1x6HygXYw0IhDNcmjGUY= Received: by 10.86.33.19 with SMTP id g19mr2031048fgg.30.1214767854131; Sun, 29 Jun 2008 12:30:54 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sun, 29 Jun 2008 12:30:54 -0700 (PDT) Message-ID: <7d6fde3d0806291230j377fba96s7e014e5d253e6d08@mail.gmail.com> Date: Sun, 29 Jun 2008 12:30:54 -0700 From: "Garrett Cooper" To: "=?ISO-8859-1?Q?S=F8ren_Schmidt?=" In-Reply-To: <5AAEE9BE-4A44-46EE-9913-16BEC21802D2@FreeBSD.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <5AAEE9BE-4A44-46EE-9913-16BEC21802D2@FreeBSD.ORG> Cc: ed@80386.nl, current@freebsd.org, Derek Ragona Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:30:56 -0000 On Sun, Jun 29, 2008 at 4:22 AM, S=F8ren Schmidt wrote: > > On 29Jun, 2008, at 5:11 , Garrett Cooper wrote: >>> >>> I hate to bring this to you, but you will not have an intact filesystem >>> when >>> the rebuild is done, you have no parity data to rebuild from, just as t= he >>> docs states. >>> >>> -S=F8ren >> >> Just as you predicted, the disk(s) are unreadable still, even after >> the rebuild (and I hope to hell that it didn't destroy/disturb any >> data on the surviving members). >> >> I may just have to get it sent off for recovery (after I dd the >> remaining members because there's still some usable data there -- >> bloody 2.7TB ... grr) -- apart from that I don't think I have a >> choice. > > You wont get anything from that except a huge bill for nothing. Why? If the thing was just treated like a RAID0 config (aka a huge single disk), then why would I end up with a huge bill for nothing (confused)? From what I can tell the drive was just defective (purchased it 4 months ago and it looks like the controller card went out), so fixing or replacing the controller card and setting up the bad blocks properly on the new card (if necessary) should solve my issue. >> Oh, where's this "document" of which you speak all the time? I don't >> see anything about parity support not being available in either the >> geom or iir manpage, or the iir sourcecode. If someone needs a helping >> hand inserting that logic into the kernel, I'll gladly assist so >> others don't follow my footsteps and fsck up their data. >> > > Would you please try to read what I write to you ? > > You still insist in mixing up ATA and IIR, it is two distinct drivers for > different HW and with very different properties. > > For ATA docs just use "man ata" and it will show you the way. > Shortcut to the raid part is "man ataraid". Yeah, I finally see what you mean (after reading the ataraid manpage). The funny thing was that (I thought) iir was in place and functioning a while back so I assumed "Hey, it's SCSI/cam supported -- I'm ok!". Boy was I wrong >:(. >> For once I wish I had been running Linux or Windows (at least) :(... > > Oooohhh, that one is soooo tempting..... 8^) Yeah, yeah, I know. I'm just pissed at myself for not backing up my critical data earlier. -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:32:23 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D76371065679 for ; Sun, 29 Jun 2008 19:32:23 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 5958E8FC2B for ; Sun, 29 Jun 2008 19:32:22 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so772505fgb.35 for ; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=dRjCqaHZVSS0Mp6+xGOauynEjGzUnYQ5JkF+cgVN68I=; b=DnIhzz705ozaRzF/qrWqCYC99tK5a76N7uwNP9pNTSPDyhDKQzq3z0bcRj5x/BwId8 qYijXWYYsfT5dnO7j137R62m7wcbmm/I6VBZl07pfhXd9+OTvF3YTE+eni/VC91iKrU8 DlS7DC9OFSAe7PYZ+BYpCds2CUHmXy6PjBnos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SG+DrQIgolIX79464Zlu8nzhMB9UjoK/8T0ulCzVp6BJ3Ui+HTty0c/zbsprVkdRTB Ppa+tIdPx5ZBJHxD0TlFVgwzyQacILfRx4tC20FnVEgK8LM0GfVxmUM0rvmLU+oEWZpm o//NyHgj5XmDYeFTWiNFAupRc6nGLfU9Xjulo= Received: by 10.86.90.2 with SMTP id n2mr5101324fgb.51.1214767941615; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) Message-ID: <7d6fde3d0806291232o407b6391lcd223c2065ffa32c@mail.gmail.com> Date: Sun, 29 Jun 2008 12:32:21 -0700 From: "Garrett Cooper" To: "Steven Hartland" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <48679898.3000905@clearchain.com> <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> Cc: Benjamin Close , current@freebsd.org, Rainer Duffner , =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:32:24 -0000 On Sun, Jun 29, 2008 at 10:05 AM, Steven Hartland wrote: > > ----- Original Message ----- From: "S=F8ren Schmidt" >>> >>> Although it is more visible, personally I would prefer it to just fail >>> instead of proceeding. RAID5 is not RAID5 without parity so why even >>> allow it to continue and hence risk such an unrecoverable situation? >> >> Well, this has been rehashed many times before, it has been disabled, p= ut >> a warning in the boot log, warning in the docs, all 3 was the favorite = at >> the time it was done. >> >> I'm all ears for what the decision might be this time, just get consens= us >> and I'll flip the right switch. > > As a small expansion to this, a good compromise might be to disable it > unless a sysctl flag is explicitly set. Similar to how the sysctl > kern.geom.debugflags=3D16 works? Then for those that know the implication= s > they can still have the functionality but prevents someone stumbling > into a nasty situation without being aware of the issues. > > Regards > Steve That wouldn't have helped me in this situation because I didn't set anything up via geom, because I was blissfully unaware and didn't ask how anyone to setup a RAID config properly before now. That idea probably wouldn't be a bad one though... -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:35:08 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92E331065681 for ; Sun, 29 Jun 2008 19:35:08 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 1C28D8FC0A for ; Sun, 29 Jun 2008 19:35:07 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so772867fgb.35 for ; Sun, 29 Jun 2008 12:35:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=NltuFcHgQ5RnkRdpIIXuq4jKRkbqIllzRlidkMqonLQ=; b=V4Nxw01oqF5lhTuwPApm7/tpcp7YGpQjefSuoUQhC6vMtV5oz3OD9cdfsVtZdLxqhY EWP+Ib+lAFuOM8OZxe7e030vK/jVDXlxTSwqJaBg2RrSs/KP09exf0I94nyi6tjug6D0 NMK6a3zAH0HxiChwyNbLAEgPQka93qRNCkQOc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WWXvYZKvNTjTTDpDuMbWbMEUhkJXGu/XtzOKD0zT4qdwH683MrgD574XhEbEVntFhy HNI2Uhmp2xYgcHD7DrKrrGEK64JhHalT+71R1l5TbJy5zQFKsGi0BhSEc18GBd/DjD/5 EpcBb8u2lPc3RogyxgM1p7c1l5AxrjUr9lnpo= Received: by 10.86.33.10 with SMTP id g10mr2625774fgg.14.1214768107110; Sun, 29 Jun 2008 12:35:07 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sun, 29 Jun 2008 12:35:07 -0700 (PDT) Message-ID: <7d6fde3d0806291235r532ecc3exf9fedc9457b1613a@mail.gmail.com> Date: Sun, 29 Jun 2008 12:35:07 -0700 From: "Garrett Cooper" To: "Erik Trulsson" In-Reply-To: <20080629163931.GA21334@owl.midgard.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <20080629163931.GA21334@owl.midgard.homeip.net> Cc: Rainer Duffner , current@freebsd.org, "Sean C. Farley" Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:35:08 -0000 On Sun, Jun 29, 2008 at 9:39 AM, Erik Trulsson wrote: > > For hardware-based RAID controllers this disadvantage is usually more than > offset by extra performance and (especially for the good cards with > battery-backed chaches) extra reliability. Such cards are rarely cheap > though. Yup. I just spent ~$600 on a RAID card from 3ware with a battery backup. Disheartening, but that's probably going to be the same cost as data recovery. -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 20:18:42 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62F7510656A8 for ; Sun, 29 Jun 2008 20:18:42 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 12F6C8FC0C for ; Sun, 29 Jun 2008 20:18:42 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:64327 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1KD3M9-0006vI-3f for current@freebsd.org; Sun, 29 Jun 2008 22:18:41 +0200 Received: (qmail 46654 invoked from network); 29 Jun 2008 22:18:38 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 29 Jun 2008 22:18:38 +0200 Received: (qmail 22883 invoked by uid 1001); 29 Jun 2008 22:18:38 +0200 Date: Sun, 29 Jun 2008 22:18:38 +0200 From: Erik Trulsson To: Garrett Cooper Message-ID: <20080629201838.GA22870@owl.midgard.homeip.net> References: <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <20080629163931.GA21334@owl.midgard.homeip.net> <7d6fde3d0806291235r532ecc3exf9fedc9457b1613a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7d6fde3d0806291235r532ecc3exf9fedc9457b1613a@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1KD3M9-0006vI-3f. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1KD3M9-0006vI-3f 0ac60d7dad5b5bd3960630f5d1d1049b Cc: Rainer Duffner , current@freebsd.org, "Sean C. Farley" Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 20:18:42 -0000 On Sun, Jun 29, 2008 at 12:35:07PM -0700, Garrett Cooper wrote: > On Sun, Jun 29, 2008 at 9:39 AM, Erik Trulsson wrote: > > > > For hardware-based RAID controllers this disadvantage is usually more than > > offset by extra performance and (especially for the good cards with > > battery-backed chaches) extra reliability. Such cards are rarely cheap > > though. > > Yup. I just spent ~$600 on a RAID card from 3ware with a battery > backup. Disheartening, but that's probably going to be the same cost > as data recovery. > -Garrett Just remember to make regular backups also. Even a good RAID implementation is not a substitute for regular backups. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 20:42:44 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C32F41065670; Sun, 29 Jun 2008 20:42:44 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 1D37B8FC1E; Sun, 29 Jun 2008 20:42:43 +0000 (UTC) (envelope-from prvs=10663a81d7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1214772163; x=1215376963; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=cKEKhE6UEjoHPYMKE0pBg qmP4mjY/eSyG6i2aLOs/5o=; b=cOG16nMBXnbm/jj1Npwi2IIipaBK+7CXjWh0O GG2mzCHDNkhCJL70DkmScnA1Bqy2zeCuHaCgwOyurQhFFXyzPIE6/YEq5Bixi9+8 of71ma2LrvCy/SNQu9Mp5a7dXD1Ppo7hn0EbtSgrbCItCdqFnHvs4eipvlJoDgwa Of/tv0= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50005839266.msg; Sun, 29 Jun 2008 21:42:42 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=10663a81d7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <238A94001EED440F88063FB8913846CF@multiplay.co.uk> From: "Steven Hartland" To: "Garrett Cooper" References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <48679898.3000905@clearchain.com> <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> <7d6fde3d0806291232o407b6391lcd223c2065ffa32c@mail.gmail.com> Date: Sun, 29 Jun 2008 21:42:39 +0100 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.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 21:42:43 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 29 Jun 2008 21:42:43 +0100 Cc: Benjamin Close , current@freebsd.org, Rainer Duffner , =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 20:42:44 -0000 ----- Original Message ----- From: "Garrett Cooper" On Sun, Jun 29, 2008 at 10:05 AM, Steven Hartland >> As a small expansion to this, a good compromise might be to disable it >> unless a sysctl flag is explicitly set. Similar to how the sysctl >> kern.geom.debugflags=16 works? Then for those that know the implications >> they can still have the functionality but prevents someone stumbling >> into a nasty situation without being aware of the issues. > > That wouldn't have helped me in this situation because I didn't set > anything up via geom, because I was blissfully unaware and didn't ask > how anyone to setup a RAID config properly before now. > That idea probably wouldn't be a bad one though... That would matter with that I meant as unless you set said flag you wouldn't be able to use the volume. And in find out what you needed to set to enable it the docs would have made it quite clear of the consequences. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 22:49:27 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B92B71065672 for ; Sun, 29 Jun 2008 22:49:27 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 15A558FC12 for ; Sun, 29 Jun 2008 22:49:26 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1221978fkk.11 for ; Sun, 29 Jun 2008 15:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mail-followup-to:mime-version:content-type :content-disposition:user-agent; bh=QoDEDpb+4l42JKI55mOAo4jWfvQr8E73Bcwr6JkLDDA=; b=JqL2GxwLYgBCGhAC6qBe3NgKUZefxJu8IJoou756XkEPWlv/JP6ZMnxrc4E/h9mQXY qfSIKMdDQA9ZyjZErcP9x29GA7cfsONRItnpS3g9SdOx6Toyo1apXGR1qnhBKZvSEmvD p8lm/gFCXL5XLPj2Wf5QHD3nZPmxBCH59A770= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent; b=dUCv7zIhq74VFHmsetN/GYh0XmZ0/Ym1vqRn2lC7nMNySt+eh16KyHHE4XlW69lEB1 CbAYAh24bVigrkcC+Hgu+1fau1rSp+/mJd6K8PeZhG2qwzqOnvaCSVht5DUihfShiX9x xF6eghYC15bKSlZC0DvwXU1e5Z/cCG4TeGkW0= Received: by 10.78.138.14 with SMTP id l14mr1116221hud.69.1214778292380; Sun, 29 Jun 2008 15:24:52 -0700 (PDT) Received: from localhost ( [213.184.224.38]) by mx.google.com with ESMTPS id 37sm4037613hub.50.2008.06.29.15.24.50 (version=SSLv3 cipher=RC4-MD5); Sun, 29 Jun 2008 15:24:51 -0700 (PDT) Date: Mon, 30 Jun 2008 01:31:56 +0300 From: Gleb Kurtsou To: current@freebsd.org Message-ID: <20080629223156.GA1416@h1.d> Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: [panic] system crashes if remove usb dongle during probe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 22:49:27 -0000 If you get lucky enough you can crash -current just inserting and removing usb flash dongle. Actually I've never seen such panics before. ~ % uname -a FreeBSD h1.d 8.0-CURRENT FreeBSD 8.0-CURRENT #65: Sat Jun 28 23:38:02 EEST 2008 root@h1.d:/usr/obj/usr/freebsd-src/p4/sys/MY1 i386 Sources are few weeks old. I have a dump and can provide with any additional info needed. Note that this dongle is somewhat really special and FreeBSD seems not to like it, but it works ok in linux and windows on the same and other hardware. It can't even be probed without a patch. I've been using the patch since 2005 and had no problems so far. All other usb devices worked as expected. (Patch is at the end of email. It just disables CAM_AUTOSNS_VALID in umass.c) And event with the patch system can't boot with dongle connected (can get a dump and assist in debugging this panic too). Script started on Mon Jun 30 01:08:45 2008 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: umass0: at uhub2 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc045894a stack pointer = 0x28:0xc2b02848 frame pointer = 0x28:0xc2b02860 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 = 18 (usb2) trap number = 12 panic: page fault KDB: stack backtrace: db_trace_self_wrapper(c085dfa3,c08f32e0,c083c90e,c2b026fc,c2b026fc,...) at db_trace_self_wrapper+0x26 panic(c083c90e,c08853fe,c2d2aa2c,1,1,...) at panic+0xea trap_fatal(c2d34af8,0,c088522d,33e,0,...) at trap_fatal+0x23d trap_pfault(8bc,c2f33690,c2f33890,c2b027a0,c2d34a70,...) at trap_pfault+0x1f4 trap(c2b02808) at trap+0x361 calltrap() at calltrap+0x6 --- trap 0xc, eip = 0xc045894a, esp = 0xc2b02848, ebp = 0xc2b02860 --- xpt_done(c2d9a400,c2d9a400,0,c08786e4,8da,...) at xpt_done+0x2a xpt_action(c2d9a400,c2d9a400,260,c2b028e0,c07df2d1,...) at xpt_action+0x702 camperiphdone(c571bd80,c2d9a400,0,100,c4a3b814,...) at camperiphdone+0x59 camisr_runqueue(c3eb57c0,1,0,c3eb57d4,c4a3b800,...) at camisr_runqueue+0x165 xpt_bus_deregister(0,c4d71000,c5792480,c2b02c34,c057a3dc,...) at xpt_bus_deregister+0x172 umass_cam_detach_sim(c4d710f4,1,c5792480,c572d100,0,...) at umass_cam_detach_sim+0x1d umass_detach(c5792480,c2c9385c,c08a71cc,98f,0,...) at umass_detach+0xcc device_detach(c5792480,2,c2d256e0,c2d35930,c2d256e0,...) at device_detach+0x8f usb_disconnect_port(c2d35930,c2d18e80,10,c2b02cd8,c061c805,...) at usb_disconnect_port+0x72 uhub_explore(c2d36180,c2d37680,c2b02cf8,c057f147,c2ccd210,...) at uhub_explore+0xff usb_discover(c2ccd210,0,5c,c0850f2a,3a98,...) at usb_discover+0x2c usb_event_thread(c2d37680,c2b02d38,c085a644,324,c2d34a70,...) at usb_event_thread+0x97 fork_exit(c057f0b0,c2d37680,c2b02d38) at fork_exit+0xa6 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc2b02d70, ebp = 0 --- Uptime: 11h12m7s Physical memory: 503 MB Dumping 194 MB: 179 163 147 131 115 99 83 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 67 51 35 19 3 Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /.boot/boot/kernel/zfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /.boot/boot/kernel/opensolaris.ko.symbols...done. done. Loaded symbols for /boot/kernel/opensolaris.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc061426d in boot (howto=260) at /usr/freebsd-src/p4/sys/kern/kern_shutdown.c:418 #2 0xc06145d2 in panic (fmt=0xc083c90e "%s") at /usr/freebsd-src/p4/sys/kern/kern_shutdown.c:572 #3 0xc07ff8dd in trap_fatal (frame=0xc2b02808, eva=0) at /usr/freebsd-src/p4/sys/i386/i386/trap.c:934 #4 0xc07ffc14 in trap_pfault (frame=0xc2b02808, usermode=0, eva=0) at /usr/freebsd-src/p4/sys/i386/i386/trap.c:847 #5 0xc08004b1 in trap (frame=0xc2b02808) at /usr/freebsd-src/p4/sys/i386/i386/trap.c:525 #6 0xc07e7adb in calltrap () at /usr/freebsd-src/p4/sys/i386/i386/exception.s:165 #7 0xc045894a in xpt_done (done_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:4835 #8 0xc0459fa2 in xpt_action (start_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:3035 #9 0xc0454089 in camperiphdone (periph=0xc571bd80, done_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_periph.c:1130 #10 0xc045a605 in camisr_runqueue (V_queue=Variable "V_queue" is not available. ) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:7316 #11 0xc045f162 in xpt_bus_deregister (pathid=0) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:4421 #12 0xc057a2dd in umass_cam_detach_sim (sc=0xc4d71000) at /usr/freebsd-src/p4/sys/dev/usb/umass.c:2712 #13 0xc057a3dc in umass_detach (self=0xc5792480) at /usr/freebsd-src/p4/sys/dev/usb/umass.c:1560 #14 0xc063a82f in device_detach (dev=0xc5792480) at device_if.h:212 #15 0xc057ffc2 in usb_disconnect_port (up=0xc2d35930, parent=0xc2d18e80) at /usr/freebsd-src/p4/sys/dev/usb/usb_subr.c:1380 #16 0xc05787bf in uhub_explore (dev=0xc2d36180) at /usr/freebsd-src/p4/sys/dev/usb/uhub.c:462 #17 0xc057e04c in usb_discover (v=Variable "v" is not available. ) at /usr/freebsd-src/p4/sys/dev/usb/usb.c:728 #18 0xc057f147 in usb_event_thread (arg=0xc2d37680) at /usr/freebsd-src/p4/sys/dev/usb/usb.c:440 #19 0xc05f68a6 in fork_exit (callout=0xc057f0b0 , arg=0xc2d37680, frame=0xc2b02d38) at /usr/freebsd-src/p4/sys/kern/kern_fork.c:812 #20 0xc07e7b50 in fork_trampoline () at /usr/freebsd-src/p4/sys/i386/i386/exception.s:270 (kgdb) fr 7 #7 0xc045894a in xpt_done (done_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:4835 4835 TAILQ_INSERT_TAIL(&sim->sim_doneq, &done_ccb->ccb_h, (kgdb) l 4830 * any of the "non-immediate" type of ccbs. 4831 */ 4832 sim = done_ccb->ccb_h.path->bus->sim; 4833 switch (done_ccb->ccb_h.path->periph->type) { 4834 case CAM_PERIPH_BIO: 4835 TAILQ_INSERT_TAIL(&sim->sim_doneq, &done_ccb->ccb_h, 4836 sim_links.tqe); 4837 done_ccb->ccb_h.pinfo.index = CAM_DONEQ_INDEX; 4838 if ((sim->flags & CAM_SIM_ON_DONEQ) == 0) { 4839 mtx_lock(&cam_simq_lock); (kgdb) p done_ccb->ccb_h $2 = {pinfo = {priority = 5, generation = 18, index = -2}, xpt_links = {le = {le_next = 0x0, le_prev = 0xc4d72a6c}, sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xc4d72a6c}, stqe = { stqe_next = 0x0}}, sim_links = {le = {le_next = 0x0, le_prev = 0xc4a3b814}, sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xc4a3b814}, stqe = {stqe_next = 0x0}}, periph_links = {le = { le_next = 0x0, le_prev = 0x0}, sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0x0}, stqe = { stqe_next = 0x0}}, retry_count = 0, cbfcnp = 0xc0462ef0 , func_code = XPT_SCSI_IO, status = 8, path = 0xc79c3360, path_id = 0, target_id = 0, target_lun = 0, flags = 64, periph_priv = {entries = {{ ptr = 0x1, field = 1, bytes = "\001\000\000"}, {ptr = 0x0, field = 0, bytes = "\000\000\000"}}, bytes = "\001\000\000\000\000\000\000"}, sim_priv = {entries = {{ptr = 0x0, field = 0, bytes = "\000\000\000"}, {ptr = 0x0, field = 0, bytes = "\000\000\000"}}, bytes = "\000\000\000\000\000\000\000"}, timeout = 5000, timeout_ch = {callout = 0x0}} (kgdb) fr 8 #8 0xc0459fa2 in xpt_action (start_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_xpt.c:3035 3035 (*(sim->sim_action))(sim, start_ccb); (kgdb) l 3030 3031 sim = path->bus->sim; 3032 if (SIM_DEAD(sim)) { 3033 /* The SIM has gone; just execute the CCB directly. */ 3034 cam_ccbq_send_ccb(&path->device->ccbq, start_ccb); 3035 (*(sim->sim_action))(sim, start_ccb); 3036 break; 3037 } 3038 3039 cam_ccbq_insert_ccb(&path->device->ccbq, start_ccb); (kgdb) fr 9 #9 0xc0454089 in camperiphdone (periph=0xc571bd80, done_ccb=0xc2d9a400) at /usr/freebsd-src/p4/sys/cam/cam_periph.c:1130 1130 xpt_action(done_ccb); (kgdb) l 1125 bcopy(done_ccb->ccb_h.saved_ccb_ptr, done_ccb, 1126 sizeof(union ccb)); 1127 1128 periph->flags &= ~CAM_PERIPH_RECOVERY_INPROG; 1129 1130 xpt_action(done_ccb); 1131 1132 break; 1133 } 1134 (kgdb) Index: umass.c =================================================================== RCS file: /pub/mirror/FreeBSD-CVS/src/sys/dev/usb/umass.c,v retrieving revision 1.123 diff -u -r1.123 umass.c --- umass.c 19 Jul 2005 05:18:23 -0000 1.123 +++ umass.c 30 Oct 2005 22:06:23 -0000 @@ -2467,7 +2467,7 @@ sense->extra_len = 10; ccb->csio.scsi_status = SCSI_STATUS_CHECK_COND; ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR | - CAM_AUTOSNS_VALID; + /* CAM_AUTOSNS_VALID */ 0; xpt_done(ccb); return; } @@ -2762,7 +2762,7 @@ */ ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; csio->scsi_status = SCSI_STATUS_CHECK_COND; #if 0 @@ -2793,7 +2793,7 @@ break; } else { ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; csio->scsi_status = SCSI_STATUS_CHECK_COND; } xpt_done(ccb); @@ -2829,7 +2829,7 @@ ccb->ccb_h.status = CAM_REQ_CMP; #endif ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; ccb->csio.scsi_status = SCSI_STATUS_CHECK_COND; xpt_done(ccb); } From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 02:17:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF2471065670 for ; Mon, 30 Jun 2008 02:17:30 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 6122F8FC17 for ; Mon, 30 Jun 2008 02:17:29 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m5U1gmPR069639; Sun, 29 Jun 2008 19:42:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48683A18.6080509@samsco.org> Date: Sun, 29 Jun 2008 19:42:48 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Julian Elischer References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> <48678334.9070500@bsdforen.de> <4867E2EE.3070008@elischer.org> In-Reply-To: <4867E2EE.3070008@elischer.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Dominic Fandrey , FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 02:17:30 -0000 Julian Elischer wrote: > Dominic Fandrey wrote: >> Kris Kennaway wrote: >>> Ruslan Ermilov wrote: >>>> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>>>> I am frequently getting this when trying to minidump on amd64: >>>>> >>>>> Physical memory: 8168 MB >>>>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>>>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 >>>>> 1750 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 >>>>> 1542 1526 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 >>>>> 1334 1318 1302 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 >>>>> 1126 1110 1094 1078 1062 1046 1030 1014 998 982 966 950 934 918 902 >>>>> 886 870 854 838 822 806 790 774 758 742 726 710 694 678 662 646 630 >>>>> 614 598 582 566 550 534 518 502 486 470 454 438 422 406 390 374 358 >>>>> 342 326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 >>>>> 70 54 38 22 6Attempt to write outside dump device boundaries. >>>>> >>>>> ** DUMP FAILED (ERROR 6) ** >>>>> = 0 >>>>> >>>> Yes, it happens most often on SMP machines. Previously it could >>>> overwrite data on your disk (in our case it destroyed GEOM mirrors). >>>> Now the attempt is logged and prevented. >>>> >>>> What's your question? ;) >>> >>> I'd have thought it was obvious: "why?" >>> >>> Kris >> >> Not enough swap space? > > It used to check that before starting.. did that check get removed? It does check when it starts. The problem is that the size grows after that. Scott From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 03:07:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 407D1106568C for ; Mon, 30 Jun 2008 03:07:35 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outG.internet-mail-service.net (outg.internet-mail-service.net [216.240.47.230]) by mx1.freebsd.org (Postfix) with ESMTP id 2754C8FC20 for ; Mon, 30 Jun 2008 03:07:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id CB6DD2429; Sun, 29 Jun 2008 20:07:34 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 25FCF2D6020; Sun, 29 Jun 2008 20:07:34 -0700 (PDT) Message-ID: <48684E07.9070602@elischer.org> Date: Sun, 29 Jun 2008 20:07:51 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Scott Long References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> <48678334.9070500@bsdforen.de> <4867E2EE.3070008@elischer.org> <48683A18.6080509@samsco.org> In-Reply-To: <48683A18.6080509@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Dominic Fandrey , FreeBSD Current Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 03:07:35 -0000 Scott Long wrote: > Julian Elischer wrote: >> Dominic Fandrey wrote: >>> Kris Kennaway wrote: >>>> Ruslan Ermilov wrote: >>>>> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>>>>> I am frequently getting this when trying to minidump on amd64: >>>>>> >>>>>> Physical memory: 8168 MB >>>>>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>>>>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 >>>>>> 1750 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 >>>>>> 1542 1526 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 >>>>>> 1334 1318 1302 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 >>>>>> 1126 1110 1094 1078 1062 1046 1030 1014 998 982 966 950 934 918 >>>>>> 902 886 870 854 838 822 806 790 774 758 742 726 710 694 678 662 >>>>>> 646 630 614 598 582 566 550 534 518 502 486 470 454 438 422 406 >>>>>> 390 374 358 342 326 310 294 278 262 246 230 214 198 182 166 150 >>>>>> 134 118 102 86 70 54 38 22 6Attempt to write outside dump device >>>>>> boundaries. >>>>>> >>>>>> ** DUMP FAILED (ERROR 6) ** >>>>>> = 0 >>>>>> >>>>> Yes, it happens most often on SMP machines. Previously it could >>>>> overwrite data on your disk (in our case it destroyed GEOM mirrors). >>>>> Now the attempt is logged and prevented. >>>>> >>>>> What's your question? ;) >>>> >>>> I'd have thought it was obvious: "why?" >>>> >>>> Kris >>> >>> Not enough swap space? >> >> It used to check that before starting.. did that check get removed? > > It does check when it starts. The problem is that the size grows after > that. > this MUST be a bug in the code that is supposed to halt all the other CPUs. > Scott From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 04:34:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 469971065674 for ; Mon, 30 Jun 2008 04:34:09 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 091EC8FC0C for ; Mon, 30 Jun 2008 04:34:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1367552rvf.43 for ; Sun, 29 Jun 2008 21:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XI4omY8A34pe8evvbw0onlHNbLKvP7xv+78XI3Tsd0k=; b=RJE7EcUXpAfAAeI9ZSad9VotHbq5ou5UlvmE615MrLRBYgPxQVnKtymC5eEu/23ppI dC9bu3xvSyQyUrDQua5jyNBNtbQjz1rX2trKg4vt08GnEyEb734DSw9mHhqoW62YtIj+ DLaeQc3QojUqB6kK/WyaWSJ+PiAh9y65SjIB8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=uA2EojHeahuHO7LYvKsDrhlMyfrohNt771zPoo1vvSsW4ub8xwncZWglcrz5fK3p17 vRRoDWsGv57i3eJJQztMUijPbQYSJox6dILXGS9Wvp27TnpUaV005+UAm97OsZSn9vrv 4tty9cNHSnyAB6FjMWsVjPnCQhYmwvHDqz+J0= Received: by 10.141.197.14 with SMTP id z14mr2341108rvp.283.1214800448115; Sun, 29 Jun 2008 21:34:08 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k2sm7085663rvb.4.2008.06.29.21.34.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 29 Jun 2008 21:34:07 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m5U4VvKR080376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 13:31:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5U4VuJm080375; Mon, 30 Jun 2008 13:31:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 30 Jun 2008 13:31:56 +0900 From: Pyun YongHyeon To: Dimitry Andric Message-ID: <20080630043156.GB79537@cdnetworks.co.kr> References: <20080607035911.GD4565@cdnetworks.co.kr> <484BC9FB.2040605@andric.com> <20080609012657.GD12521@cdnetworks.co.kr> <484D215A.7050700@andric.com> <20080609123206.GF12521@cdnetworks.co.kr> <484D25CC.9050106@andric.com> <20080610050550.GB17874@cdnetworks.co.kr> <484E9377.2050609@andric.com> <20080611005814.GA3529@cdnetworks.co.kr> <48666CD7.9020706@andric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48666CD7.9020706@andric.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.org Subject: Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 04:34:09 -0000 On Sat, Jun 28, 2008 at 06:54:47PM +0200, Dimitry Andric wrote: > On 2008-06-11 02:58, Pyun YongHyeon wrote: > > > This seems to work better, although it still takes quite some time > > > (~10s) for the interfaces to go up at boot time. I haven't yet been > > > able to get them "stuck", however, so that's good. :) > > Hmm, that's interesting. Can you spot where re(4) spends its time? > > Did RELENG_7 also have this issue? > > Apparently it's experiencing timeouts, I usually get these: > > re0: link state changed to DOWN > re0: watchdog timeout ^^^^^^^^^^^^^^^^ Because link state changed to DOWN re(4) should not queue transmitting packets anymore until it get a valid link. Trying to send further packets would cause watchdong timeouts as above. This indicates re(4) failed to detect link loss event. What makes me wonder is why the link state was changed to DOWN. Do you have a clue(e.g. switching hub down etc)? > re0: 3 link states coalesced ^^^^^^^^^^^^^^^^^^^^^^^ Hmm, I guess you've encountered another bug. The link states coalescing message indicates a bug in PHY driver and link state handling of re(4). ATM the link state handling of re(4) is in very bad state and it doesn't correctly drive MII_TICK. re(4) just relys on link status change interrupt of controller but re(4) failed to determine what's current link event is for (The event could be link up or down or auto-negotiation complete etc). In addition, all RealTek controllers lack proper programming interface to tell MAC negotiated speed/duplex/flow-controls which in turn taking proper action to the event very hard. I guess re(4) should not rely on link status change interrupt but it should fall back to traditional polling mechanism which will enable correct tracking of link establishment. Also the link up/ down handling should be changed to process mii(4) posted events. All these change requires a lot of code change and needs more testing. I think I may have to commit accumulated patches for newer RTL8168 family before going to that direction. The patch is not perfect to address all issues for RTL8168 family but it allows recognition of the new hardware and make it usable in most cases. > re0: link state changed to UP > re1: link state changed to DOWN > > I've been running all tests under RELENG_7, btw. Note also, these > delays don't always happen, in some cases the interfaces react very > quickly. In rare cases, they don't work at all, until you manually > ifconfig down and up them a few times. > > What's funny though, is that the interfaces seem to start in DOWN mode: > > [...booting...] > Mounting local file systems:. > Setting hostname: tensor.andric.com. > re0: link state changed to DOWN > re1: link state changed to DOWN > lo0: flags=8049 metric 0 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 > inet 127.0.0.1 netmask 0xff000000 > re0: flags=8843 metric 0 mtu 1500 > options=399b > ether 00:30:18:a6:f1:a8 > inet6 fe80::230:18ff:fea6:f1a8%re0 prefixlen 64 tentative scopeid 0x1 > inet 87.251.56.140 netmask 0xffffffc0 broadcast 87.251.56.191 > media: Ethernet autoselect (none) > status: no carrier > re1: flags=8843 metric 0 mtu 1500 > options=399b > ether 00:30:18:a6:f1:a9 > inet6 fe80::230:18ff:fea6:f1a9%re1 prefixlen 64 tentative scopeid 0x2 > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (none) > status: no carrier > [...more initialization...] > net.inet6.ip6.forwarding: 0 -> 1 > net.inet6.ip6.accept_rtadv: 0 -> 0 > re0: link state changed to UP > re1: link state changed to UP > > and only then do they "really" go up... :) > I can't sure due to bugs in link state handling in driver but generally it's normal. Establishing a link with link partner takes time and sometimes it would even take 10 seconds or more. > Do you have any good suggestions on where I could put some debug > printfs in re to find out what it's timing out on? > Before doing that it would be more appropriate to fix link state handing in driver. I'll let you know when I have a patch for link handling clean-up. > > > Plugging/unplugging UTP cable to ethernet controller during boot > > change the long delay? How about disabling WOL before system > > shutdown?(e.g. ifconfig re0 -wol) > > Plugging/unplugging the cable doesn't seem to make much difference, and > neither does disabling WOL before shutdown (or altogether)... > Ok. Thanks for reporting. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 08:27:12 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF745106566C; Mon, 30 Jun 2008 08:27:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9087B8FC21; Mon, 30 Jun 2008 08:27:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 133FA46C0D; Mon, 30 Jun 2008 04:27:12 -0400 (EDT) Date: Mon, 30 Jun 2008 09:27:11 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: net@FreeBSD.org, current@FreeBSD.org In-Reply-To: <20080629180126.F90836@fledge.watson.org> Message-ID: <20080630091033.P3968@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 08:27:12 -0000 On Sun, 29 Jun 2008, Robert Watson wrote: > An FYI on the state of things here: in the last month, John has updated a > number of device drivers to be MPSAFE, and the USB work remains in-flight. > I'm holding fire a bit on disabling IFF_NEEDSGIANT while things settle and I > catch up on driver state, and will likely send out an update next week > regarding which device drivers remain on the kill list, and generally what > the status of this project is. Here's the revised list of drivers that will have their build disabled in the next week (subject to an appropriate block of time for me): Name Bus Man page description ---- --- -------------------- ar ISA/PCI synchronous Digi/Arnet device driver arl ISA Aironet Arlan 655 wireless network adapter driver cnw ISA Netwave AirSurfer wireless network driver ic I2C I2C bus system oltr ISA/PCI Olicom Token Ring device driver plip PPBUS printer port Internet Protocol driver ppp TTY point to point protocol network interface ray PCCARD Raytheon Raylink/Webgear Aviator PCCard driver sbni ISA/PCI Granch SBNI12 leased line modem driver sbsh PCI Granch SBNI16 SHDSL modem device driver sl TTY slip network interface snc ISA/PCCARD National Semiconductor DP8393X SONIC Ethernet adapter driver sppp TTY point to point protocol network layer for synchronous lines sr ISA/PCI synchronous RISCom/N2 / WANic 400/405 device driver Obviously, if necessary work is done to remove the IFF_NEEDSGIANT requirement from a driver, it will be pulled from the list, and I'll do an IFF_NEEDSGIANT scan before pulling the plug. Drivers will remain in the tree but disconnected for about a month before being removed from HEAD. Thanks greatly to John and others who have worked hard to reduce the size of the list in the last year! The following USB drivers will remain enabled due to on-going USB work that should eliminate IFF_NEEDSGIANT: Name Bus Man page description ---- --- -------------------- axe USB ASIX Electronics AX88172 USB Ethernet driver cdce USB USB Communication Device Class Ethernet driver cue USB CATC USB-EL1210A USB Ethernet driver kue USB Kawasaki LSI KL5KUSB101B USB Ethernet driver rue USB RealTek RTL8150 USB to Fast Ethernet controller rum USB Ralink Technology USB IEEE 802.11a/b/g wireless network device udav USB Davicom DM9601 USB Ethernet driver ural USB Ralink Technology RT2500USB IEEE 802.11 driver zyd USB ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device The following drivers reference IFF_NEEDSGIANT but only when running in an optional non-MPSAFE mode; that optional mode will be removed but the drivers will remain: Name Bus Man page description ---- --- -------------------- ce PCI driver for synchronous Cronyx Tau-PCI/32 WAN adapters cp PCI driver for synchronous Cronyx Tau-PCI WAN adapters ctau ISA driver for synchronous Cronyx Tau WAN adapters cx ISA driver for synchronous/asynchronous Cronyx Sigma WAN adapters Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 09:25:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EFC11065674; Mon, 30 Jun 2008 09:25:27 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id D88E08FC1E; Mon, 30 Jun 2008 09:25:26 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru (BL-18-PXY-0.express.ru [212.24.36.217] (may be forged)) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m5U8qd0I014083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 12:52:41 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDF7n-0008rb-3l; Mon, 30 Jun 2008 12:52:39 +0400 From: Vladimir Grebenschikov To: Alexey Shuvaev In-Reply-To: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 30 Jun 2008 12:52:38 +0400 Message-Id: <1214815958.3581.67.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: kientzle@freebsd.org, freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 09:25:27 -0000 On Thu, 2008-06-26 at 13:05 +0200, Alexey Shuvaev wrote: > Hello! >=20 > Yesterday I have encountered a strange problem > trying to build math/qtiplot, the compiler exited with errors during > the build. After examining the situation it appeared that math/qtiplot3d-= qt4 > have installed damaged include files. In a nutshell the problem is that > bsdcpio damages the files: Same here, also it shows strange warning on every directory being copied: $ cd ~/tmp $ mkdir -p a/b/c/1 a/b/c/2 a/b/c/3 dst $ cp DSC01699.JPG a/b/c/1/ =EF=BB=BF$ cp DSC01699.JPG a/b/c/2/ =EF=BB=BF$ cp DSC01699.JPG a/b/c/3/ $ file a/b/c/?/* a/b/c/1/DSC01699.JPG: JPEG image data, EXIF standard 2.2 a/b/c/2/DSC01699.JPG: JPEG image data, EXIF standard 2.2 a/b/c/3/DSC01699.JPG: JPEG image data, EXIF standard 2.2 $ find a | cpio -dumpl dst/ Operation not permitted: Operation not permitted cpio: Can't create 'dst/a/b': Operation not permitted: Operation not permitted cpio: Can't create 'dst/a/b/c': Operation not permitted: Operation not permitted cpio: Can't create 'dst/a/b/c/1': Operation not permitted: Operation not permitted cpio: Can't create 'dst/a/b/c/2': Operation not permitted: Operation not permitted cpio: Can't create 'dst/a/b/c/3': Operation not permitted: Operation not permitted $ file a/b/c/?/* a/b/c/1/DSC01699.JPG: data a/b/c/2/DSC01699.JPG: data a/b/c/3/DSC01699.JPG: data $ truss shows: ... lstat("dst/a/b/c/3",0xbfbfe15c) ERR#2 'No such file or directory' link("a/b/c/3","dst/a/b/c/3") ERR#1 'Operation not permitted' ... Bad news, that it damaged original files also. PS:=20 upgrading now ... --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 10:01:03 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CC99106568B for ; Mon, 30 Jun 2008 10:01:03 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id EA8C68FC14 for ; Mon, 30 Jun 2008 10:01:02 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from [87.242.97.68] (port=58130 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1KDGBq-000GcV-Tl; Mon, 30 Jun 2008 10:00:55 +0000 Date: Mon, 30 Jun 2008 14:00:35 +0400 From: Ruslan Ermilov To: Julian Elischer Message-ID: <20080630100035.GA99247@edoofus.dev.vega.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48684E07.9070602@elischer.org> Cc: current@FreeBSD.org Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 10:01:03 -0000 On Sun, Jun 29, 2008 at 08:07:51PM -0700, Julian Elischer wrote: > this MUST be a bug in the code that is supposed to halt all the other > CPUs. > An email thread in current@ from January 2008 I quoted earlier in this thread described all of this in detail. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 10:09:03 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A782D1065684 for ; Mon, 30 Jun 2008 10:09:03 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6AE058FC14 for ; Mon, 30 Jun 2008 10:09:03 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1351634wfg.7 for ; Mon, 30 Jun 2008 03:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=IE9H0mnXHAuLgzbfdAYyi10hFrKOMsKZ0szKskxNkzo=; b=s6JXOYrHok8KIP7wf8pD5h7sJqS3WLwjeZXOoRgGosKhaRkJC7QRnVWtrxsIJU0+eZ LxBTLDOFYtKt1XnkQTnJ8j8HKxyFabpgWJ533z7w60CwSZOYDnzbZMDK8ONMfRSiMYih ehl0yf1IPlLqAJosdkwhEpXkQclPMNzgUEni4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fAAuKbPs5dzExvViFYQ/QaekpxslvhMIEyRoW96IlcY+cGZFEGt7xjtplNBDFx4H9p r1HnX4cCNnOFpXW7+glVEfof6kw5yRhdsPF0ktwO4CcAroI6FgUES83WSN6VIaLKD5pz 6OfSI/xD0U/k0e+ojFt2QugoKDm938TdeeK0I= Received: by 10.142.72.4 with SMTP id u4mr1774371wfa.269.1214819001986; Mon, 30 Jun 2008 02:43:21 -0700 (PDT) Received: by 10.143.172.8 with HTTP; Mon, 30 Jun 2008 02:43:21 -0700 (PDT) Message-ID: <70e8236f0806300243k69399808mf54ccb5796d395c0@mail.gmail.com> Date: Mon, 30 Jun 2008 10:43:21 +0100 From: "Joao Barros" To: "Robert Watson" In-Reply-To: <20080630091033.P3968@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> Cc: arch@freebsd.org, current@freebsd.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 10:09:03 -0000 On Mon, Jun 30, 2008 at 9:27 AM, Robert Watson wrote: > The following USB drivers will remain enabled due to on-going USB work that > should eliminate IFF_NEEDSGIANT: Hi Robert, Is this on-going USB work just on the driver level or on the USB stack as well? I assume both need to be touched for MP safety. Who is doing this work? Joao Barros From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 12:16:17 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2762106564A; Mon, 30 Jun 2008 12:16:17 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 65B318FC14; Mon, 30 Jun 2008 12:16:17 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A57A87.dip.t-dialin.net [84.165.122.135]) by redbull.bpaserver.net (Postfix) with ESMTP id 9E4332E2D6; Mon, 30 Jun 2008 14:16:14 +0200 (CEST) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 096AE1340F1; Mon, 30 Jun 2008 14:16:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1214828172; bh=HmifkMrU5So/Hf6WY68q+Etsuz7q1OLXQ eXJkj5i0kM=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=WCAGTs15tdtBZxf++LK/YktEC4sq3PnweMCQUhRNZpO6RKRCYmVq2KtoNO6S3ton7 jD2eTb08bfT+m/QiMW0TNUH8DPXf8k2jBzdmdejLBNAd2lpV2zMbI1Mgvocr3EKZIXB 5C37BZ8+NrDT4mgA9w8GQfauiQBSrFdBot6rFNZkAetKRaaT9LebGCPwcZbZxtFr5c3 1pS53jb0QJ7/6JauipH6kdm4THBGqh4/ctgCRX4Gtfr+b8p+hByFy6puT7v0rqBJ1eR T+lBzcq0NvVmf9lYi/nKt1O4iKWtlSTzOy4Bh9L6m7KazNUQfy/adskBLxbMPgT1kW+ zTl9CyvFA== Received: (from www@localhost) by webmail.leidinger.net (8.14.2/8.13.8/Submit) id m5UCGBZa067264; Mon, 30 Jun 2008 14:16:11 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Mon, 30 Jun 2008 14:16:11 +0200 Message-ID: <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 30 Jun 2008 14:16:11 +0200 From: Alexander Leidinger To: Robert Watson References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> In-Reply-To: <20080630091033.P3968@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.2-RC2) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.823, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10, TW_CX 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 12:16:17 -0000 Quoting Robert Watson (from Mon, 30 Jun 2008 =20 09:27:11 +0100 (BST)): > > On Sun, 29 Jun 2008, Robert Watson wrote: > >> An FYI on the state of things here: in the last month, John has =20 >> updated a number of device drivers to be MPSAFE, and the USB work =20 >> remains in-flight. I'm holding fire a bit on disabling =20 >> IFF_NEEDSGIANT while things settle and I catch up on driver state, =20 >> and will likely send out an update next week regarding which device =20 >> drivers remain on the kill list, and generally what the status of =20 >> this project is. > > Here's the revised list of drivers that will have their build =20 > disabled in the next week (subject to an appropriate block of time =20 > for me): Is this list supposed to be complete (including dependencies)? bktr =20 uses some I2C stuff and cxm (in ports) too. Bye, Alexander. --=20 meeting, n: =09An assembly of people coming together to decide what person or =09department not represented in the room must solve a problem. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 12:36:46 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34EA61065672; Mon, 30 Jun 2008 12:36:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0A1D28FC1B; Mon, 30 Jun 2008 12:36:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id AA10446B2E; Mon, 30 Jun 2008 08:36:45 -0400 (EDT) Date: Mon, 30 Jun 2008 13:36:45 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Alexander Leidinger In-Reply-To: <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> Message-ID: <20080630133335.K54631@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 12:36:46 -0000 On Mon, 30 Jun 2008, Alexander Leidinger wrote: >> Here's the revised list of drivers that will have their build disabled in >> the next week (subject to an appropriate block of time for me): > > Is this list supposed to be complete (including dependencies)? bktr uses > some I2C stuff and cxm (in ports) too. As far as I'm aware, this list is complete. I compiled it by identifying all network device drivers that set (or may set) the IFF_NEEDSGIANT. With respect to i2c, this refers *only* to the if_ic.c network device driver, and not the other services associated with i2c, so bktr and other i2c consumers should be unaffected. I'm not familiar with cxm so can't comment on that. If you are aware of any other in-tree network device drivers that use IFF_NEEDSGIANT and aren't on the list, please do let me know. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 12:37:54 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC762106564A; Mon, 30 Jun 2008 12:37:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8FD908FC1B; Mon, 30 Jun 2008 12:37:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 48F6346C0C; Mon, 30 Jun 2008 08:37:54 -0400 (EDT) Date: Mon, 30 Jun 2008 13:37:54 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Joao Barros In-Reply-To: <70e8236f0806300243k69399808mf54ccb5796d395c0@mail.gmail.com> Message-ID: <20080630133649.P54631@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <70e8236f0806300243k69399808mf54ccb5796d395c0@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@freebsd.org, current@freebsd.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 12:37:54 -0000 On Mon, 30 Jun 2008, Joao Barros wrote: > On Mon, Jun 30, 2008 at 9:27 AM, Robert Watson wrote: >> The following USB drivers will remain enabled due to on-going USB work that >> should eliminate IFF_NEEDSGIANT: > > Is this on-going USB work just on the driver level or on the USB stack as > well? I assume both need to be touched for MP safety. Who is doing this > work? I'm not familiar with the details of the on-going work, but as I understand it, all USB device drivers have been fully locked and the requirement for IFF_NEEDSGIANT is eliminated. Perhaps Hans, Warner, or Alfred could provide some further insight in this area. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 13:17:25 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 084491065670; Mon, 30 Jun 2008 13:17:25 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id A237E8FC1A; Mon, 30 Jun 2008 13:17:24 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A57A87.dip.t-dialin.net [84.165.122.135]) by redbull.bpaserver.net (Postfix) with ESMTP id 913022E095; Mon, 30 Jun 2008 15:17:17 +0200 (CEST) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 103A211926B; Mon, 30 Jun 2008 15:17:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1214831835; bh=CD8DDhyprgMB3SA392bQDGRjGB8kkVnhv P1wDGcvHUw=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tUDKlmol9tESEn2hZhr8l/IbZN2AQg4P6KfzCKb0AglslYd9JIQuL+G2cJptD18Pg C9U4PFQk2DjEpUQotDSoQrsspiLX6sO5gOrjUGFWtri8uvUn1cKolcWInkIGPUIg+6C SeH7FB7rHF4v/mYrjBdC7PVOpGdEjINbB1ZiLFKawXqgGYrUAwGaAix+ZlkWWColscp MkBftVoO4ngm+5EnOPF2zh56qq13nyDLE+nOKCFoRoPGJrAWbTqHUUYIU3w40xY2m1u sHJxFIR7sGSkv5X4O30xU2qS7MrG8noZSIsheNU39elTo7P/sZecpL6VGUCvn7M6swP zAzHcP2ug== Received: (from www@localhost) by webmail.leidinger.net (8.14.2/8.13.8/Submit) id m5UDHEeJ077404; Mon, 30 Jun 2008 15:17:14 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Mon, 30 Jun 2008 15:17:14 +0200 Message-ID: <20080630151714.13993elkvrzzzda8@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 30 Jun 2008 15:17:14 +0200 From: Alexander Leidinger To: Robert Watson References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> <20080630133335.K54631@fledge.watson.org> In-Reply-To: <20080630133335.K54631@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.2-RC2) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.823, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10, TW_CX 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 13:17:25 -0000 Quoting Robert Watson (from Mon, 30 Jun 2008 =20 13:36:45 +0100 (BST)): > > On Mon, 30 Jun 2008, Alexander Leidinger wrote: > >>> Here's the revised list of drivers that will have their build =20 >>> disabled in the next week (subject to an appropriate block of time =20 >>> for me): >> >> Is this list supposed to be complete (including dependencies)? bktr =20 >> uses some I2C stuff and cxm (in ports) too. > > As far as I'm aware, this list is complete. I compiled it by =20 > identifying all network device drivers that set (or may set) the =20 > IFF_NEEDSGIANT. With respect to i2c, this refers *only* to the =20 > if_ic.c network device driver, and not the other services associated =20 > with i2c, so bktr and other i2c consumers should be unaffected. I'm Ok. > not familiar with cxm so can't comment on that. If you are aware of =20 > any other in-tree network device drivers that use IFF_NEEDSGIANT and =20 > aren't on the list, please do let me know. I think cxm is similar to bktr in this regard (both are multimedia devices). Bye, Alexander. --=20 PARDON me, am I speaking ENGLISH? http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 14:40:16 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D3F1106568A; Mon, 30 Jun 2008 14:40:16 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 7EDCE8FC0A; Mon, 30 Jun 2008 14:40:15 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=tUWMqruglosA:10 a=vGZbR77S6-YA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=6I5d2MoRAAAA:8 a=x3mGqk6BiQcakV6IviYA:9 a=tEWCTne9EWEIHHrelncA:7 a=ZaVJdwSAxtzrjc5kqyx-8OciHPUA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 991033122; Mon, 30 Jun 2008 15:40:11 +0200 From: Hans Petter Selasky To: freebsd-arch@freebsd.org Date: Mon, 30 Jun 2008 15:41:44 +0200 User-Agent: KMail/1.9.7 References: <20080524111715.T64552@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <70e8236f0806300243k69399808mf54ccb5796d395c0@mail.gmail.com> In-Reply-To: <70e8236f0806300243k69399808mf54ccb5796d395c0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806301541.46177.hselasky@c2i.net> Cc: arch@freebsd.org, Joao Barros , Robert Watson , current@freebsd.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 14:40:16 -0000 On Monday 30 June 2008, Joao Barros wrote: > On Mon, Jun 30, 2008 at 9:27 AM, Robert Watson wrote: > > The following USB drivers will remain enabled due to on-going USB work > > that should eliminate IFF_NEEDSGIANT: > > Hi Robert, > > Is this on-going USB work just on the driver level or on the USB stack > as well? I assume both need to be touched for MP safety. > Who is doing this work? > > Joao Barros > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" Hi, In the USB perforce project there are Giant free USB ethernet drivers, which have been around for quite a while. I am currently in the run-up renaming symbols so that my new USB stack can co-exist with the old USB stack. At least it will be possible to compile a kernel with both USB stacks. I suppose that USB ethernet drivers will no longer be available in the old USB stack ? References for FreeBSD developers: Before symbol rename: //depot/projects/usb/src/sys/dev/usb {if_xxx.c} After symbol rename: //depot/projects/usb/src/sys/dev/usb2/ethernet Others: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb2/ethernet&HIDEDEL=NO --HPS From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 14:46:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E9691065678 for ; Mon, 30 Jun 2008 14:46:54 +0000 (UTC) (envelope-from jamesfrancistoy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 365EA8FC21 for ; Mon, 30 Jun 2008 14:46:54 +0000 (UTC) (envelope-from jamesfrancistoy@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so322209ana.13 for ; Mon, 30 Jun 2008 07:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=ynBv+5Jabk/Zl3vmvamHC7gap4wwoCW5Gk/wlcsXUt0=; b=xxzASRDG0rU+mfEgVhFtZ4h46EefVLXER2N0WRGx4CD16bocBslFV4np4XEjYPnuBC /P2rUeUX+0t3lezd51t/xFrs/vsW0sA6bYzXIQCeqCL5sWH1D68gBCrTL/NiaafMkICF KF8Qt3RkmAKzepGi124cQoNvXC9CZCjNVHMpw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=hmC067uY9KJaRIGatY0ShT0jPv1wLg9rdyHxFZ1I0SJI/VR6f9zkn4ZJhlxopWstaW Zw1e+MSylBDY4iLNJr4o1GV+yBDeH1EdPkrB4fk9ja/whHCNWiNR6gd2eYT6ZbccWKoY p5KS3E17JTXkEtPt97wlgF5mcl2BoHMRSpBaQ= Received: by 10.100.3.4 with SMTP id 4mr3169346anc.54.1214837213498; Mon, 30 Jun 2008 07:46:53 -0700 (PDT) Received: by 10.100.190.10 with HTTP; Mon, 30 Jun 2008 07:46:53 -0700 (PDT) Message-ID: <9f8af95f0806300746qde2a282kbade983626c20495@mail.gmail.com> Date: Mon, 30 Jun 2008 10:46:53 -0400 From: "james toy" Sender: jamesfrancistoy@gmail.com To: "FreeBSD Current" MIME-Version: 1.0 X-Google-Sender-Auth: c042c633b54ab95e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Wacom Tablet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 14:46:54 -0000 Hey all, I have an IBM x61t tablet -- serial wacom -- I was just wondering if anyone had a good place to start -- a generic how to for freebsd i've seen the one at linuxwacom.sourceforge.net -- is this all i need? Is there somewhere special to look in the freebsd docs? Sorry for the simple question. Hope everyone is well. respectfully, -- jt From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 15:30:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDFD61065672 for ; Mon, 30 Jun 2008 15:30:36 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 539E08FC18 for ; Mon, 30 Jun 2008 15:30:36 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m5UFHnAd093456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 30 Jun 2008 17:17:50 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m5UFHjbf062224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 17:17:45 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m5UFHim7024304; Mon, 30 Jun 2008 17:17:44 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m5UFHi2L024303; Mon, 30 Jun 2008 17:17:44 +0200 (CEST) (envelope-from ticso) Date: Mon, 30 Jun 2008 17:17:44 +0200 From: Bernd Walter To: freebsd-current@freebsd.org Message-ID: <20080630151740.GQ17364@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.074, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: Bernd Walter Subject: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 15:30:36 -0000 This is not about a specific hardware - I have a general problem. Normaly I run ntpdate and ntpd - ntpdate sets the time on boot and then ntpd takes over to keep it in sync. What recently happend was that a server with a multiple years uptime rebootet because of a power failure and the local ntp-server wasn't up early enough, so ntpdate didn't set the clock. ntpd didn't tune the clock either, because the offset was too big. I know from debugging RTC support on arm, that the RTC only gets written on explizit time setting with ntpdate, date and such. But since ntpd only tunes the softclock and never sets the RTC it allows the RTC to run completely unsyncronized. Is there a way to regulary trigger a write to the RTC without disturbing ntpd, so that the offset never gets large? Of course I can configure ntpd to accept a large offset, but it seems wrong to me that the RTC runs unsyncronized for a large time. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 15:56:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC520106568F for ; Mon, 30 Jun 2008 15:56:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id B206E8FC16 for ; Mon, 30 Jun 2008 15:56:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m5UFtdtv026704; Mon, 30 Jun 2008 08:55:44 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <486901FB.5080308@freebsd.org> Date: Mon, 30 Jun 2008 08:55:39 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> In-Reply-To: <1214815958.3581.67.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 15:56:08 -0000 Vladimir Grebenschikov wrote: > On Thu, 2008-06-26 at 13:05 +0200, Alexey Shuvaev wrote: > >>In a nutshell the problem is that bsdcpio damages the files: > > Same here, also it shows strange warning on every directory being > copied: > > cpio: Can't create 'dst/a/b/c/3': Operation not permitted: Operation not > permitted > > Bad news, that it damaged original files also. > > PS: > upgrading now ... Let me know if you still see this problem after the upgrade. I believe it's completely fixed now. Tim From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 16:07:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2ACE106567D; Mon, 30 Jun 2008 16:07:38 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6AF3D8FC15; Mon, 30 Jun 2008 16:07:38 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru (ppp85-140-165-154.pppoe.mtu-net.ru [85.140.165.154]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m5UG7VgN005200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 20:07:36 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDLuZ-0008Zi-5l; Mon, 30 Jun 2008 20:07:27 +0400 From: Vladimir Grebenschikov To: Tim Kientzle In-Reply-To: <486901FB.5080308@freebsd.org> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 30 Jun 2008 20:07:22 +0400 Message-Id: <1214842042.8768.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 16:07:39 -0000 =F7 Mon, 30/06/2008 =D7 08:55 -0700, Tim Kientzle =D0=C9=DB=C5=D4: > Vladimir Grebenschikov wrote: > > On Thu, 2008-06-26 at 13:05 +0200, Alexey Shuvaev wrote: > >=20 > >>In a nutshell the problem is that bsdcpio damages the files: > >=20 > > Same here, also it shows strange warning on every directory being > > copied: > >=20 > > cpio: Can't create 'dst/a/b/c/3': Operation not permitted: Operation no= t > > permitted > > > > Bad news, that it damaged original files also. > >=20 > > PS:=20 > > upgrading now ... >=20 > Let me know if you still see this problem after the > upgrade. I believe it's completely fixed now. Files are not corrupted any more, but strange message for every directory still shown. > Tim >=20 --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 16:09:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BE801065675 for ; Mon, 30 Jun 2008 16:09:14 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id A44E88FC0A for ; Mon, 30 Jun 2008 16:09:13 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id 9FF6224D22; Mon, 30 Jun 2008 17:51:38 +0200 (SAST) Date: Mon, 30 Jun 2008 17:51:38 +0200 From: Aragon Gouveia To: ticso@cicely.de Message-ID: <20080630155138.GA3084@phat.za.net> References: <20080630151740.GQ17364@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080630151740.GQ17364@cicely7.cicely.de> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Cc: freebsd-current@freebsd.org Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 16:09:14 -0000 adjkerntz(8) ? | By Bernd Walter | [ 2008-06-30 17:30 +0200 ] > This is not about a specific hardware - I have a general problem. > Normaly I run ntpdate and ntpd - ntpdate sets the time on boot and > then ntpd takes over to keep it in sync. > What recently happend was that a server with a multiple years uptime > rebootet because of a power failure and the local ntp-server wasn't > up early enough, so ntpdate didn't set the clock. > ntpd didn't tune the clock either, because the offset was too big. > I know from debugging RTC support on arm, that the RTC only gets > written on explizit time setting with ntpdate, date and such. > But since ntpd only tunes the softclock and never sets the RTC it > allows the RTC to run completely unsyncronized. > Is there a way to regulary trigger a write to the RTC without > disturbing ntpd, so that the offset never gets large? > Of course I can configure ntpd to accept a large offset, but it seems > wrong to me that the RTC runs unsyncronized for a large time. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 16:21:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8915D106567F for ; Mon, 30 Jun 2008 16:21:15 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 4D9BB8FC16 for ; Mon, 30 Jun 2008 16:21:15 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 16682170E4; Mon, 30 Jun 2008 15:54:23 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m5UFsN2v007577; Mon, 30 Jun 2008 15:54:23 GMT (envelope-from phk@critter.freebsd.dk) To: ticso@cicely.de From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 30 Jun 2008 17:17:44 +0200." <20080630151740.GQ17364@cicely7.cicely.de> Date: Mon, 30 Jun 2008 15:54:23 +0000 Message-ID: <7576.1214841263@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Bernd Walter , freebsd-current@freebsd.org Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 16:21:15 -0000 In message <20080630151740.GQ17364@cicely7.cicely.de>, Bernd Walter writes: >But since ntpd only tunes the softclock and never sets the RTC it >allows the RTC to run completely unsyncronized. >Is there a way to regulary trigger a write to the RTC without >disturbing ntpd, so that the offset never gets large? Ideally the adjkerntz we run in cron every night should do that. The easiest way would be to add a sysctl that when written does it, thatway systems without adjkerntz could do it with a cronjob that just sysctl's that variable directly. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 16:59:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8538106564A for ; Mon, 30 Jun 2008 16:59:28 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5DF808FC19 for ; Mon, 30 Jun 2008 16:59:28 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m5UGxPFa099000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Jun 2008 18:59:26 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m5UGxMcq064239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 18:59:22 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m5UGxMO4024613; Mon, 30 Jun 2008 18:59:22 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m5UGxLOq024612; Mon, 30 Jun 2008 18:59:21 +0200 (CEST) (envelope-from ticso) Date: Mon, 30 Jun 2008 18:59:21 +0200 From: Bernd Walter To: Poul-Henning Kamp Message-ID: <20080630165919.GR17364@cicely7.cicely.de> References: <20080630151740.GQ17364@cicely7.cicely.de> <7576.1214841263@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7576.1214841263@critter.freebsd.dk> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.071, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: Bernd Walter , freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 16:59:28 -0000 On Mon, Jun 30, 2008 at 03:54:23PM +0000, Poul-Henning Kamp wrote: > In message <20080630151740.GQ17364@cicely7.cicely.de>, Bernd Walter writes: > > >But since ntpd only tunes the softclock and never sets the RTC it > >allows the RTC to run completely unsyncronized. > >Is there a way to regulary trigger a write to the RTC without > >disturbing ntpd, so that the offset never gets large? > > Ideally the adjkerntz we run in cron every night should do that. > > The easiest way would be to add a sysctl that when written does it, > thatway systems without adjkerntz could do it with a cronjob that > just sysctl's that variable directly. Ok - a sysctl which, when written calls resettodr(). Plus adding this call to adjkerntz independend of wall_cmos_clock existence. I wonder if people might forget about this when they remove adjkerntz from a small system. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 17:02:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A1721065670 for ; Mon, 30 Jun 2008 17:02:05 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 84F948FC1F for ; Mon, 30 Jun 2008 17:02:04 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m5UH22T0099106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Jun 2008 19:02:03 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m5UH1rFY064361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jun 2008 19:01:54 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m5UH1r18024640; Mon, 30 Jun 2008 19:01:53 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m5UH1rrM024639; Mon, 30 Jun 2008 19:01:53 +0200 (CEST) (envelope-from ticso) Date: Mon, 30 Jun 2008 19:01:53 +0200 From: Bernd Walter To: Aragon Gouveia Message-ID: <20080630170152.GS17364@cicely7.cicely.de> References: <20080630151740.GQ17364@cicely7.cicely.de> <20080630155138.GA3084@phat.za.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080630155138.GA3084@phat.za.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.068, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 17:02:05 -0000 On Mon, Jun 30, 2008 at 05:51:38PM +0200, Aragon Gouveia wrote: > adjkerntz(8) ? adjkerntz, as is, does this only when doing daylight switching. This is only true for systems running their RTC on localtime. Without starting a discussion about running your RTC on localtime vs UTC - some RTC chips can only do UTC. > | By Bernd Walter > | [ 2008-06-30 17:30 +0200 ] > > This is not about a specific hardware - I have a general problem. > > Normaly I run ntpdate and ntpd - ntpdate sets the time on boot and > > then ntpd takes over to keep it in sync. > > What recently happend was that a server with a multiple years uptime > > rebootet because of a power failure and the local ntp-server wasn't > > up early enough, so ntpdate didn't set the clock. > > ntpd didn't tune the clock either, because the offset was too big. > > I know from debugging RTC support on arm, that the RTC only gets > > written on explizit time setting with ntpdate, date and such. > > But since ntpd only tunes the softclock and never sets the RTC it > > allows the RTC to run completely unsyncronized. > > Is there a way to regulary trigger a write to the RTC without > > disturbing ntpd, so that the offset never gets large? > > Of course I can configure ntpd to accept a large offset, but it seems > > wrong to me that the RTC runs unsyncronized for a large time. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 17:04:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E0261065670 for ; Mon, 30 Jun 2008 17:04:46 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 102168FC1C for ; Mon, 30 Jun 2008 17:04:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 2004E170E4; Mon, 30 Jun 2008 17:04:43 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m5UH4h5c008063; Mon, 30 Jun 2008 17:04:43 GMT (envelope-from phk@critter.freebsd.dk) To: ticso@cicely.de From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 30 Jun 2008 18:59:21 +0200." <20080630165919.GR17364@cicely7.cicely.de> Date: Mon, 30 Jun 2008 17:04:43 +0000 Message-ID: <8062.1214845483@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Bernd Walter , freebsd-current@freebsd.org Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 17:04:46 -0000 In message <20080630165919.GR17364@cicely7.cicely.de>, Bernd Walter writes: >> The easiest way would be to add a sysctl that when written does it, >> thatway systems without adjkerntz could do it with a cronjob that >> just sysctl's that variable directly. > >Ok - a sysctl which, when written calls resettodr(). >Plus adding this call to adjkerntz independend of wall_cmos_clock >existence. > >I wonder if people might forget about this when they remove adjkerntz >from a small system. The alternative is to do it in the kernel, but I'm not sure if you can do it from a callout, so it's not quite trivial to add. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 19:05:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A40B10656A8 for ; Mon, 30 Jun 2008 19:05:09 +0000 (UTC) (envelope-from mva@sysfault.org) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) by mx1.freebsd.org (Postfix) with ESMTP id EC44D8FC1F for ; Mon, 30 Jun 2008 19:05:08 +0000 (UTC) (envelope-from mva@sysfault.org) Received: from [89.182.204.103] (helo=localhost) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1KDOS1-0008S6-6M for freebsd-current@freebsd.org; Mon, 30 Jun 2008 20:50:09 +0200 Date: Mon, 30 Jun 2008 20:53:04 +0200 From: Marcus von Appen To: freebsd-current@freebsd.org Message-ID: <20080630185304.GA1031@medusa.sysfault.org> Mail-Followup-To: freebsd-current@freebsd.org References: <9f8af95f0806300746qde2a282kbade983626c20495@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline In-Reply-To: <9f8af95f0806300746qde2a282kbade983626c20495@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Df-Sender: 320095 Subject: Re: Wacom Tablet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcus von Appen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 19:05:09 -0000 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On, Mon Jun 30, 2008, james toy wrote: > Hey all, >=20 > I have an IBM x61t tablet -- serial wacom -- I was just > wondering if anyone had a good place to start -- a generic how to for > freebsd i've seen the one at linuxwacom.sourceforge.net -- is this all i > need? Is there somewhere special to look in the freebsd docs? Sorry for > the simple question. Hope everyone is well. Bartosz Fabianowsky wrote a module[0] for wacom tablets, which works very well with my Graphire USB tablet on RELENG_7. You might want to give it a t= ry. [0] http://www.chillt.de/bsdwacom.tbz Regards Marcus --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhpK5AACgkQo/JpszXavhyucwCcDjZrL0t1tvBM/5jJqPmU/ViW qyEAn2eVpOsBUd4x1b9v2vzbu4S8RqQ4 =oaK+ -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 19:13:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C703F1065688 for ; Mon, 30 Jun 2008 19:13:53 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.freebsd.org (Postfix) with ESMTP id 40DA58FC16 for ; Mon, 30 Jun 2008 19:13:53 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail18.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5UJDeNV028842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 05:13:41 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m5UJDejC007205; Tue, 1 Jul 2008 05:13:40 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m5UJDd2J007204; Tue, 1 Jul 2008 05:13:39 +1000 (EST) (envelope-from peter) Date: Tue, 1 Jul 2008 05:13:39 +1000 From: Peter Jeremy To: ticso@cicely.de Message-ID: <20080630191339.GS29380@server.vk2pj.dyndns.org> References: <20080630151740.GQ17364@cicely7.cicely.de> <7576.1214841263@critter.freebsd.dk> <20080630165919.GR17364@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="v9Ux+11Zm5mwPlX6" Content-Disposition: inline In-Reply-To: <20080630165919.GR17364@cicely7.cicely.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Poul-Henning Kamp , Bernd Walter , freebsd-current@freebsd.org Subject: Re: RTC problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 19:13:53 -0000 --v9Ux+11Zm5mwPlX6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-30 18:59:21 +0200, Bernd Walter wrote: >Ok - a sysctl which, when written calls resettodr(). According to kern/subr_clock.c, machdep.adjkerntz already does this so something like sysctl machdep.adjkerntz=3D`sysctl -n machdep.adjkerntz` should work. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --v9Ux+11Zm5mwPlX6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhpMGMACgkQ/opHv/APuIeQmQCgxAGJH2Cc8JZsWqABWvZjwVUa iE4An0RmOidYRNQcTtQzttMzeu9YbeB5 =nwh5 -----END PGP SIGNATURE----- --v9Ux+11Zm5mwPlX6-- From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 20:13:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 520041065670 for ; Mon, 30 Jun 2008 20:13:14 +0000 (UTC) (envelope-from dougk@dougk-ff7.net) Received: from mail.dougk-ff7.net (shen.liquidneon.com [216.87.78.181]) by mx1.freebsd.org (Postfix) with ESMTP id 3D0CF8FC14 for ; Mon, 30 Jun 2008 20:13:13 +0000 (UTC) (envelope-from dougk@dougk-ff7.net) Received: from localhost (localhost.liquidneon.com [127.0.0.1]) by mail.dougk-ff7.net (Postfix) with ESMTP id 041D595845; Mon, 30 Jun 2008 13:54:39 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=dougk-ff7.net; s=mail; t=1214855679; bh=R0MWKCsLALDZRKwI005bCYFU+iw=; h=Date:From:To:Cc: Subject:Message-ID:References:MIME-Version:Content-Type: In-Reply-To; b=TLhLPjo6cQbU6tyAfGx0IPjk4fhDwbYjHgJ+7YFfnxkVxR5G7Ir ZSxRZFrcWopyavLvUTPkymQrnP3bC+VbK/tzEGqrbCqjxFs+Wyr/PW4IrnCm0GYrRb0 q5tjoNQAq1i/G33fJ/WVBdkP4KpHiYfsexq/lY9QfNBssSNWogZCU= X-Virus-Scanned: by amavisd-new at dougk-ff7.net Received: from mail.dougk-ff7.net ([127.0.0.1]) by localhost (shen.liquidneon.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id oOeIag7xX7XM; Mon, 30 Jun 2008 13:54:36 -0600 (MDT) Received: from dougk-ff7.net (CPE-65-28-64-154.kc.res.rr.com [65.28.64.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.dougk-ff7.net (Postfix) with ESMTPSA id 0414D9582E; Mon, 30 Jun 2008 13:54:35 -0600 (MDT) Date: Mon, 30 Jun 2008 14:55:59 -0500 From: Doug Kelly To: james toy Message-ID: <20080630195558.GD87398@dougk-ff7.net> References: <9f8af95f0806300746qde2a282kbade983626c20495@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9f8af95f0806300746qde2a282kbade983626c20495@mail.gmail.com> X-Operating-System: FreeBSD tsukasa.dougk-ff7.net 6.2-STABLE FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.17 (2007-11-01) Cc: FreeBSD Current Subject: Re: Wacom Tablet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 20:13:16 -0000 On Mon, Jun 30, 2008 at 10:46:53AM -0400, james toy wrote: > Hey all, > > I have an IBM x61t tablet -- serial wacom -- I was just > wondering if anyone had a good place to start -- a generic how to for > freebsd i've seen the one at linuxwacom.sourceforge.net -- is this all i > need? Is there somewhere special to look in the freebsd docs? Sorry for > the simple question. Hope everyone is well. > Last I tried this on FreeBSD with my X60 Tablet, the linuxwacom driver built for FreeBSD worked fine, but as I recall, lacked pressure sensitivity. Oddly, the worst problem I had at the time was the unfinished ipw driver. But in short, yes, the linuxwacom steps should work fine. --Doug From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 23:10:23 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC5431065670; Mon, 30 Jun 2008 23:10:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1143B8FC1E; Mon, 30 Jun 2008 23:10:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5UNA9vo022818; Mon, 30 Jun 2008 19:10:16 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-arch@freebsd.org Date: Mon, 30 Jun 2008 15:17:21 -0400 User-Agent: KMail/1.9.7 References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> In-Reply-To: <20080629180126.F90836@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806301517.22173.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 30 Jun 2008 19:10:16 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7596/Mon Jun 30 18:21:48 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: arch@freebsd.org, Robert Watson , current@freebsd.org, net@freebsd.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 23:10:23 -0000 On Sunday 29 June 2008 01:02:49 pm Robert Watson wrote: > > On Sat, 24 May 2008, Robert Watson wrote: > > > Just as a reminder, we've just about reached the one month date before > > IFF_NEEDSGIANT drivers are disabled in the build. You can find a > > description of the general problem and list of specific drivers below. > > > > As USB work is on-going, I will *not* disable the USB drivers at this time, > > but all other drivers in the list below will be disabled on 26 June. They > > will remain in the tree, easily accessible for patch distribution and > > re-enabling, until October, when any remaining non-MPSAFE drivers will be > > deleted in 8.x. FreeBSD 8.0 will not ship with compatibility shims to > > support non-MPSAFE network device drivers. > > An FYI on the state of things here: in the last month, John has updated a > number of device drivers to be MPSAFE, and the USB work remains in-flight. > I'm holding fire a bit on disabling IFF_NEEDSGIANT while things settle and I > catch up on driver state, and will likely send out an update next week > regarding which device drivers remain on the kill list, and generally what the > status of this project is. Pending someone testing them real soon, I will be axeing at least sbsh, sbni, snc, and cnw this week (I had someone e-mail who said they would test the arl(4) pages). I still want to work on if_plip (which means locking ppbus) and if_ic (iicbus). I started working on locking iicbus recently FWIW. Aside from USB that leaves ray(4) (which does tsleep() all over the place including in interrupt handlers.. this couldn't have worked on 4.x all that well) and the various Cronyx drivers which interface with netgraph. Someone who knows netgraph can probably step up to lock those. Could also ask rik@ directly about the Cronyx drivers (cx, ctau, and cp). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 04:40:15 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D74071065673 for ; Tue, 1 Jul 2008 04:40:15 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 80EB18FC19 for ; Tue, 1 Jul 2008 04:40:09 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.24.21.170]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m614e5QT007586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 08:40:06 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDO7N-000G13-DF; Mon, 30 Jun 2008 22:28:49 +0400 From: Vladimir Grebenschikov To: David Xu In-Reply-To: <200806240737.m5O7bhc5018813@repoman.freebsd.org> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Mon, 30 Jun 2008 22:28:44 +0400 Message-Id: <1214850524.42354.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, current@FreeBSD.org, cvs-all@FreeBSD.org Subject: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 04:40:15 -0000 On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: This commit makes threaded application almost unusable on 8-CURRENT. Applications eat 100% CPU all the time and works _very_ slowly. (top shows several threads for every constantly applications eating CPU) Following applications are affected for me: firefox, evolution, eclipse (probably more). Reverting user-land part of commit fixes problem, reverting kernel changes nothing regarding the problem. I have: FreeBSD 8.0-CURRENT #0: Fri Jun 20 17:14:23 MSD 2008 root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 > davidxu 2008-06-24 07:32:12 UTC > > FreeBSD src repository > > Modified files: > lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h > sys/kern kern_umtx.c > sys/sys umtx.h > Log: > SVN rev 179970 on 2008-06-24 07:32:12Z by davidxu > > Add two commands to _umtx_op system call to allow a simple mutex to be > locked and unlocked completely in userland. by locking and unlocking mutex > in userland, it reduces the total time a mutex is locked by a thread, > in some application code, a mutex only protects a small piece of code, the > code's execution time is less than a simple system call, if a lock contention > happens, however in current implemenation, the lock holder has to extend its > locking time and enter kernel to unlock it, the change avoids this disadvantage, > it first sets mutex to free state and then enters kernel and wake one waiter > up. This improves performance dramatically in some sysbench mutex tests. > > Tested by: kris > Sounds great: jeff > > Revision Changes Path > 1.75 +33 -35 src/lib/libthr/thread/thr_mutex.c > 1.17 +60 -10 src/lib/libthr/thread/thr_umtx.c > 1.14 +13 -9 src/lib/libthr/thread/thr_umtx.h > 1.71 +142 -35 src/sys/kern/kern_umtx.c > 1.33 +3 -1 src/sys/sys/umtx.h > _______________________________________________ > cvs-src@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/cvs-src > To unsubscribe, send any mail to "cvs-src-unsubscribe@freebsd.org" -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 05:46:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59904106567D for ; Tue, 1 Jul 2008 05:46:55 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1DE6B8FC1E for ; Tue, 1 Jul 2008 05:46:55 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m615kitv030977; Mon, 30 Jun 2008 22:46:47 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4869C4C4.1050806@freebsd.org> Date: Mon, 30 Jun 2008 22:46:44 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> In-Reply-To: <1214842042.8768.12.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 05:46:55 -0000 Vladimir Grebenschikov wrote: > > > Files are not corrupted any more, but strange message for every > directory still shown. Yes. I think I just fixed this. Please let me know if you see any other problems. Tim From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 08:17:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1875F1065675; Tue, 1 Jul 2008 08:17:55 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7B47E8FC1F; Tue, 1 Jul 2008 08:17:52 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m618Hlwf022826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 12:17:48 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDb3b-000Ag5-FE; Tue, 01 Jul 2008 12:17:47 +0400 From: Vladimir Grebenschikov To: Tim Kientzle In-Reply-To: <4869C4C4.1050806@freebsd.org> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 01 Jul 2008 12:17:46 +0400 Message-Id: <1214900266.1947.13.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 08:17:55 -0000 On Mon, 2008-06-30 at 22:46 -0700, Tim Kientzle wrote: > Vladimir Grebenschikov wrote: > > > > > > Files are not corrupted any more, but strange message for every > > directory still shown. > > Yes. I think I just fixed this. Please let me know if > you see any other problems. Now it works ok with directories, but I think, condition is too generic: + if (cpio->option_link + && archive_entry_filetype(entry) != AE_IFDIR) + { New cpio: $ ln -s /none a/symlink $ find a | cpio -dumpl dst/ cpio: Can't create 'dst/a/symlink': No such file or directory: No such file or directory $ ls -l dst/a/symlink ls: dst/a/symlink: No such file or directory $ Old cpio: $ mkdir zz dst $ ln -s /none zz/symlink $ find zz | cpio -dumpl dst/ 0 blocks $ ls -l dst/zz/symlink lrwxrwxrwx 1 vova 207 5 Jul 1 12:45 dst/zz/symlink -> /none $ > Tim -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 08:49:15 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFEAA1065688; Tue, 1 Jul 2008 08:49:15 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout4.freenet.de (mout4.freenet.de [IPv6:2001:748:100:40::2:6]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB1C8FC38; Tue, 1 Jul 2008 08:49:15 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.23] (helo=13.mx.freenet.de) by mout4.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #19) id 1KDbY1-00007V-Mq; Tue, 01 Jul 2008 10:49:13 +0200 Received: from mad5a.m.pppool.de ([89.49.173.90]:57248 helo=peedub.jennejohn.org) by 13.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #12) id 1KDbY1-00068x-Bv; Tue, 01 Jul 2008 10:49:13 +0200 Date: Tue, 1 Jul 2008 10:49:12 +0200 From: Gary Jennejohn To: vova@fbsd.ru Message-ID: <20080701104912.5e9e16e0@peedub.jennejohn.org> In-Reply-To: <1214850524.42354.9.camel@localhost> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, David Xu , cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 08:49:16 -0000 On Mon, 30 Jun 2008 22:28:44 +0400 Vladimir Grebenschikov wrote: > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > This commit makes threaded application almost unusable on 8-CURRENT. > > Applications eat 100% CPU all the time and works _very_ slowly. > (top shows several threads for every constantly applications eating CPU) > > Following applications are affected for me: firefox, evolution, eclipse > (probably more). > > Reverting user-land part of commit fixes problem, reverting kernel > changes nothing regarding the problem. > > I have: > FreeBSD 8.0-CURRENT #0: Fri Jun 20 17:14:23 MSD 2008 > root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.01-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100000 > AMD Features2=0x1 > Cores per package: 2 > [snip commit message] Did you recompile these misbehaving applications? I ask because I installed a fresh world yesterday, without recompiling any ports, and I'm _not_ seeing any misbehavior with firefox. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 08:58:03 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F4C11065673; Tue, 1 Jul 2008 08:58:03 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id BD2D88FC2B; Tue, 1 Jul 2008 08:58:02 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m618vwei000778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 12:57:59 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDbgU-0000L3-Qp; Tue, 01 Jul 2008 12:57:58 +0400 From: Vladimir Grebenschikov To: gary.jennejohn@freenet.de In-Reply-To: <20080701104912.5e9e16e0@peedub.jennejohn.org> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 01 Jul 2008 12:57:58 +0400 Message-Id: <1214902678.1947.23.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, David Xu , cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 08:58:03 -0000 On Tue, 2008-07-01 at 10:49 +0200, Gary Jennejohn wrote: > On Mon, 30 Jun 2008 22:28:44 +0400 > Vladimir Grebenschikov wrote: > > > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > > > This commit makes threaded application almost unusable on 8-CURRENT. > > > > Applications eat 100% CPU all the time and works _very_ slowly. > > (top shows several threads for every constantly applications eating CPU) > > > > Following applications are affected for me: firefox, evolution, eclipse > > (probably more). > > > > Reverting user-land part of commit fixes problem, reverting kernel > > changes nothing regarding the problem. > > > > I have: > > FreeBSD 8.0-CURRENT #0: Fri Jun 20 17:14:23 MSD 2008 > > root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.01-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > Features=0xbfebfbff > > Features2=0xe3bd > > AMD Features=0x20100000 > > AMD Features2=0x1 > > Cores per package: 2 > > > [snip commit message] > > Did you recompile these misbehaving applications? > > I ask because I installed a fresh world yesterday, without recompiling > any ports, and I'm _not_ seeing any misbehavior with firefox. Yes, I've tried to rebuild firefox - nothing changed. Probably need to rebuild something else (glib or what ?). In that case one need to bump lib version or/and announcer that problem. > --- > Gary Jennejohn -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 09:14:48 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 241F6106567F; Tue, 1 Jul 2008 09:14:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id E74E58FC27; Tue, 1 Jul 2008 09:14:47 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 37EF31325BE; Tue, 1 Jul 2008 05:14:47 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 01 Jul 2008 05:14:47 -0400 X-Sasl-enc: pg1O+wpjmR4ds5E47tjB60Xr0CQ1z9taMYSboiCqX0zU 1214903686 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 767C713356; Tue, 1 Jul 2008 05:14:46 -0400 (EDT) Message-ID: <4869F586.7010708@FreeBSD.org> Date: Tue, 01 Jul 2008 10:14:46 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Robert Watson References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> In-Reply-To: <20080629180126.F90836@fledge.watson.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org, current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 09:14:48 -0000 Robert Watson wrote: > > An FYI on the state of things here: in the last month, John has > updated a number of device drivers to be MPSAFE, and the USB work > remains in-flight. I'm holding fire a bit on disabling IFF_NEEDSGIANT > while things settle and I catch up on driver state, and will likely > send out an update next week regarding which device drivers remain on > the kill list, and generally what the status of this project is. Goliath needs to get stoned, it's been a major hurdle in doing IGMPv3/SSM because of the locking fandango. I look forward to it. [For those who ask, what the hell? IGMPv3 potentially makes your wireless multicast better with or without little things like SSM, because of protocol robustness, compact state-changes, and the use of a single link-local IPv4 group for state-change reports, making it easier for your switches to actually do their job.] From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 10:29:39 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6A2E1065672; Tue, 1 Jul 2008 10:29:39 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2AF7A8FC22; Tue, 1 Jul 2008 10:29:38 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m61ATXjj012820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 14:29:34 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDd77-0007bg-Fj; Tue, 01 Jul 2008 14:29:33 +0400 From: Vladimir Grebenschikov To: gary.jennejohn@freenet.de In-Reply-To: <20080701104912.5e9e16e0@peedub.jennejohn.org> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 01 Jul 2008 14:29:32 +0400 Message-Id: <1214908172.1947.29.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, David Xu , cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 10:29:39 -0000 On Tue, 2008-07-01 at 10:49 +0200, Gary Jennejohn wrote: > On Mon, 30 Jun 2008 22:28:44 +0400 > Vladimir Grebenschikov wrote: > > > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > > > This commit makes threaded application almost unusable on 8-CURRENT. > > > > Applications eat 100% CPU all the time and works _very_ slowly. > > (top shows several threads for every constantly applications eating CPU) > > > > Following applications are affected for me: firefox, evolution, eclipse > > (probably more). > > > > Reverting user-land part of commit fixes problem, reverting kernel > > changes nothing regarding the problem. ... > Did you recompile these misbehaving applications? > > I ask because I installed a fresh world yesterday, without recompiling > any ports, and I'm _not_ seeing any misbehavior with firefox. Do you have SMP system ? > Gary Jennejohn -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 08:12:31 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 542981065677; Tue, 1 Jul 2008 08:12:31 +0000 (UTC) (envelope-from rehsack@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id 146968FC2B; Tue, 1 Jul 2008 08:12:30 +0000 (UTC) (envelope-from rehsack@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate01.web.de (Postfix) with ESMTP id 077B3E5F794B; Tue, 1 Jul 2008 09:53:24 +0200 (CEST) Received: from [87.149.238.95] (helo=waldorf.muppets.liwing.de) by smtp05.web.de with esmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KDafz-0003jd-00; Tue, 01 Jul 2008 09:53:23 +0200 Message-ID: <4869E272.1060606@web.de> Date: Tue, 01 Jul 2008 07:53:22 +0000 From: Jens Rehsack User-Agent: Thunderbird 2.0.0.14 (X11/20080608) MIME-Version: 1.0 To: David O'Brien Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: rehsack@web.de X-Sender: rehsack@web.de X-Provags-ID: V01U2FsdGVkX19of1k6N9uS10FJaQz9OYNNpK7R2AqskO3T5Y2n 8YZgrnE9x/kBJOFFB4+a3DsieR4Kiara1tZYYr6aMIYU+UeyJZ 8EwKK4hcI= X-Mailman-Approved-At: Tue, 01 Jul 2008 11:27:17 +0000 Cc: FreeBSD-Current-List Subject: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 08:12:31 -0000 Hi David, because you are the maintainer of src/contrib/binutils, I first want to ask you before I start to update src/contrib/binutils. I've read the README's you've placed there, but 2 questions remain: 1) How can I create a patch using a cvs-checkout when I do not have write permissions to the repository? This is no request for a commit bit (to much accountability), more a technical request. Do I need to use cvsup from ports to get a copy of the cvs server and checkout against my local copy? 2) Is it ok to do it on a FreeBSD7-Stable, as long no change between the RELENG7 branch and the HEAD prevents merge? Or is it mandatory to test it with -CURRENT? I ask, because -CURRENT maybe unstable by definition, and I don't want to search for errors in my work come in by experimental code. I have no problem, when a first patch exists, to test it on -CURRENT, but it should be the 2nd step (for me). Best regards, Jens From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 12:03:38 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D83D10656EC for ; Tue, 1 Jul 2008 12:03:38 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE4D8FC25 for ; Tue, 1 Jul 2008 12:03:37 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1321451wah.3 for ; Tue, 01 Jul 2008 05:03:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=yjE6O8sukEXbEPm716E0TronGr+7HLacyoaViI+9U0Q=; b=NH3M2tp5PHw4b1z55apDMbiuYuolqGyiOBZdQJ0zGXbizaKxM+eFOs0CjlwCk3V+OS QkRny4mrmf5+O4KZ+nOBNDxU1BWFJ6eA6B/e19twwV2DOnymzQgGeRlrhHjrqDqcnlLC FX8tgfeZBJwkfT74qTQ5Xf5XDk3iftPenWEII= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=ovvJ17z6jUTpYyz02lgTWBHBPH2x6T59Kg3c/EcxZlNp+d1N6K5c57v2uymtzGP+FQ xCpgzviMAQjCXnH8VVPlp5lqnUZaKSoyz0zbzfR+vKv9gb2z3sOjAMfyCXj0TnogxkFR 0QUFbZBGE7Q5vh3j6Ud/0Q7DHZS5ugCJ299dM= Received: by 10.114.182.15 with SMTP id e15mr5333237waf.186.1214912079994; Tue, 01 Jul 2008 04:34:39 -0700 (PDT) Received: from kan.dnsalias.net ( [24.218.183.247]) by mx.google.com with ESMTPS id 4sm1990171yxj.7.2008.07.01.04.34.39 (version=SSLv3 cipher=RC4-MD5); Tue, 01 Jul 2008 04:34:39 -0700 (PDT) Date: Tue, 1 Jul 2008 07:34:34 -0400 From: Alexander Kabaev To: vova@fbsd.ru Message-ID: <20080701073434.523a72ea@kan.dnsalias.net> In-Reply-To: <1214908172.1947.29.camel@localhost> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/lenhXljRDDmfuDGz0GQbsGw"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: current@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 12:03:38 -0000 --Sig_/lenhXljRDDmfuDGz0GQbsGw Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 01 Jul 2008 14:29:32 +0400 Vladimir Grebenschikov wrote: > On Tue, 2008-07-01 at 10:49 +0200, Gary Jennejohn wrote: > > On Mon, 30 Jun 2008 22:28:44 +0400 > > Vladimir Grebenschikov wrote: > >=20 > > > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > >=20 > > > This commit makes threaded application almost unusable on > > > 8-CURRENT. > > >=20 > > > Applications eat 100% CPU all the time and works _very_ slowly. > > > (top shows several threads for every constantly applications > > > eating CPU) > > >=20 > > > Following applications are affected for me: firefox, evolution, > > > eclipse (probably more). > > >=20 > > > Reverting user-land part of commit fixes problem, reverting kernel > > > changes nothing regarding the problem. >=20 > ... >=20 > > Did you recompile these misbehaving applications? > >=20 > > I ask because I installed a fresh world yesterday, without > > recompiling any ports, and I'm _not_ seeing any misbehavior with > > firefox. >=20 > Do you have SMP system ?=20 >=20 Works fine for me on amd64 SMP and i386 UP systems, world build on June 29th on both. Could you ktrace firefox-bin while it spins? Just in case... --=20 Alexander Kabaev --Sig_/lenhXljRDDmfuDGz0GQbsGw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFIahZKQ6z1jMm+XZYRAvEeAJ9BiyU6ZqwplliOaIi3jCdNIGyYtwCfUa4I 6KiEh2srCXixgHtLGOb6fCw= =yAx6 -----END PGP SIGNATURE----- --Sig_/lenhXljRDDmfuDGz0GQbsGw-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 12:12:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 219E11065673 for ; Tue, 1 Jul 2008 12:12:48 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id EDB4B8FC0A for ; Tue, 1 Jul 2008 12:12:47 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id kafR1Z0070EPchoA504l00; Tue, 01 Jul 2008 12:12:47 +0000 Received: from mail.cokane.org ([24.60.133.163]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id kcCm1Z0013Xh0XL8McCmhZ; Tue, 01 Jul 2008 12:12:47 +0000 X-Authority-Analysis: v=1.0 c=1 a=W7PIFKygEJwA:10 a=Y7MndFLvfEUA:10 a=mao6I00Vmj4Fn3PGtRcA:9 a=y6YsuFow1OwX_E7svXSHAb89uBEA:4 a=LY0hPdMaydYA:10 a=h78ISFpv37-uUuO8q4QA:9 a=eTwWfg9dwDy5wVzvRYqcndc0SFQA:4 a=rPt6xJ-oxjAA:10 Received: by mail.cokane.org (Postfix, from userid 103) id BECF016B55F; Tue, 1 Jul 2008 08:12:45 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id 4FE6416B55B; Tue, 1 Jul 2008 08:12:32 -0400 (EDT) From: Coleman Kane To: Alexander Kabaev In-Reply-To: <20080701073434.523a72ea@kan.dnsalias.net> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> <20080701073434.523a72ea@kan.dnsalias.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-zE5NP1TyCyhRLV/JI7gp" Organization: FreeBSD Project Date: Tue, 01 Jul 2008 08:10:39 -0400 Message-Id: <1214914239.1802.31.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Cc: vova@fbsd.ru, current@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 12:12:48 -0000 --=-zE5NP1TyCyhRLV/JI7gp Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-07-01 at 07:34 -0400, Alexander Kabaev wrote: > On Tue, 01 Jul 2008 14:29:32 +0400 > Vladimir Grebenschikov wrote: >=20 > > On Tue, 2008-07-01 at 10:49 +0200, Gary Jennejohn wrote: > > > On Mon, 30 Jun 2008 22:28:44 +0400 > > > Vladimir Grebenschikov wrote: > > >=20 > > > > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > > >=20 > > > > This commit makes threaded application almost unusable on > > > > 8-CURRENT. > > > >=20 > > > > Applications eat 100% CPU all the time and works _very_ slowly. > > > > (top shows several threads for every constantly applications > > > > eating CPU) > > > >=20 > > > > Following applications are affected for me: firefox, evolution, > > > > eclipse (probably more). > > > >=20 > > > > Reverting user-land part of commit fixes problem, reverting kernel > > > > changes nothing regarding the problem. > >=20 > > ... > >=20 > > > Did you recompile these misbehaving applications? > > >=20 > > > I ask because I installed a fresh world yesterday, without > > > recompiling any ports, and I'm _not_ seeing any misbehavior with > > > firefox. > >=20 > > Do you have SMP system ?=20 > >=20 > Works fine for me on amd64 SMP and i386 UP systems, world build on June > 29th on both. >=20 > Could you ktrace firefox-bin while it spins? Just in case... >=20 Firefox depends upon a lot of external things, including glib, nss, and nspr (among others, probably) which would propagate thread-lib bugs even after the main app has been recompiled. I suggest running ldd on /usr/local/lib/firefox/firefox-bin (and other shared objects in that dir) to find out what all you might need to rebuild. At the very least, I'd expect a rebuild of nspr and nss to be mandatory. I *think* firefox uses nspr's thread implementation, and not the one from gthread (glib). --=20 Coleman Kane --=-zE5NP1TyCyhRLV/JI7gp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkhqHrwACgkQcMSxQcXat5fzrwCdH++9r/X+p0eK/KJ1oW//tvc2 IaAAnRrL8HoWyurikYIZ0WK4WVJ0v61i =0/qU -----END PGP SIGNATURE----- --=-zE5NP1TyCyhRLV/JI7gp-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 12:41:14 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5F361065684 for ; Tue, 1 Jul 2008 12:41:14 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id 4E90C8FC16 for ; Tue, 1 Jul 2008 12:41:14 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.22] (helo=12.mx.freenet.de) by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #19) id 1KDfAW-0008J9-OL; Tue, 01 Jul 2008 14:41:12 +0200 Received: from mad5a.m.pppool.de ([89.49.173.90]:58234 helo=peedub.jennejohn.org) by 12.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #12) id 1KDfAW-0003YA-GK; Tue, 01 Jul 2008 14:41:12 +0200 Date: Tue, 1 Jul 2008 14:41:11 +0200 From: Gary Jennejohn To: vova@fbsd.ru Message-ID: <20080701144111.02c49938@peedub.jennejohn.org> In-Reply-To: <1214908172.1947.29.camel@localhost> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 12:41:14 -0000 On Tue, 01 Jul 2008 14:29:32 +0400 Vladimir Grebenschikov wrote: > On Tue, 2008-07-01 at 10:49 +0200, Gary Jennejohn wrote: > > On Mon, 30 Jun 2008 22:28:44 +0400 > > Vladimir Grebenschikov wrote: > > > > > On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: > > > > > > This commit makes threaded application almost unusable on 8-CURRENT. > > > > > > Applications eat 100% CPU all the time and works _very_ slowly. > > > (top shows several threads for every constantly applications eating CPU) > > > > > > Following applications are affected for me: firefox, evolution, eclipse > > > (probably more). > > > > > > Reverting user-land part of commit fixes problem, reverting kernel > > > changes nothing regarding the problem. > > ... > > > Did you recompile these misbehaving applications? > > > > I ask because I installed a fresh world yesterday, without recompiling > > any ports, and I'm _not_ seeing any misbehavior with firefox. > > Do you have SMP system ? > Yes. I also run gkrellm, hacked to show both cores, and I never see firefox using an unusual amount of CPU. But as I wrote previously, my firefox is old and probably doesn't use the features which David added. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 12:45:36 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20DE41065671 for ; Tue, 1 Jul 2008 12:45:36 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224]) by mx1.freebsd.org (Postfix) with ESMTP id C6E268FC0A for ; Tue, 1 Jul 2008 12:45:35 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so769888wra.27 for ; Tue, 01 Jul 2008 05:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=c7+Of7MNnqx1HXQFsxiJjfbkq+jjMZgntBPFC0ZPPn4=; b=lER8mtuNk3f7H/JcTMinSzHzTsYzCE5Uj4xVS8MNHDbss4nNqBLkXDGoPqX62YXW67 +p/IAazR21Jv3ZvoTscu0s1K9w26DBsVaUiagFjUGPUlq+L9A9uQ8GtE1+upxrO71bUA PgOPeFvD1WS6kqghrI0s5+sG17XWiod88KzNM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=r+MwsaujqyhlZq3CN+iOp0Bxr7NYaTBm+IU/P8ZdvbFJF1YDFE5VOsRMSkvqhJ8qtJ GCQhNF3uKelnyaPfGw4CVb5780WU6Mh2ulaHsvUpqO7aUnrptSYH+cDu7M+x//PEEtmv 97LGO3VoPuk7uAztgJ4E6KScGos8EvgMJXkh0= Received: by 10.100.31.3 with SMTP id e3mr5750565ane.21.1214916327902; Tue, 01 Jul 2008 05:45:27 -0700 (PDT) Received: from kan.dnsalias.net ( [24.218.183.247]) by mx.google.com with ESMTPS id c9sm6770256ana.9.2008.07.01.05.45.26 (version=SSLv3 cipher=RC4-MD5); Tue, 01 Jul 2008 05:45:26 -0700 (PDT) Date: Tue, 1 Jul 2008 08:45:20 -0400 From: Alexander Kabaev To: Coleman Kane Message-ID: <20080701084520.75180b9c@kan.dnsalias.net> In-Reply-To: <1214914239.1802.31.camel@localhost> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> <20080701073434.523a72ea@kan.dnsalias.net> <1214914239.1802.31.camel@localhost> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/0durCfU6KXlFwlBs1IqYe_1"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: vova@fbsd.ru, current@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 12:45:36 -0000 --Sig_/0durCfU6KXlFwlBs1IqYe_1 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 01 Jul 2008 08:10:39 -0400 Coleman Kane wrote: >=20 > Firefox depends upon a lot of external things, including glib, nss, > and nspr (among others, probably) which would propagate thread-lib > bugs even after the main app has been recompiled. I suggest running > ldd on /usr/local/lib/firefox/firefox-bin (and other shared objects > in that dir) to find out what all you might need to rebuild. At the > very least, I'd expect a rebuild of nspr and nss to be mandatory. I > *think* firefox uses nspr's thread implementation, and not the one > from gthread (glib). Recompiling is NOT the cure and people should not focus on it. If one needs to recompile anything after a commit, then commit breaks ABI which usually should be accompanied with a very good explanation of why it was necessary. David's commit does not appear to fall into that category and his changes are ABI compatible as far as userland is concerned. --=20 Alexander Kabaev --Sig_/0durCfU6KXlFwlBs1IqYe_1 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFIaibgQ6z1jMm+XZYRAvEJAJ9d3go7DFFJt5QtPAudfcpZu74kQQCfYeHK BPv7UcB5ZBJew+vB+cVOXHs= =vzTX -----END PGP SIGNATURE----- --Sig_/0durCfU6KXlFwlBs1IqYe_1-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 12:29:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 358EF1065681 for ; Tue, 1 Jul 2008 12:29:56 +0000 (UTC) (envelope-from cokane@cokane.org) Received: from QMTA05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 17E218FC23 for ; Tue, 1 Jul 2008 12:29:56 +0000 (UTC) (envelope-from cokane@cokane.org) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id kaT11Z00C0FhH24A506X00; Tue, 01 Jul 2008 12:13:56 +0000 Received: from mail.cokane.org ([24.60.133.163]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id kcDu1Z00E3Xh0XL8UcDvMf; Tue, 01 Jul 2008 12:13:56 +0000 X-Authority-Analysis: v=1.0 c=1 a=5EqdJHlVj73Prj_YJzUA:9 a=rAZWLjpDho5OuHkxGMoA:7 a=3GZt9NS_z-zTXC1eOkm34Cr6C54A:4 a=LY0hPdMaydYA:10 Received: by mail.cokane.org (Postfix, from userid 103) id 9ADD716B55D; Tue, 1 Jul 2008 08:13:54 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id 75F2D16B55B; Tue, 1 Jul 2008 08:13:40 -0400 (EDT) From: Coleman Kane To: Jens Rehsack In-Reply-To: <4869E272.1060606@web.de> References: <4869E272.1060606@web.de> Content-Type: text/plain Date: Tue, 01 Jul 2008 08:11:47 -0400 Message-Id: <1214914307.1802.33.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 01 Jul 2008 12:49:23 +0000 Cc: FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 12:29:56 -0000 On Tue, 2008-07-01 at 07:53 +0000, Jens Rehsack wrote: > Hi David, > > because you are the maintainer of src/contrib/binutils, I first want to ask > you before I start to update src/contrib/binutils. I've read the README's > you've placed there, but 2 questions remain: > > 1) How can I create a patch using a cvs-checkout when I do not have > write permissions to the repository? This is no request for a commit > bit (to much accountability), more a technical request. > Do I need to use cvsup from ports to get a copy of the cvs server > and checkout against my local copy? > 2) Is it ok to do it on a FreeBSD7-Stable, as long no change between > the RELENG7 branch and the HEAD prevents merge? Or is it mandatory > to test it with -CURRENT? > I ask, because -CURRENT maybe unstable by definition, and I don't > want to search for errors in my work come in by experimental code. > I have no problem, when a first patch exists, to test it on -CURRENT, > but it should be the 2nd step (for me). > > Best regards, > Jens This sounds intriguing.... what version of binutils are you updating to? -- Coleman Kane From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 13:01:21 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FC93106566C for ; Tue, 1 Jul 2008 13:01:21 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id A071F8FC18 for ; Tue, 1 Jul 2008 13:01:20 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA05.westchester.pa.mail.comcast.net with comcast id kbCu1Z0011HzFnQ5507V00; Tue, 01 Jul 2008 13:01:20 +0000 Received: from mail.cokane.org ([24.60.133.163]) by OMTA14.westchester.pa.mail.comcast.net with comcast id kd1J1Z00C3Xh0XL3ad1JNJ; Tue, 01 Jul 2008 13:01:19 +0000 X-Authority-Analysis: v=1.0 c=1 a=W7PIFKygEJwA:10 a=Y7MndFLvfEUA:10 a=C0mjvLovnUsPXOlwYsMA:9 a=tx8bMqCAYAAPOm7rZTngpu2CJ_AA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 a=s_bpOS0uFe5XM1_KtC0A:9 a=NSG1SzltYgmCEBmn9oPPa0EW1wQA:4 a=rPt6xJ-oxjAA:10 Received: by mail.cokane.org (Postfix, from userid 103) id DF38F16B55B; Tue, 1 Jul 2008 09:01:18 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id 6D2C416B55B; Tue, 1 Jul 2008 09:01:04 -0400 (EDT) From: Coleman Kane To: Alexander Kabaev In-Reply-To: <20080701084520.75180b9c@kan.dnsalias.net> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> <20080701073434.523a72ea@kan.dnsalias.net> <1214914239.1802.31.camel@localhost> <20080701084520.75180b9c@kan.dnsalias.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pJ+WN8jwhwoFbYynXakQ" Organization: FreeBSD Project Date: Tue, 01 Jul 2008 08:59:11 -0400 Message-Id: <1214917151.1802.36.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Cc: vova@fbsd.ru, current@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 13:01:21 -0000 --=-pJ+WN8jwhwoFbYynXakQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-07-01 at 08:45 -0400, Alexander Kabaev wrote: > On Tue, 01 Jul 2008 08:10:39 -0400 > Coleman Kane wrote: >=20 >=20 > >=20 > > Firefox depends upon a lot of external things, including glib, nss, > > and nspr (among others, probably) which would propagate thread-lib > > bugs even after the main app has been recompiled. I suggest running > > ldd on /usr/local/lib/firefox/firefox-bin (and other shared objects > > in that dir) to find out what all you might need to rebuild. At the > > very least, I'd expect a rebuild of nspr and nss to be mandatory. I > > *think* firefox uses nspr's thread implementation, and not the one > > from gthread (glib). >=20 > Recompiling is NOT the cure and people should not focus on it. >=20 > If one needs to recompile anything after a commit, then commit > breaks ABI which usually should be accompanied with a very good > explanation of why it was necessary. David's commit does not appear to > fall into that category and his changes are ABI compatible as far as > userland is concerned. >=20 >=20 Well, I'll be building/installing world from last night's cvsup today on my laptop, so I'll let you know how it works for me. --=20 Coleman Kane --=-pJ+WN8jwhwoFbYynXakQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkhqKh4ACgkQcMSxQcXat5digACfTYL5LMJRYD8g2qOb3JsXCwup pC8An1WRJAch+QcCqOh3ur2dnNKSv1sz =h1v4 -----END PGP SIGNATURE----- --=-pJ+WN8jwhwoFbYynXakQ-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 14:16:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBB95106567E; Tue, 1 Jul 2008 14:16:56 +0000 (UTC) (envelope-from rehsack@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id 7C56D8FC0A; Tue, 1 Jul 2008 14:16:56 +0000 (UTC) (envelope-from rehsack@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate02.web.de (Postfix) with ESMTP id 06D3BE3C576F; Tue, 1 Jul 2008 16:16:55 +0200 (CEST) Received: from [87.149.238.95] (helo=waldorf.muppets.liwing.de) by smtp05.web.de with esmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KDgf8-0005qX-00; Tue, 01 Jul 2008 16:16:54 +0200 Message-ID: <486A3C55.6030801@web.de> Date: Tue, 01 Jul 2008 14:16:53 +0000 From: Jens Rehsack User-Agent: Thunderbird 2.0.0.14 (X11/20080608) MIME-Version: 1.0 To: Coleman Kane References: <4869E272.1060606@web.de> <1214914307.1802.33.camel@localhost> In-Reply-To: <1214914307.1802.33.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: rehsack@web.de X-Sender: rehsack@web.de X-Provags-ID: V01U2FsdGVkX195j5UBjPntPYjF5nG86PjCuD1yxuOL/fI1fLoM MlyoYUcyBoPuiF0H9dTitlgwvgCfCQJwcOwO1oioc4rvCOLPLc IqhTYxrqk= X-Mailman-Approved-At: Tue, 01 Jul 2008 14:30:36 +0000 Cc: FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 14:16:56 -0000 Coleman Kane wrote: > On Tue, 2008-07-01 at 07:53 +0000, Jens Rehsack wrote: >> Hi David, >> >> because you are the maintainer of src/contrib/binutils, I first want to ask >> you before I start to update src/contrib/binutils. I've read the README's >> you've placed there, but 2 questions remain: [..] > This sounds intriguing.... what version of binutils are you updating to? The most recent is 2.18, in src/ is 2.12 - so I would try to update to the most recent. This is nothing which will finished tomorrow or in a week - it will take some time. To be true, the reason why I wanna do this, is using SSE3 instructions ;-) /Jens From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 14:45:37 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B7991065670; Tue, 1 Jul 2008 14:45:37 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 100578FC1D; Tue, 1 Jul 2008 14:45:36 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m61Ek5je020964; Tue, 1 Jul 2008 09:46:05 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m61Ek4qh020963; Tue, 1 Jul 2008 09:46:04 -0500 (CDT) (envelope-from brooks) Date: Tue, 1 Jul 2008 09:46:04 -0500 From: Brooks Davis To: Jens Rehsack Message-ID: <20080701144604.GB7398@lor.one-eyed-alien.net> References: <4869E272.1060606@web.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <4869E272.1060606@web.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 01 Jul 2008 09:46:05 -0500 (CDT) Cc: FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 14:45:37 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 01, 2008 at 07:53:22AM +0000, Jens Rehsack wrote: > Hi David, >=20 > because you are the maintainer of src/contrib/binutils, I first want to a= sk=20 > you before I start to update src/contrib/binutils. I've read the README's= =20 > you've placed there, but 2 questions remain: >=20 > 1) How can I create a patch using a cvs-checkout when I do not have > write permissions to the repository? This is no request for a commit > bit (to much accountability), more a technical request. > Do I need to use cvsup from ports to get a copy of the cvs server > and checkout against my local copy? > 2) Is it ok to do it on a FreeBSD7-Stable, as long no change between > the RELENG7 branch and the HEAD prevents merge? Or is it mandatory > to test it with -CURRENT? > I ask, because -CURRENT maybe unstable by definition, and I don't > want to search for errors in my work come in by experimental code. > I have no problem, when a first patch exists, to test it on -CURRENT, > but it should be the 2nd step (for me). There is very little chance anything but a well targeted bugfix would get merged to a stable branch and there is zero chance that GPLv3 code will be merged to an existing, GPLv3-free stable branch. As such, any work on RELENG_7 is likely a waste of time. -- Brooks --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIakMsXY6L6fI4GtQRAoE+AKCeVS6wu25DVLzvc8K08cMcIvMQIQCfacha fwCzGty6HGuXBg0+M7De58o= =lS+F -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:08:16 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFE0F1065673 for ; Tue, 1 Jul 2008 15:08:16 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id 470238FC17 for ; Tue, 1 Jul 2008 15:08:16 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA01.westchester.pa.mail.comcast.net with comcast id kZzD1Z0050EZKEL510Qi00; Tue, 01 Jul 2008 15:08:15 +0000 Received: from mail.cokane.org ([24.60.133.163]) by OMTA01.westchester.pa.mail.comcast.net with comcast id kf7o1Z0083Xh0XL3Mf7obZ; Tue, 01 Jul 2008 15:07:48 +0000 X-Authority-Analysis: v=1.0 c=1 a=jELy_hNlLGfH4viERQUA:9 a=EbLU1ZIUrZwAhUu6b6UA:7 a=P9GNdIPLkeX_I971RRJkLgdOLo0A:4 a=LY0hPdMaydYA:10 a=NciV1ahng6x1BGp6A7MA:9 a=5eaxgcPhpIKg4WCIJNumIFnVllUA:4 a=rPt6xJ-oxjAA:10 Received: by mail.cokane.org (Postfix, from userid 103) id 12A681DB2F9; Tue, 1 Jul 2008 11:07:48 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id F2FA716B55B; Tue, 1 Jul 2008 11:07:33 -0400 (EDT) From: Coleman Kane To: Jens Rehsack In-Reply-To: <486A3C55.6030801@web.de> References: <4869E272.1060606@web.de> <1214914307.1802.33.camel@localhost> <486A3C55.6030801@web.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1BrZ7b4nS65Vt7Cadw7l" Organization: FreeBSD Project Date: Tue, 01 Jul 2008 11:05:41 -0400 Message-Id: <1214924741.1802.42.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Cc: FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 15:08:17 -0000 --=-1BrZ7b4nS65Vt7Cadw7l Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-07-01 at 14:16 +0000, Jens Rehsack wrote: > Coleman Kane wrote: > > On Tue, 2008-07-01 at 07:53 +0000, Jens Rehsack wrote: > >> Hi David, > >> > >> because you are the maintainer of src/contrib/binutils, I first want t= o ask=20 > >> you before I start to update src/contrib/binutils. I've read the READM= E's=20 > >> you've placed there, but 2 questions remain: > [..] > > This sounds intriguing.... what version of binutils are you updating to= ? >=20 > The most recent is 2.18, in src/ is 2.12 - so I would try to update to > the most recent. This is nothing which will finished tomorrow or in a > week - it will take some time. > To be true, the reason why I wanna do this, is using SSE3 instructions ;-= ) >=20 > /Jens >=20 Sounds nice. Are there any considerations needed to be made concerning GPLv3 licensing of newer binutils? I remember this came up before concerning importing future revisions of GCC 4.2.x into the tree (right now we've got one of the last GPL2 releases that were made). --=20 Coleman Kane --=-1BrZ7b4nS65Vt7Cadw7l Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkhqR8MACgkQcMSxQcXat5cjUACeLqG2WJwmAMWFGqTpg4UF1x7S Gi4AoISd1EVOSWQK2UXzaLaIwmUhZmFR =exgI -----END PGP SIGNATURE----- --=-1BrZ7b4nS65Vt7Cadw7l-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:29:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66749106567D for ; Tue, 1 Jul 2008 15:29:33 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3141D8FC25 for ; Tue, 1 Jul 2008 15:29:32 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.2/8.14.2) with ESMTP id m61FTWMX027295; Tue, 1 Jul 2008 08:29:32 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.2/Submit) id m61FTWNO027294; Tue, 1 Jul 2008 08:29:32 -0700 (PDT) (envelope-from obrien) Date: Tue, 1 Jul 2008 08:29:32 -0700 From: "David O'Brien" To: Jens Rehsack Message-ID: <20080701152932.GA27253@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Jens Rehsack , FreeBSD-Current-List References: <4869E272.1060606@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4869E272.1060606@web.de> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 15:29:33 -0000 On Tue, Jul 01, 2008 at 07:53:22AM +0000, Jens Rehsack wrote: > because you are the maintainer of src/contrib/binutils, I first want to > ask you before I start to update src/contrib/binutils. Hi Jens, As part of the MIPS effort, I will be updating Binutils to 2.17, the last GPLv2 release. Please wait for that effort. thanks, -- David -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:41:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 028091065683 for ; Tue, 1 Jul 2008 15:41:02 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2E6038FC22 for ; Tue, 1 Jul 2008 15:41:00 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id m61FLVNH004681; Tue, 1 Jul 2008 11:21:32 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Tue, 01 Jul 2008 11:21:32 -0400 (EDT) Date: Tue, 1 Jul 2008 11:21:31 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Gary Jennejohn In-Reply-To: <20080701104912.5e9e16e0@peedub.jennejohn.org> Message-ID: References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: src-committers@freebsd.org, current@freebsd.org, vova@fbsd.ru, cvs-src@freebsd.org, cvs-all@freebsd.org, David Xu Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 15:41:02 -0000 On Tue, 1 Jul 2008, Gary Jennejohn wrote: > On Mon, 30 Jun 2008 22:28:44 +0400 > Vladimir Grebenschikov wrote: > >> On Tue, 2008-06-24 at 07:32 +0000, David Xu wrote: >> >> This commit makes threaded application almost unusable on 8-CURRENT. >> >> Applications eat 100% CPU all the time and works _very_ slowly. >> (top shows several threads for every constantly applications eating CPU) >> >> Following applications are affected for me: firefox, evolution, eclipse >> (probably more). >> >> Reverting user-land part of commit fixes problem, reverting kernel >> changes nothing regarding the problem. >> >> I have: >> FreeBSD 8.0-CURRENT #0: Fri Jun 20 17:14:23 MSD 2008 >> root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.01-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 >> Features=0xbfebfbff >> Features2=0xe3bd >> AMD Features=0x20100000 >> AMD Features2=0x1 >> Cores per package: 2 >> > [snip commit message] > > Did you recompile these misbehaving applications? If that is necessary, then something is certainly borken. One shouldn't have to rebuild the applications. -- DE From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:56:31 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82EBA106566C for ; Tue, 1 Jul 2008 15:56:31 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 168878FC0A for ; Tue, 1 Jul 2008 15:56:30 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KDiDS-00015O-Ua for freebsd-current@freebsd.org; Tue, 01 Jul 2008 15:56:27 +0000 Received: from 213.202.123.89 ([213.202.123.89]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Jul 2008 15:56:26 +0000 Received: from ivoras by 213.202.123.89 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Jul 2008 15:56:26 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 01 Jul 2008 17:56:18 +0200 Lines: 52 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 213.202.123.89 User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) X-Enigmail-Version: 0.94.1.0 Sender: news Subject: 6-core CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 15:56:31 -0000 Hi, I have a chance, for a few hours, to test a machine build upon Xeon MP "Dunnington" CPUs, with 2 CPUs with 6 core each (2x6). Everything works fine except that only 4 cores are activated from each CPU: CPU: Genuine Intel(R) CPU @ 2.13GHz (2133.35-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106d0 Stepping = 0 Features=0xbfebfbff Features2=0xce33d> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 6 usable memory = 8576860160 (8179 MB) avail memory = 8281669632 (7898 MB) ACPI APIC Table: <111607 APIC1739> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 9 cpu6 (AP): APIC ID: 10 cpu7 (AP): APIC ID: 11 Note that it detects 6 cores per package (which is correct) but then proceeds to say 8 CPUs total are detected. Entire dmesg is here: http://people.freebsd.org/~ivoras/dmesg/mp6-dmesg.txt Output of mptable is also missing the CPUs: -- Processors: APIC ID Version State Family Model Step Flags 0 0x14 BSP, usable 6 13 0 0xbfebfbff 8 0x14 AP, usable 6 13 0 0xbfebfbff 1 0x14 AP, usable 6 13 0 0xbfebfbff 2 0x14 AP, usable 6 13 0 0xbfebfbff 3 0x14 AP, usable 6 13 0 0xbfebfbff 9 0x14 AP, usable 6 13 0 0xbfebfbff 10 0x14 AP, usable 6 13 0 0xbfebfbff 11 0x14 AP, usable 6 13 0 0xbfebfbff -- If any quick fixes are found within the next few hours, I can test them. This is 7-STABLE. From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:56:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DAF91065673 for ; Tue, 1 Jul 2008 15:56:45 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCAF8FC1F for ; Tue, 1 Jul 2008 15:56:44 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m61FuTtv034883; Tue, 1 Jul 2008 08:56:29 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <486A53AD.9090904@freebsd.org> Date: Tue, 01 Jul 2008 08:56:29 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> <1214900266.1947.13.camel@localhost> In-Reply-To: <1214900266.1947.13.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 15:56:45 -0000 Vladimir Grebenschikov wrote: > On Mon, 2008-06-30 at 22:46 -0700, Tim Kientzle wrote: > >>Vladimir Grebenschikov wrote: >> >>> >>>Files are not corrupted any more, but strange message for every >>>directory still shown. >> >>Yes. I think I just fixed this. Please let me know if >>you see any other problems. > > Now it works ok with directories, but I think, condition is too generic: > > + if (cpio->option_link > + && archive_entry_filetype(entry) != AE_IFDIR) > + { [ ... example showing breakage copying symlinks ... ] Try adding the following to the above condition: && archive_entry_filetype(entry) != AE_IFLNK From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 16:45:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8EAA1065679; Tue, 1 Jul 2008 16:45:36 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE638FC1F; Tue, 1 Jul 2008 16:45:35 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m61GjVPE021427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 20:45:33 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDiyw-000Mjb-VX; Tue, 01 Jul 2008 20:45:31 +0400 From: Vladimir Grebenschikov To: Tim Kientzle In-Reply-To: <486A53AD.9090904@freebsd.org> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> <1214900266.1947.13.camel@localhost> <486A53AD.9090904@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 01 Jul 2008 20:45:30 +0400 Message-Id: <1214930730.1898.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 16:45:36 -0000 On Tue, 2008-07-01 at 08:56 -0700, Tim Kientzle wrote: > Vladimir Grebenschikov wrote: > > On Mon, 2008-06-30 at 22:46 -0700, Tim Kientzle wrote: > > > >>Vladimir Grebenschikov wrote: > >> > >>> > >>>Files are not corrupted any more, but strange message for every > >>>directory still shown. > >> > >>Yes. I think I just fixed this. Please let me know if > >>you see any other problems. > > > > Now it works ok with directories, but I think, condition is too generic: > > > > + if (cpio->option_link > > + && archive_entry_filetype(entry) != AE_IFDIR) > > + { > > [ ... example showing breakage copying symlinks ... ] > > Try adding the following to the above condition: > > && archive_entry_filetype(entry) != AE_IFLNK I guess it will work. I just wander about other AE_IF* that may not pass link(2). -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 17:31:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 376F11065682 for ; Tue, 1 Jul 2008 17:31:48 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [194.62.233.102]) by mx1.freebsd.org (Postfix) with ESMTP id E1E1C8FC12 for ; Tue, 1 Jul 2008 17:31:47 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from sp34.ipt.ru ([194.62.233.107] helo=bs1.sp34.ru) by mail.ipt.ru with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1KDjhi-000NPR-T0; Tue, 01 Jul 2008 21:31:46 +0400 Received: from bsam by bs1.sp34.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDjiq-0000Ml-AC; Tue, 01 Jul 2008 21:32:56 +0400 To: Ivan Voras References: From: Boris Samorodov Date: Tue, 01 Jul 2008 21:32:56 +0400 In-Reply-To: (Ivan Voras's message of "Tue\, 01 Jul 2008 17\:56\:18 +0200") Message-ID: <52055287@bs1.sp34.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: 6-core CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 17:31:48 -0000 On Tue, 01 Jul 2008 17:56:18 +0200 Ivan Voras wrote: > If any quick fixes are found within the next few hours, I can test them. It's not an answer but may be booting with 8-CURRENT CD may show a difference. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 17:56:05 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5514E106564A; Tue, 1 Jul 2008 17:56:05 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id C7A328FC1F; Tue, 1 Jul 2008 17:56:04 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m61Hu0gZ003807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jul 2008 21:56:01 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDk5A-00013H-37; Tue, 01 Jul 2008 21:56:00 +0400 From: Vladimir Grebenschikov To: Coleman Kane In-Reply-To: <1214914239.1802.31.camel@localhost> References: <200806240737.m5O7bhc5018813@repoman.freebsd.org> <1214850524.42354.9.camel@localhost> <20080701104912.5e9e16e0@peedub.jennejohn.org> <1214908172.1947.29.camel@localhost> <20080701073434.523a72ea@kan.dnsalias.net> <1214914239.1802.31.camel@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 01 Jul 2008 21:55:59 +0400 Message-Id: <1214934959.1889.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: [fwd] cvs commit: src/lib/libthr/thread thr_mutex.c thr_umtx.c thr_umtx.h src/sys/kern kern_umtx.c src/sys/sys umtx.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 17:56:05 -0000 On Tue, 2008-07-01 at 08:10 -0400, Coleman Kane wrote: > Firefox depends upon a lot of external things, including glib, nss, > and > nspr (among others, probably) which would propagate thread-lib bugs > even > after the main app has been recompiled. I suggest running ldd > on /usr/local/lib/firefox/firefox-bin (and other shared objects in > that > dir) to find out what all you might need to rebuild. At the very > least, > I'd expect a rebuild of nspr and nss to be mandatory. I *think* > firefox > uses nspr's thread implementation, and not the one from gthread > (glib). Hm, effect affects both eclipse, evolution and firefox. truss shows nothing (no syscalls) while that problem on firefox (for several seconds) I had no ktrace in kernel so I have rebuild kernel with ktrace and reboot. Effect disappears, rebuilding kernel back without ktrace also does not helps to reproduce problem. Probably fix related to latest ports update, but not likely, following ports was updated after I have seen effect last time: x11/kdelibs3 x11-drivers/xorg-drivers mail/evolution-exchange multimedia/cheese graphics/poppler-gtk x11/gdm graphics/gimp-app x11/gnome-desktop devel/subversion accessibility/mousetweaks www/neon28 x11/gnome-session x11-fm/nautilus graphics/evince deskutils/deskbar-applet x11/gnome-applets games/gnome-games security/seahorse no more ideas how to reproduce problem :( -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 18:14:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8F0B106566C for ; Tue, 1 Jul 2008 18:14:04 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 562AC8FC17 for ; Tue, 1 Jul 2008 18:14:03 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 5CAC4198E48; Tue, 1 Jul 2008 20:14:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 5082C198E47; Tue, 1 Jul 2008 20:14:00 +0200 (CEST) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id 245C0198E45; Tue, 1 Jul 2008 20:13:59 +0200 (CEST) Received: from wep4017.physik.uni-wuerzburg.de ([132.187.37.17]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.1HF110) with ESMTP id 2008070120135820-94913 ; Tue, 1 Jul 2008 20:13:58 +0200 Received: by wep4017.physik.uni-wuerzburg.de (sSMTP sendmail emulation); Tue, 1 Jul 2008 20:13:58 +0200 From: "Alexey Shuvaev" Date: Tue, 1 Jul 2008 20:13:58 +0200 To: xcllnt@mac.com Message-ID: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> MIME-Version: 1.0 Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 08:13:58 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 08:14:00 PM, Serialize complete at 07/01/2008 08:14:00 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 18:14:04 -0000 Hello! I have got puc0@pci0:0:10:0: class=0x078000 card=0x00121000 chip=0x98359710 rev=0x01 hdr=0x00 vendor = 'MosChip Semiconductors (Was: Netmos Technology)' device = 'Nm9835 Parallel/Serial Port Adapter' class = simple comms In a nutshell I have the following proposals to review: - I have spent few hours figuring out why serial interfaces covered by puc(4) do not come up at boot time. The issue was I tried to use kernel module instead of compiling puc(4) into the kernel. Will it be good to have explicit note about it in the man page? - First time when I rebuilt the kernel I only added options COM_MULTIPORT, which is used inside sio(4). The puc(4) also states the serial ports are managed by sio(4). However it seems that serial ports are actually handled by uart(4). Is COM_MULTIPORT kernel option obsolete? - The puc(4) man page states parallel ports are not supported yet. It seems thay did now. More info about the system: [wep4020] ~> uname -a FreeBSD wep4020 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Mon Jun 30 19:24:21 CEST 2008 root@wep4020:/usr/obj/usr/src/sys/MULTIPORT i386 ---from dmesg--- puc0: port 0x7c00-0x7c07,0x8000-0x8007,0x8400-0x8407,0x8800-0x8807,0x8c00-0x8c07,0x9000-0x900f irq 7 at device 10.0 on pci0 puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart1: on puc0 uart1: [FILTER] ppc0: on puc0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/12 bytes threshold ppbus0: on ppc0 plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 I have roughly tested the functionality of this parallel port throug the ppi interface. It seems to work. Attached is a draft of a patch to share/man/man4/puc.4 but maybe more work is required (regarding COM_MULTIPORT and sio(4) man page...). Alexey. From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 18:18:37 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC1721065671 for ; Tue, 1 Jul 2008 18:18:37 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 750A78FC1C for ; Tue, 1 Jul 2008 18:18:37 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id CF2A9198E49; Tue, 1 Jul 2008 20:18:36 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id C2DC5198E48; Tue, 1 Jul 2008 20:18:36 +0200 (CEST) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id 96586198E47; Tue, 1 Jul 2008 20:18:35 +0200 (CEST) Received: from wep4017.physik.uni-wuerzburg.de ([132.187.37.17]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.1HF110) with ESMTP id 2008070120183533-94931 ; Tue, 1 Jul 2008 20:18:35 +0200 Received: by wep4017.physik.uni-wuerzburg.de (sSMTP sendmail emulation); Tue, 1 Jul 2008 20:18:35 +0200 From: "Alexey Shuvaev" Date: Tue, 1 Jul 2008 20:18:35 +0200 To: xcllnt@mac.com Message-ID: <20080701181835.GB93601@wep4017.physik.uni-wuerzburg.de> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> MIME-Version: 1.0 In-Reply-To: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 08:18:35 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 08:18:36 PM, Serialize complete at 07/01/2008 08:18:36 PM Content-Type: multipart/mixed; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 18:18:38 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 01, 2008 at 08:13:58PM +0200, Alexey Shuvaev wrote: > [snip] > > Attached is a draft of a patch to share/man/man4/puc.4 but maybe more > work is required (regarding COM_MULTIPORT and sio(4) man page...). > Forgotten patch: --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch --- /usr/src/share/man/man4/puc.4 2008-01-24 13:09:59.000000000 +0100 +++ man4/puc.4 2008-07-01 20:11:57.000000000 +0200 @@ -35,11 +35,11 @@ .Sh SYNOPSIS .Cd "device pci" .Cd "device puc" -.Cd "device sio" +.Cd "device uart" .Cd "device ppc" .Sh DESCRIPTION This driver acts as a shim to connect PCI serial and parallel ports to the -.Xr sio 4 +.Xr uart 4 and .Xr ppc 4 driver. @@ -47,9 +47,12 @@ The list of supported devices is in .Pa sys/dev/puc/pucdata.c . Support for new cards should be added there. +.Pp +Note that this driver should be compiled into the kernel +in order to work properly. .Sh SEE ALSO .Xr ppc 4 , -.Xr sio 4 +.Xr uart 4 .Sh HISTORY This driver took the idea from the .Nx @@ -57,6 +60,8 @@ driver and still uses the same structure to describe cards, to ease exchanging card info. .Sh BUGS -Only serial ports are supported through the -.Xr sio 4 -driver at the moment. +The serial ports are supported through the +.Xr uart 4 +driver. The support of parallel ports through the +.Xr ppc 4 +driver is not widely tested at the moment. --M9NhX3UHpAaciwkO-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 20:02:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CC161065686 for ; Tue, 1 Jul 2008 20:02:34 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.64]) by mx1.freebsd.org (Postfix) with ESMTP id 723BF8FC19 for ; Tue, 1 Jul 2008 20:02:34 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp018-bge351000.mac.com (asmtp018-bge351000 [10.150.69.81]) by smtpoutm.mac.com (Xserve/smtpout001/MantshX 4.0) with ESMTP id m61K2YBT007326 for ; Tue, 1 Jul 2008 13:02:34 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp018.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3C00NOQFO83R40@asmtp018.mac.com> for freebsd-current@freebsd.org; Tue, 01 Jul 2008 13:02:34 -0700 (PDT) Message-id: From: Marcel Moolenaar To: Alexey Shuvaev In-reply-to: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> Date: Tue, 01 Jul 2008 13:02:32 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> X-Mailer: Apple Mail (2.926) Cc: freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 20:02:34 -0000 On Jul 1, 2008, at 11:13 AM, Alexey Shuvaev wrote: > Hello! > > I have got > puc0@pci0:0:10:0: class=0x078000 card=0x00121000 > chip=0x98359710 rev=0x01 hdr=0x00 > vendor = 'MosChip Semiconductors (Was: Netmos Technology)' > device = 'Nm9835 Parallel/Serial Port Adapter' > class = simple comms > > In a nutshell I have the following proposals to review: > > - I have spent few hours figuring out why serial interfaces > covered by puc(4) do not come up at boot time. The issue was I tried > to use kernel module instead of compiling puc(4) into the kernel. > Will it be good to have explicit note about it in the man page? Well, no. There's a very simple rule: If driver C is a child of a driver P and driver P is loaded as a module, then driver C must be loaded as a module as well. In this case uart(4) and ppc(4) are children of puc(4) and both are compiled into the kernel by default. So, you must either compile puc(4) into the kernel or build uart(4) and puc(4) as modules as well. In other words: there's no problem with puc(4) being loaded as a module. It's a generic problem with our modules vs. compiled-in case. > - First time when I rebuilt the kernel I only added > options COM_MULTIPORT, which is used inside sio(4). The puc(4) also > states > the serial ports are managed by sio(4). However it seems that serial > ports are actually handled by uart(4). Is COM_MULTIPORT kernel option > obsolete? COM_MULTIPORT is specific to sio(4), so yes it's obsolete. puc(4) favors uart(4) over sio(4), because both puc(4) and uart(4) implement the serdev I/F, which gives puc(4) better control over which port gets to service what interrupt condition in what relative order. In other words, it allows puc(4) to handle all receive interrupts of all ports before it handles any transmit interrupts. With sio(4) there's no benefit. > - The puc(4) man page states parallel ports are not supported yet. > It seems thay did now. Parallel ports are supported, yes. > Attached is a draft of a patch to share/man/man4/puc.4 but maybe more > work is required (regarding COM_MULTIPORT and sio(4) man page...). I would not mention COM_MULTIPORT in the puc(4) manpage at all. Neither sio(4)... FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 21:30:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8F47106566C for ; Tue, 1 Jul 2008 21:30:11 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E73C8FC22 for ; Tue, 1 Jul 2008 21:30:10 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 9A484A06F2; Tue, 1 Jul 2008 23:30:07 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 8D4E2A06F1; Tue, 1 Jul 2008 23:30:07 +0200 (CEST) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id 5A616A06E8; Tue, 1 Jul 2008 23:30:06 +0200 (CEST) Received: from wep4017.physik.uni-wuerzburg.de ([132.187.37.17]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.1HF110) with ESMTP id 2008070123300575-95452 ; Tue, 1 Jul 2008 23:30:05 +0200 Received: by wep4017.physik.uni-wuerzburg.de (sSMTP sendmail emulation); Tue, 1 Jul 2008 23:30:05 +0200 From: "Alexey Shuvaev" Date: Tue, 1 Jul 2008 23:30:05 +0200 To: Marcel Moolenaar Message-ID: <20080701213005.GA94030@wep4017.physik.uni-wuerzburg.de> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> MIME-Version: 1.0 In-Reply-To: Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 11:30:05 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 11:30:07 PM, Serialize complete at 07/01/2008 11:30:07 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 21:30:11 -0000 On Tue, Jul 01, 2008 at 01:02:32PM -0700, Marcel Moolenaar wrote: > > On Jul 1, 2008, at 11:13 AM, Alexey Shuvaev wrote: > >> - I have spent few hours figuring out why serial interfaces >> covered by puc(4) do not come up at boot time. The issue was I tried >> to use kernel module instead of compiling puc(4) into the kernel. >> Will it be good to have explicit note about it in the man page? > > Well, no. There's a very simple rule: > > If driver C is a child of a driver P and driver P is > loaded as a module, then driver C must be loaded as > a module as well. > > In this case uart(4) and ppc(4) are children of puc(4) > and both are compiled into the kernel by default. So, > you must either compile puc(4) into the kernel or > build uart(4) and puc(4) as modules as well. > > In other words: there's no problem with puc(4) being > loaded as a module. It's a generic problem with our > modules vs. compiled-in case. > Ok, clear now. The GENERIC kernel contains both sio(4) and uart(4) but not the puc(4). In this sense it is "wrong" (which is the cost for removing rarely used puc(4) out of the GENERIC kernel). >> - First time when I rebuilt the kernel I only added >> options COM_MULTIPORT, which is used inside sio(4). The puc(4) also >> states >> the serial ports are managed by sio(4). However it seems that serial >> ports are actually handled by uart(4). Is COM_MULTIPORT kernel option >> obsolete? > > COM_MULTIPORT is specific to sio(4), so yes it's obsolete. > > puc(4) favors uart(4) over sio(4), because both puc(4) and > uart(4) implement the serdev I/F, which gives puc(4) better > control over which port gets to service what interrupt > condition in what relative order. In other words, it allows > puc(4) to handle all receive interrupts of all ports before > it handles any transmit interrupts. > > With sio(4) there's no benefit. > So, one can still use puc(4) + sio(4) (by removing, for example, uart(4) from the kernel)? Then COM_MULTIPORT is not 100% obsolete yet. >> Attached is a draft of a patch to share/man/man4/puc.4 but maybe more >> work is required (regarding COM_MULTIPORT and sio(4) man page...). > > I would not mention COM_MULTIPORT in the puc(4) manpage > at all. Neither sio(4)... > I thougt about removing COM_MULTIPORT from the sio(4) both man page and source code. If one can still use it, let it be so. >> - The puc(4) man page states parallel ports are not supported yet. >> It seems thay did now. > > Parallel ports are supported, yes. > That's good! Attached is updated patch to puc man page. Don't know if it is really worthwhile. Thanks, Alexey. From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 21:39:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EC07106567B for ; Tue, 1 Jul 2008 21:39:00 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id E4EBB8FC14 for ; Tue, 1 Jul 2008 21:38:59 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 439BA198E57; Tue, 1 Jul 2008 23:38:59 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 3729D198E54; Tue, 1 Jul 2008 23:38:59 +0200 (CEST) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id A5132198E51; Tue, 1 Jul 2008 23:38:55 +0200 (CEST) Received: from wep4017.physik.uni-wuerzburg.de ([132.187.37.17]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.1HF110) with ESMTP id 2008070123385514-95468 ; Tue, 1 Jul 2008 23:38:55 +0200 Received: by wep4017.physik.uni-wuerzburg.de (sSMTP sendmail emulation); Tue, 1 Jul 2008 23:38:55 +0200 From: "Alexey Shuvaev" Date: Tue, 1 Jul 2008 23:38:55 +0200 To: Marcel Moolenaar Message-ID: <20080701213855.GB94030@wep4017.physik.uni-wuerzburg.de> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080701213005.GA94030@wep4017.physik.uni-wuerzburg.de> MIME-Version: 1.0 In-Reply-To: <20080701213005.GA94030@wep4017.physik.uni-wuerzburg.de> Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 11:38:55 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.1HF110 | April 11, 2008) at 07/01/2008 11:38:59 PM, Serialize complete at 07/01/2008 11:38:59 PM Content-Type: multipart/mixed; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 21:39:00 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 01, 2008 at 11:30:05PM +0200, Alexey Shuvaev wrote: > > Attached is updated patch to puc man page. > Don't know if it is really worthwhile. > It seems I should go sleep now :) --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch --- /usr/src/share/man/man4/puc.4 2008-01-24 13:09:59.000000000 +0100 +++ man4/puc.4 2008-07-01 23:23:42.000000000 +0200 @@ -35,28 +35,32 @@ .Sh SYNOPSIS .Cd "device pci" .Cd "device puc" -.Cd "device sio" +.Cd "device uart" .Cd "device ppc" .Sh DESCRIPTION This driver acts as a shim to connect PCI serial and parallel ports to the -.Xr sio 4 +.Xr uart 4 and .Xr ppc 4 -driver. +drivers. .Pp The list of supported devices is in .Pa sys/dev/puc/pucdata.c . Support for new cards should be added there. +.Pp +As +.Xr uart 4 +and +.Xr ppc 4 +are children of +.Xr puc 4 +they all should be either compiled into the kernel or loaded as a modules. .Sh SEE ALSO .Xr ppc 4 , -.Xr sio 4 +.Xr uart 4 , .Sh HISTORY This driver took the idea from the .Nx .Xr puc 4 driver and still uses the same structure to describe cards, to ease exchanging card info. -.Sh BUGS -Only serial ports are supported through the -.Xr sio 4 -driver at the moment. --x+6KMIRAuhnl3hBn-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 22:49:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A5461065674 for ; Tue, 1 Jul 2008 22:49:34 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.80]) by mx1.freebsd.org (Postfix) with ESMTP id EFA1B8FC2A for ; Tue, 1 Jul 2008 22:49:33 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp012-bge351000.mac.com (asmtp012-bge351000 [10.150.69.75]) by smtpoutm.mac.com (Xserve/smtpout017/MantshX 4.0) with ESMTP id m61MnXGw013462 for ; Tue, 1 Jul 2008 15:49:33 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp012.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3C00IH0NEK7300@asmtp012.mac.com> for freebsd-current@freebsd.org; Tue, 01 Jul 2008 15:49:33 -0700 (PDT) Message-id: From: Marcel Moolenaar To: Alexey Shuvaev In-reply-to: <20080701213005.GA94030@wep4017.physik.uni-wuerzburg.de> Date: Tue, 01 Jul 2008 15:49:32 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080701213005.GA94030@wep4017.physik.uni-wuerzburg.de> X-Mailer: Apple Mail (2.926) Cc: freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 22:49:34 -0000 On Jul 1, 2008, at 2:30 PM, Alexey Shuvaev wrote: > So, one can still use puc(4) + sio(4) (by removing, for example, > uart(4) from the kernel)? Yes. > Then COM_MULTIPORT is not 100% obsolete yet. Really? :-) >>> Attached is a draft of a patch to share/man/man4/puc.4 but maybe >>> more >>> work is required (regarding COM_MULTIPORT and sio(4) man page...). >> >> I would not mention COM_MULTIPORT in the puc(4) manpage >> at all. Neither sio(4)... >> > I thougt about removing COM_MULTIPORT from the sio(4) both man page > and source code. If one can still use it, let it be so. COM_MULTIPORT is just confusing. There are PCI cards that puc(4) supports and to which puc(4) sio(4) can attach and that don't report interrupts in a way compatible with COM_MULTIPORT. In those cases puc(4)+sio(4) is broken, but puc(4)+uart(4) works. Really, we should just drop sio(4), focus on a single serial driver that just works and works everywhere. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 02:43:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D9A11065681; Wed, 2 Jul 2008 02:43:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D0D648FC14; Wed, 2 Jul 2008 02:43:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m622gtjQ035969; Tue, 1 Jul 2008 22:42:56 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 1 Jul 2008 22:24:21 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807012224.21358.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Tue, 01 Jul 2008 22:42:57 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7612/Tue Jul 1 19:13:47 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS, UPPERCASE_25_50 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Ivan Voras Subject: Re: 6-core CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 02:43:04 -0000 On Tuesday 01 July 2008 11:56:18 am Ivan Voras wrote: > Hi, > > I have a chance, for a few hours, to test a machine build upon Xeon MP > "Dunnington" CPUs, with 2 CPUs with 6 core each (2x6). Everything works > fine except that only 4 cores are activated from each CPU: > > CPU: Genuine Intel(R) CPU @ 2.13GHz (2133.35-MHz > K8-class CPU) > Origin = "GenuineIntel" Id = 0x106d0 Stepping = 0 > > Features=0xbfebfbff > > Features2=0xce33d> > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 6 > usable memory = 8576860160 (8179 MB) > avail memory = 8281669632 (7898 MB) > ACPI APIC Table: <111607 APIC1739> > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 8 > cpu5 (AP): APIC ID: 9 > cpu6 (AP): APIC ID: 10 > cpu7 (AP): APIC ID: 11 > > Note that it detects 6 cores per package (which is correct) but then > proceeds to say 8 CPUs total are detected. > > Entire dmesg is here: > http://people.freebsd.org/~ivoras/dmesg/mp6-dmesg.txt > > Output of mptable is also missing the CPUs: > -- > Processors: APIC ID Version State Family Model Step Flags > 0 0x14 BSP, usable 6 13 0 0xbfebfbff > 8 0x14 AP, usable 6 13 0 0xbfebfbff > 1 0x14 AP, usable 6 13 0 0xbfebfbff > 2 0x14 AP, usable 6 13 0 0xbfebfbff > 3 0x14 AP, usable 6 13 0 0xbfebfbff > 9 0x14 AP, usable 6 13 0 0xbfebfbff > 10 0x14 AP, usable 6 13 0 0xbfebfbff > 11 0x14 AP, usable 6 13 0 0xbfebfbff > -- Presumably 'acpidump -t' also only shows 8 CPUs? In that case, the BIOS needs to be fixed to recognize all 12 cores before FreeBSD will see them. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 03:26:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 291AD106567C for ; Wed, 2 Jul 2008 03:26:39 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 0449D8FC1D for ; Wed, 2 Jul 2008 03:26:38 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m623QPtv038647; Tue, 1 Jul 2008 20:26:28 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <486AF561.70201@freebsd.org> Date: Tue, 01 Jul 2008 20:26:25 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> <1214900266.1947.13.camel@localhost> <486A53AD.9090904@freebsd.org> <1214930730.1898.3.camel@localhost> In-Reply-To: <1214930730.1898.3.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 03:26:39 -0000 Vladimir Grebenschikov wrote: > On Tue, 2008-07-01 at 08:56 -0700, Tim Kientzle wrote: > >>Try adding the following to the above condition: >> >> && archive_entry_filetype(entry) != AE_IFLNK > > I guess it will work. I just wander about other AE_IF* that may not pass > link(2). Perhaps cpio -dumpl should only try to hardlink regular files? That would be an easy change. Tim From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 06:52:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DBC11065671; Wed, 2 Jul 2008 06:52:05 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id A4F4D8FC1A; Wed, 2 Jul 2008 06:52:01 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.24.21.170]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m626pwWP021003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 10:52:00 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KDwC6-0008y3-5d; Wed, 02 Jul 2008 10:51:58 +0400 From: Vladimir Grebenschikov To: Tim Kientzle In-Reply-To: <486AF561.70201@freebsd.org> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> <1214900266.1947.13.camel@localhost> <486A53AD.9090904@freebsd.org> <1214930730.1898.3.camel@localhost> <486AF561.70201@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Wed, 02 Jul 2008 10:51:57 +0400 Message-Id: <1214981517.2513.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 06:52:05 -0000 On Tue, 2008-07-01 at 20:26 -0700, Tim Kientzle wrote: > Vladimir Grebenschikov wrote: > > On Tue, 2008-07-01 at 08:56 -0700, Tim Kientzle wrote: > > > >>Try adding the following to the above condition: > >> > >> && archive_entry_filetype(entry) != AE_IFLNK > > > > I guess it will work. I just wander about other AE_IF* that may not pass > > link(2). > > Perhaps cpio -dumpl should only try to hardlink regular files? I think, one need to check original cpio behaviour and do exactly as was done here. Probably some software expect, for example, same inode number after cpio -dump on, say, copied devices or like. IMHO, It is more compatibility issue. > That would be an easy change. > > Tim -- Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 07:46:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B67B9106564A for ; Wed, 2 Jul 2008 07:46:00 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB6B8FC1B for ; Wed, 2 Jul 2008 07:46:00 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so360518rvf.43 for ; Wed, 02 Jul 2008 00:46:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=dUOWAaED1phh/dIQl8tzgxPgPhvXV7PxW/9xJ5BtXg0=; b=HOOrmLYwHyyZIYYdp5MxVxwRdbzYU6WQJH6WlzhkI0ZV3zu0Vham2+kEvac2Hd46B3 4cVJd6cu4FPhfXsxX+HKHWzBMi2oxGZ0eFfAKlU7C69RZz0zL6hH/Sz85Zy7RpApZpgf Vq1pXQI0srdHtLNfXV4gO5ST5izYsSSwAQJjY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=Ua1Mo3/7NvZm+u/lM2dS+zAZT0LjZB1NytSFvwcHTy1I3LIh9A6iWHT9tfduI9vXop 7gV8BPXX4wxyLR5lqz6k1JaHcvXteSYN3/0oVp1VSLKFn0IhfVjsgAXF5fKZoC2jyNSJ l0SBWZ4zyakec8AMbLmg3tS5GbNdbviLfXhPM= Received: by 10.140.147.5 with SMTP id u5mr4194136rvd.274.1214984760074; Wed, 02 Jul 2008 00:46:00 -0700 (PDT) Received: by 10.141.186.2 with HTTP; Wed, 2 Jul 2008 00:46:00 -0700 (PDT) Message-ID: <11167f520807020046n3a4008a4m2bfc0a72e69b6d91@mail.gmail.com> Date: Wed, 2 Jul 2008 02:46:00 -0500 From: "Sam Fourman Jr." To: "Jeremie Le Hen" In-Reply-To: <20080618202212.GF46885@obiwan.tataz.chchile.org> MIME-Version: 1.0 References: <484CC690.9020303@elischer.org> <48536C9A.8020801@elischer.org> <20080618151911.GB46885@obiwan.tataz.chchile.org> <485935FF.8040308@elischer.org> <20080618192903.O83875@maildrop.int.zabbadoz.net> <20080618202212.GF46885@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Bjoern A. Zeeb" , FreeBSD Current , freebsd-virtualization@freebsd.org Subject: Re: Vimage headsup.. revised. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 07:46:00 -0000 Does anyone Know if vimage works with pf? Sam Fourman Jr. From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 03:26:58 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76EB1106564A for ; Wed, 2 Jul 2008 03:26:58 +0000 (UTC) (envelope-from bri@brianwhalen.net) Received: from entwistle.sonicboom.org (entwistle.sonicboom.org [66.93.34.170]) by mx1.freebsd.org (Postfix) with ESMTP id 358AA8FC2C for ; Wed, 2 Jul 2008 03:26:57 +0000 (UTC) (envelope-from bri@brianwhalen.net) Received: from [127.0.0.1] (localhost.sonicboom.org [127.0.0.1]) by entwistle.sonicboom.org (8.14.2/8.14.2) with ESMTP id m622mKOS002719 for ; Tue, 1 Jul 2008 19:48:20 -0700 (PDT) (envelope-from bri@brianwhalen.net) Message-ID: <486AEC75.4000504@brianwhalen.net> Date: Tue, 01 Jul 2008 19:48:21 -0700 From: Brian User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 02 Jul 2008 12:43:35 +0000 Cc: Subject: Re: 6-core CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 03:26:58 -0000 Ivan Voras wrote: > Hi, > > I have a chance, for a few hours, to test a machine build upon Xeon MP > "Dunnington" CPUs, with 2 CPUs with 6 core each (2x6). Everything works > fine except that only 4 cores are activated from each CPU: > > CPU: Genuine Intel(R) CPU @ 2.13GHz (2133.35-MHz > K8-class CPU) > Origin = "GenuineIntel" Id = 0x106d0 Stepping = 0 > > > I wasnt aware that chip was even out yet.. Brian From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 13:11:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 029891065678 for ; Wed, 2 Jul 2008 13:11:00 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id ADAAF8FC0A for ; Wed, 2 Jul 2008 13:10:59 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KE26n-0002Cz-TW for freebsd-current@freebsd.org; Wed, 02 Jul 2008 13:10:53 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 02 Jul 2008 13:10:53 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 02 Jul 2008 13:10:53 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 02 Jul 2008 15:10:46 +0200 Lines: 40 Message-ID: References: <486AEC75.4000504@brianwhalen.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig12CFE9B49A8CBB8E77047C4E" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: <486AEC75.4000504@brianwhalen.net> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: 6-core CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 13:11:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig12CFE9B49A8CBB8E77047C4E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Brian wrote: > Ivan Voras wrote: >> Hi, >> >> I have a chance, for a few hours, to test a machine build upon Xeon MP= >> "Dunnington" CPUs, with 2 CPUs with 6 core each (2x6). Everything work= s >> fine except that only 4 cores are activated from each CPU: >> >> CPU: Genuine Intel(R) CPU @ 2.13GHz (2133.35-MHz >> K8-class CPU) >> Origin =3D "GenuineIntel" Id =3D 0x106d0 Stepping =3D 0 >> >> >> =20 > I wasnt aware that chip was even out yet.. It's not - this is a testing sample. --------------enig12CFE9B49A8CBB8E77047C4E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIa35WldnAQVacBcgRAitPAKCOG4ZH/7907MQrJgKhbZ4fmI+rswCgmySn dAoiairGZvdv3w0i/rvUbvs= =apq/ -----END PGP SIGNATURE----- --------------enig12CFE9B49A8CBB8E77047C4E-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 14:31:13 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D4021065687; Wed, 2 Jul 2008 14:31:13 +0000 (UTC) (envelope-from rehsack@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id EFEAC8FC17; Wed, 2 Jul 2008 14:31:12 +0000 (UTC) (envelope-from rehsack@web.de) Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate01.web.de (Postfix) with ESMTP id 5F9DCE608546; Wed, 2 Jul 2008 16:31:11 +0200 (CEST) Received: from [87.149.238.85] (helo=waldorf.muppets.liwing.de) by smtp07.web.de with esmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KE3MU-0004Yc-00; Wed, 02 Jul 2008 16:31:10 +0200 Message-ID: <486B912D.3000307@web.de> Date: Wed, 02 Jul 2008 14:31:09 +0000 From: Jens Rehsack User-Agent: Thunderbird 2.0.0.14 (X11/20080608) MIME-Version: 1.0 To: obrien@freebsd.org, Jens Rehsack , FreeBSD-Current-List References: <4869E272.1060606@web.de> <20080701152932.GA27253@dragon.NUXI.org> In-Reply-To: <20080701152932.GA27253@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: rehsack@web.de X-Sender: rehsack@web.de X-Provags-ID: V01U2FsdGVkX19Yrzf0zOo8PdmVs6lYEmYWro+zLHw8jBmoP0wi atYIjxtJD34TiXD9Ug4hyJttL8JZbTz4dk7XOz/2T5mF+eqOUm 3Xiis5/60= X-Mailman-Approved-At: Wed, 02 Jul 2008 14:47:13 +0000 Cc: Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 14:31:13 -0000 David O'Brien wrote: > On Tue, Jul 01, 2008 at 07:53:22AM +0000, Jens Rehsack wrote: >> because you are the maintainer of src/contrib/binutils, I first want to >> ask you before I start to update src/contrib/binutils. > > Hi Jens, > As part of the MIPS effort, I will be updating Binutils to 2.17, the last > GPLv2 release. Please wait for that effort. Sounds great, things get done without investing work *gg* So I will concentrate my time on some other thinggies - thanks David. /Jens From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 15:50:06 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98036106566C for ; Wed, 2 Jul 2008 15:50:06 +0000 (UTC) (envelope-from jbucht@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 6B23D8FC3A for ; Wed, 2 Jul 2008 15:50:06 +0000 (UTC) (envelope-from jbucht@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so563031rvf.43 for ; Wed, 02 Jul 2008 08:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=/rkjkZ+AAppScdWODLyoX4N5tshonjDQXravpqb6U2o=; b=kcpcdU/xai9LMtRqBSu0wIsuYDXWa4ZMPPBX6KxA0VQ5CRBl1pXpkVzHpZiq696QrD WjKIz9j6HOM2P/LXa5TlvIfgGhv1t4h/nxfcIvyCIvCcUGACr7WlCt/5Th71aLEZoORF xFmN0j25b2bqbwdxAwAIZn7HEkk4+81R1SgZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=C1NiOJe6deq7JmnrY5qsa+XY6nOyrEBJ5SKhz1fYntdhQTgyCTbKpAPgrDHwzLuye1 pWwXtGxvRC4ALxJGX5Oq0rMyODi6pxQmerT87up1c9zdtA9aD49jfzkFzuKqXRPxUr20 djn7itweXwLTWfXTdNM/PBU52duneH4D6eUEE= Received: by 10.141.176.6 with SMTP id d6mr1282729rvp.214.1215012083034; Wed, 02 Jul 2008 08:21:23 -0700 (PDT) Received: by 10.141.89.16 with HTTP; Wed, 2 Jul 2008 08:21:23 -0700 (PDT) Message-ID: <947010c30807020821s5f62f61bh2c2221d27282b5c0@mail.gmail.com> Date: Wed, 2 Jul 2008 17:21:23 +0200 From: "Johan Bucht" To: obrien@freebsd.org, "Jens Rehsack" , FreeBSD-Current-List In-Reply-To: <20080701152932.GA27253@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4869E272.1060606@web.de> <20080701152932.GA27253@dragon.NUXI.org> Cc: Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 15:50:06 -0000 On Tue, Jul 1, 2008 at 5:29 PM, David O'Brien wrote: > On Tue, Jul 01, 2008 at 07:53:22AM +0000, Jens Rehsack wrote: >> because you are the maintainer of src/contrib/binutils, I first want to >> ask you before I start to update src/contrib/binutils. > > Hi Jens, > As part of the MIPS effort, I will be updating Binutils to 2.17, the last > GPLv2 release. Please wait for that effort. > How tightly coupled are binutils and gcc? Is it be possible to replace some/all of the binutil binaries with bsd licensed counter-parts (like the ElfToolChain) without breaking something? /Johan From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 16:27:25 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 631CF1065678; Wed, 2 Jul 2008 16:27:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (unknown [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 073CF8FC0A; Wed, 2 Jul 2008 16:27:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 269E128448; Thu, 3 Jul 2008 00:27:22 +0800 (CST) Received: from localhost (tarsier.geekcn.org [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id C885AF07432; Thu, 3 Jul 2008 00:27:21 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id W+ZxmDpQ-kJ9; Thu, 3 Jul 2008 00:27:17 +0800 (CST) Received: from charlie.delphij.net (c-69-181-135-56.hsd1.ca.comcast.net [69.181.135.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 43679F070CE; Thu, 3 Jul 2008 00:27:14 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=aTP3/0O0h/MS1WCpVHDKaUs4Icf268oThPS/oFDDEvyHm+N2jXfPq2mPdDjVFN+Ci cv8B60CZdmw88BzE9uT6A== Message-ID: <486BAC60.6060001@delphij.net> Date: Wed, 02 Jul 2008 09:27:12 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Johan Bucht References: <4869E272.1060606@web.de> <20080701152932.GA27253@dragon.NUXI.org> <947010c30807020821s5f62f61bh2c2221d27282b5c0@mail.gmail.com> In-Reply-To: <947010c30807020821s5f62f61bh2c2221d27282b5c0@mail.gmail.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jens Rehsack , FreeBSD-Current-List Subject: Re: Updating src/contrib/binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 16:27:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Johan Bucht wrote: | On Tue, Jul 1, 2008 at 5:29 PM, David O'Brien wrote: |> On Tue, Jul 01, 2008 at 07:53:22AM +0000, Jens Rehsack wrote: |>> because you are the maintainer of src/contrib/binutils, I first want to |>> ask you before I start to update src/contrib/binutils. |> Hi Jens, |> As part of the MIPS effort, I will be updating Binutils to 2.17, the last |> GPLv2 release. Please wait for that effort. |> | | How tightly coupled are binutils and gcc? Is it be possible to replace | some/all of the binutil binaries with bsd licensed counter-parts (like | the ElfToolChain) without breaking something? I think we are lacking an usable as(1) implementation that supported both SSE3, mips, etc. which is critical for binutils to be useful with gcc. Additionally gdb come into mind which we do not yet have a BSD version. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhrrF8ACgkQi+vbBBjt66DHbwCdHIJu/dvVGlNgd4YioJWPcDC5 g7MAoIYKsbSMxuWFlLFNVqeUvEggxdTm =YrTJ -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 16:28:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDC011065671 for ; Wed, 2 Jul 2008 16:28:00 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outa.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id B1AE68FC27 for ; Wed, 2 Jul 2008 16:28:00 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 59E1023EE; Wed, 2 Jul 2008 09:28:00 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 9E4762D6004; Wed, 2 Jul 2008 09:27:59 -0700 (PDT) Message-ID: <486BACA4.7020809@elischer.org> Date: Wed, 02 Jul 2008 09:28:20 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <484CC690.9020303@elischer.org> <48536C9A.8020801@elischer.org> <20080618151911.GB46885@obiwan.tataz.chchile.org> <485935FF.8040308@elischer.org> <20080618192903.O83875@maildrop.int.zabbadoz.net> <20080618202212.GF46885@obiwan.tataz.chchile.org> <11167f520807020046n3a4008a4m2bfc0a72e69b6d91@mail.gmail.com> In-Reply-To: <11167f520807020046n3a4008a4m2bfc0a72e69b6d91@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , Jeremie Le Hen , FreeBSD Current , freebsd-virtualization@freebsd.org Subject: Re: Vimage headsup.. revised. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 16:28:00 -0000 Sam Fourman Jr. wrote: > Does anyone Know if vimage works with pf? > > Sam Fourman Jr. > _______________________________________________ > 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" It did, then pf got updated. we have not redone the port of the new pf. From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 19:09:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CE33106566C; Wed, 2 Jul 2008 19:09:03 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 62E4A8FC1B; Wed, 2 Jul 2008 19:09:02 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 6895E1CD13; Wed, 2 Jul 2008 21:09:01 +0200 (CEST) Date: Wed, 2 Jul 2008 21:09:01 +0200 From: Ed Schouten To: FreeBSD Current , FreeBSD Arch Message-ID: <20080702190901.GS14567@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bk6L21jbBNK7V1Rv" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Philip Paeps Subject: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 19:09:03 -0000 --Bk6L21jbBNK7V1Rv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, About 2 weeks ago I sent a message to these lists about the new MPSAFE TTY layer I've been working on. In my opinion, it is quite robust and after some minor polishing it should be a great candidate for inclusion in FreeBSD -CURRENT (never to be MFC'd). The last 2 weeks I've ported all the console drivers and fixed some bugs after I received some feedback from testers. Below is a list of pros and cons of the new TTY layer: + The new TTY layer allows drivers to operate without the Giant lock. Drivers like uart(4), the console drivers and the pseudo-terminal driver already support fine grained locking. + The new pseudo-terminal driver is capable of garbage collecting unused PTY's. Because PTY's are never recycled, they are a lot more robust (they are always initialized the same, no need to revoke() them before usage, etc). + The new TTY layer includes a new buffer scheme called the ttyinq and ttyoutq. Unlike clists, they provide unbuffered copying of data back to userspace, making read() calls in raw mode more efficient. + The programming interface for kernel drivers is a lot more simple. There is no need to have any knowledge about the internal state of the TTY layer. - Not all drivers have been ported to the new TTY layer yet. These drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), umodem(4), dcons(4). Even though drivers are very important to have, I am convinced we can get these working not long after the code as been integrated. I have considered adding two TTY layers to the FreeBSD kernel, but looking at the drivers, I'm not sure this is worth it, it turns certain parts of the kernel into rubbish. If you really care about one of these drivers, please port it to the new TTY layer as soon as possible! Below is the schedule I'm proposing for the integration of the MPSAFE TTY layer into our kernel. I would really appreciate it if I could get this code in before the end of the summer break, because I've got heaps of spare time to fix any problems then. July 2 2008 (today): Send a schedule to the lists about the integration of the MPSAFE TTY layer. July 13 2008: Make uart(4) the default serial port driver, instead of sio(4). sio(4) has not been ported to the new TTY layer and is very hard to do so. uart(4) has been proven to be more portable than sio(4) and already supports the hardware we need. July 20 2008: Send another heads-up to the lists about the new TTY layer. Kindly ask people to test the patchset, port more drivers, etc. August 3 2008: Disconnect drivers from the build that haven't been patched in the MPSAFE TTY branch. August 8 2008: Send the last heads-up to the lists, to warn people about the big commit. August 10 2008: Commit the new MPSAFE TTY driver in several commits (first commit the layer itself, then commit changes to drivers one by one). I'll stay close to my inbox the next couple of days after I've integrated the code, to make sure I can fix any bugs which may be spotted to be fixed shortly. Please, make sure we can make this a smooth transition by testing/reviewing my code. I tend to generate diffs very often. They can be downloaded here: http://www.il.fontys.nl/~ed/projects/mpsafetty/patches/ Thanks! --=20 Ed Schouten WWW: http://80386.nl/ --Bk6L21jbBNK7V1Rv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhr0k0ACgkQ52SDGA2eCwVIAACeI4NqzWRZ3Si7b5zhBdoCc6mM T3YAn2qvQJHuSgTeIZXFKkL2mDydJcLD =x78/ -----END PGP SIGNATURE----- --Bk6L21jbBNK7V1Rv-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 18:48:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11EB41065672 for ; Wed, 2 Jul 2008 18:48:35 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id D9CED8FC19 for ; Wed, 2 Jul 2008 18:48:34 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so427423wfg.7 for ; Wed, 02 Jul 2008 11:48:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=neSnrLcMoy+UCGVS9M2Lb0uv3cGjDzlELQS5qgIjp9I=; b=VvKcroxmp032D0vL3DIkFNYQJigCF7aMXGxdgHOhF7Crl40Fo3PKexq+7bi22YYpfv irUS35a+4nq+nbWDk+QEuUb828Z4mJM4AItSHE2xzgm5T155Js7K6BpEEMIQ87WnNNdo zJnAOlvKhfLLPJ6hmymRK+xiC5vRW2RExC0MQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=L6OyeG+m7X6K4zAYOsxVH6PwbuyEoy1gJ09cBgUNazbTY/9Rr5nU4ujMFJS9lpWBuy ruqpB3h+Yqk+7KgcDCKOA31YG3UvBg9eqL1P9CKyRPEzNsXieOFG6Dsmp6tjqKy9+gqq tKgP7NARaFHm+3Aax5Hcsw0UYlzs0zCIGceSc= Received: by 10.142.177.7 with SMTP id z7mr3183663wfe.88.1215023028088; Wed, 02 Jul 2008 11:23:48 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Wed, 2 Jul 2008 11:23:48 -0700 (PDT) Message-ID: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> Date: Wed, 2 Jul 2008 11:23:48 -0700 From: "Rob Lytle" To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 02 Jul 2008 19:29:59 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 18:48:35 -0000 Hi All, My depressing analysis- YMMV. I've used FreeBSD since 1998. 1..Installing the packages off of the menu on the 3 CDROMs is an incredibly tedious miserable process. I had to switch out the CD's around 40 times. If you don't believe me, just mark a whole bunch of random packages after obtaining the 7.0 release CD's, ad then install. Its frustrating and almost like Windows, except its a bit faster as replacing CD's is faster than reboots. 2. When installing any given package, if a dependency is already there , the package aborts and then goes though some loop where you have to press OK half a dozen times. Thats insane. I think the CD switching problem would be to install all the packages at once from CD1, then CD2, then CD3. As for the second case, I don't know enough about the infrastructure to suggest any thing except to perhaps comment that code in its entirety or put in switch to bypass already installed dependencies. I wish I knew more about your infrastructure to fix this myself. Is it written in Python? Thats the only language I'm not so rusty at. I've programmed in 5 languages, but that was long ago. I'm old. But someone who knows the system could probably fix it fast. I think this is such an inherent infrastructure problem that has existed so long that a bug report would be futile. Food for thought. Thanks, Rob -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 22:23:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE4DF106564A for ; Wed, 2 Jul 2008 22:23:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 56D888FC13 for ; Wed, 2 Jul 2008 22:23:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 25287 invoked by uid 399); 2 Jul 2008 22:23:35 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 2 Jul 2008 22:23:35 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <486BFFE5.1010808@FreeBSD.org> Date: Wed, 02 Jul 2008 15:23:33 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Panic using rsync to msdosfs filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 22:23:36 -0000 I have a western digital passport USB hard drive that I use for backups. It's always worked fine in FreeBSD and Windows doing straight copies. Today I tried to get fancy and use rsync and it blew up on me. It is a large disk (160G) and I use the following options in fstab: /dev/da0s1 /mnt/wd msdosfs rw,noauto,-olarge,-m775 0 0 Using the following command line for rsync I get a panic as soon as I hit return: rsync -vv --backup -u -rlt source/ destination/ I'm using -current as of r180191. Here is the stack trace: Unread portion of the kernel message buffer: panic: stack overflow detected; backtrace may be corrupted cpuid = 1 Uptime: 1h52m1s Physical memory: 2029 MB Dumping 133 MB: 118 102 86 70 54 38 22 6 Reading symbols from /boot/modules/nvidia.ko...Reading symbols from /boot/modules/nvidia.ko.symbols...done. done. Loaded symbols for /boot/modules/nvidia.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/if_bge.ko...Reading symbols from /boot/kernel/if_bge.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_bge.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/msdosfs.ko...Reading symbols from /boot/kernel/msdosfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/msdosfs.ko #0 doadump () at pcpu.h:196 196 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) where #0 doadump () at pcpu.h:196 #1 0xc057a9ce in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:418 #2 0xc057ac93 in panic (fmt=Variable "fmt" is not available. ) at /usr/local/src/sys/kern/kern_shutdown.c:572 #3 0xc059c5b2 in __stack_chk_fail () at /usr/local/src/sys/kern/stack_protector.c:17 #4 0xc652384a in msdosfs_rename (ap=0xc644aca4) at /usr/local/src/sys/modules/msdosfs/../../fs/msdosfs/msdosfs_vnops.c:1286 #5 0xc07b4df5 in VOP_RENAME_APV (vop=0xc6525cc0, a=0xe9e59c1c) at vnode_if.c:1184 #6 0xc0605619 in kern_renameat (td=0xc58f1d20, oldfd=-100, old=0xbfbfc4a0
, newfd=-100, new=0xbfbfcca0
, pathseg=UIO_USERSPACE) at vnode_if.h:622 #7 0xc06057a6 in kern_rename (td=0xc58f1d20, from=0xbfbfc4a0
, to=0xbfbfcca0
, pathseg=UIO_USERSPACE) at /usr/local/src/sys/kern/vfs_syscalls.c:3526 #8 0xc06057d9 in rename (td=0xc58f1d20, uap=0xe9e59cf8) at /usr/local/src/sys/kern/vfs_syscalls.c:3503 #9 0xc07a6283 in syscall (frame=0xe9e59d38) at /usr/local/src/sys/i386/i386/trap.c:1081 #10 0xc078bb80 in Xint0x80_syscall () at /usr/local/src/sys/i386/i386/exception.s:261 #11 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Let me know what I can do to help. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 22:45:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13BDF1065679 for ; Wed, 2 Jul 2008 22:45:30 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 82E408FC14 for ; Wed, 2 Jul 2008 22:45:29 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-002-228.pools.arcor-ip.net [88.66.2.228]) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis) id 0MKwtQ-1KEB4q1n2h-0006AC; Thu, 03 Jul 2008 00:45:28 +0200 Received: (qmail 7636 invoked from network); 2 Jul 2008 22:45:28 -0000 Received: from myhost.laiers.local (192.168.4.151) by ns1.laiers.local with SMTP; 2 Jul 2008 22:45:28 -0000 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Thu, 3 Jul 2008 00:43:18 +0200 User-Agent: KMail/1.9.9 References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> In-Reply-To: <486BFE3B.3040509@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807030043.18865.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1+gVg1WyAibawGYMWy2zRFv0boxSBeRnOVsnNp 4KU6cQjiEmqIB+LmDMqH0lyIO6IPrT2/IbQEFSJR7S3kH3eGU/ kNuDtY5yRXp6f0yhIw5SA== Cc: freebsd-current@freebsd.org, jan6146@gmail.com, Curtis Penner Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 22:45:30 -0000 http://www.pcbsd.org/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 22:44:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C34B1065674 for ; Wed, 2 Jul 2008 22:44:55 +0000 (UTC) (envelope-from curtis.penner2@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 230DE8FC14 for ; Wed, 2 Jul 2008 22:44:54 +0000 (UTC) (envelope-from curtis.penner2@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so316090pyb.10 for ; Wed, 02 Jul 2008 15:44:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Sa+r45eKEyrdWwy/piwoO2ExL44jGcpSQslEfp9uVCs=; b=QWQLxmPhUqXzeP04v695Bkk8gZwSmh+Z7A0k6wXdYZvyavJwu5xVNHlE+hUorYPXJD OJxiMe99bJWLR4C9ACwXkWG+t6smR6NIEOyiGEO+K2UPSdOWbvV0KLVigy6m7afhkFaD DaQeQuMiKOCjNBoMmncg9F9wqLYv8oDjKd2rY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=cDkqtgw+g4CL4JnlapXpzG6ySRXSgjKFmAlJ00PuM7aVnw0lf23+4WRokUYNy9PgUs lTxFYh7WVr2dpHmt1g+kak15WU3Hx8H01li8zax4HkxFegiu96/RF5S/LTrTVzCveEBL aHYcO/1GF2MXmDFY4zkVYYrwJkQJe/QuJEcQU= Received: by 10.142.173.8 with SMTP id v8mr1224516wfe.221.1215037026730; Wed, 02 Jul 2008 15:17:06 -0700 (PDT) Received: from ?192.168.2.105? ( [71.131.191.52]) by mx.google.com with ESMTPS id 29sm18706046wfg.0.2008.07.02.15.16.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Jul 2008 15:17:04 -0700 (PDT) Message-ID: <486BFE3B.3040509@gmail.com> Date: Wed, 02 Jul 2008 15:16:27 -0700 From: Curtis Penner User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: jan6146@gmail.com References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> In-Reply-To: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 02 Jul 2008 22:51:33 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 22:44:55 -0000 Let us take this further. Let's compare BSD to the Linux install solutions. Well, lets not, Linux is so far ahead of BSD. Linux understands the user. BSD has a better overall core OS then the other UNIX flavors. The size to capability is outstanding. Once you have the core OS on the system it is rock steady and only getting better. The documentation is outstanding. It is what others should look to. So what is wrong? It doesn't have the native 3rd party applications. Why? Not enough users. Why? Because it is hard to get what you want unless you are tech savvy. When you do a system install it is like jumping back to the 80's. The front-end is like something from the DOS days. You have to be tech savvy to know what you want to do. You have to search out all the variations of the applications (tedious and unnecessary) to get a full package -- Examples: Postgres, PHP, etc. To add wireless (very common these day), you better set aside as much time or more as doing the initial install. Given that the system is rock solid, you think more people would develop on it, at least secondarily. But no. Java - go fish. All the development environments and features that go with it (Eclipse, NetBean, Hibernation, Sturts, and so forth) are painful to get. You feel like a rabbit jumping around, and then it most likely doesn't work. That is such a turn off. As for the installs, to get an idea of how to package an install, look at the current install packages that are from the Linux side. You don't have to copy, but emulate. (Oh, the best out-of-the-box is Apple.) I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), and the BSDs, and I have found the BSDs to be so yesterday that there is little in common with the rest. Porting, so that applications that matter go native, we need more installs and more people on the systems. That means more installs to laptops. The installs have to be seamless and complete. That mean getting more Open Source people and companies to compile and distribute BSD. I am looking forward to a time when installing BSD is point and click with not much understanding of what is going on (unless I want to go advance and do special custom work). -Curtis Rob Lytle wrote: > Hi All, > > My depressing analysis- YMMV. I've used FreeBSD since 1998. > > 1..Installing the packages off of the menu on the 3 CDROMs is an incredibly > tedious miserable process. I had to switch out the CD's around 40 times. > If you don't believe me, just mark a whole bunch of random packages after > obtaining the 7.0 release CD's, ad then install. Its frustrating and almost > like Windows, except its a bit faster as replacing CD's is faster than > reboots. > > 2. When installing any given package, if a dependency is already there , > the package aborts and then goes though some loop where you have to press > OK half a dozen times. Thats insane. > > I think the CD switching problem would be to install all the packages at > once from CD1, then CD2, then CD3. As for the second case, I don't know > enough about the infrastructure to suggest any thing except to perhaps > comment that code in its entirety or put in switch to bypass already > installed dependencies. > > I wish I knew more about your infrastructure to fix this myself. Is it > written in Python? Thats the only language I'm not so rusty at. I've > programmed in 5 languages, but that was long ago. I'm old. But someone who > knows the system could probably fix it fast. I think this is such an > inherent infrastructure problem that has existed so long that a bug report > would be futile. > > Food for thought. Thanks, > > Rob > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:15:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45683106567F for ; Wed, 2 Jul 2008 23:15:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1CA5F8FC21 for ; Wed, 2 Jul 2008 23:15:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1A5F146B9D; Wed, 2 Jul 2008 18:59:56 -0400 (EDT) Date: Wed, 2 Jul 2008 23:59:56 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rob Lytle In-Reply-To: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> Message-ID: <20080702235800.H47773@fledge.watson.org> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:15:54 -0000 On Wed, 2 Jul 2008, Rob Lytle wrote: > My depressing analysis- YMMV. I've used FreeBSD since 1998. The good news is that there are no less than three in-progress sysinstall replacements. At least two have been posted about recently with test ISOs for 7.0. And there are at least a couple of other variations floating around, such as the PC-BSD installer. So I think we can expect to see non-trivial progress here in the next year. My primary concern about some of these replacement installer projects is that they've placed a strong focus on making them graphical -- I actually couldn't care less about GUIs (and I think they actually hurt my configurations, since I use serial consoles a lot), but what I do want is a very tight and efficient install process, which I feel sysinstall does badly on (not just for the reasons you specify). Robert N M Watson Computer Laboratory University of Cambridge > > 1..Installing the packages off of the menu on the 3 CDROMs is an incredibly > tedious miserable process. I had to switch out the CD's around 40 times. > If you don't believe me, just mark a whole bunch of random packages after > obtaining the 7.0 release CD's, ad then install. Its frustrating and almost > like Windows, except its a bit faster as replacing CD's is faster than > reboots. > > 2. When installing any given package, if a dependency is already there , > the package aborts and then goes though some loop where you have to press > OK half a dozen times. Thats insane. > > I think the CD switching problem would be to install all the packages at > once from CD1, then CD2, then CD3. As for the second case, I don't know > enough about the infrastructure to suggest any thing except to perhaps > comment that code in its entirety or put in switch to bypass already > installed dependencies. > > I wish I knew more about your infrastructure to fix this myself. Is it > written in Python? Thats the only language I'm not so rusty at. I've > programmed in 5 languages, but that was long ago. I'm old. But someone who > knows the system could probably fix it fast. I think this is such an > inherent infrastructure problem that has existed so long that a bug report > would be futile. > > Food for thought. Thanks, > > Rob > > > -- > ---------------------------------------------------------- > http://www.youtube.com/user/whiteflluffyclouds > (Ham radio videos) > _______________________________________________ > 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" > From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:16:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 984881065671; Wed, 2 Jul 2008 23:16:38 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from fb1.tech.numericable.fr (fb1.tech.numericable.fr [82.216.111.51]) by mx1.freebsd.org (Postfix) with ESMTP id 277B58FC0C; Wed, 2 Jul 2008 23:16:38 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from smtp5.tech.numericable.fr (smtp5.nc.sdv.fr [10.0.0.72]) by fb1.tech.numericable.fr (Postfix) with ESMTP id F087C11DCDF; Thu, 3 Jul 2008 01:03:08 +0200 (CEST) Received: from brunel.pagan.fr (cable-83.217.146.118.coditel.net [83.217.146.118]) by smtp5.tech.numericable.fr (Postfix) with ESMTP id 311FD124009; Thu, 3 Jul 2008 01:03:07 +0200 (CEST) Message-ID: <486C0928.8050607@yahoo.fr> Date: Thu, 03 Jul 2008 01:03:04 +0200 From: Antoine BRUNEL User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Curtis Penner References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> In-Reply-To: <486BFE3B.3040509@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:16:38 -0000 I complete what Curtis wrote... How many times do you have to install a BSD system ??? even in case of hell, you can still remove every ports/ package, juste leaving the CSH and kernel layer, then install what you need again... try to remove the "glibc" package from Linux (an Howto exists), and enjoy.... Compared to Windows / Linux (RedHat or Suse distributions), BSD still offers a way to finely tune your system depending on your needs, instead of putting gigabyte software in place, "just in case of", with tons of windows managers, productivity tools, etc... BSD are still "harder" systems compared to other, but with more control on what happens.... In conclusion, I can agree you in that the "sysinstall" soft is a bit out-dated, but it respond on a need of a BSD philosophy: just installing a working operating system. All the later tasks have to be done by "hands". But that's exactly what I wanted when I replaced Windows / Debian to FreeBSD: having a full control on my system. So, just another useless contribution..... Curtis Penner a écrit : > Let us take this further. > > Let's compare BSD to the Linux install solutions. Well, lets not, > Linux is so far ahead of BSD. Linux understands the user. > > BSD has a better overall core OS then the other UNIX flavors. The > size to capability is outstanding. Once you have the core OS on the > system it is rock steady and only getting better. The documentation > is outstanding. It is what others should look to. > > So what is wrong? > > It doesn't have the native 3rd party applications. Why? Not enough > users. Why? Because it is hard to get what you want unless you are > tech savvy. > > When you do a system install it is like jumping back to the 80's. The > front-end is like something from the DOS days. You have to be tech > savvy to know what you want to do. You have to search out all the > variations of the applications (tedious and unnecessary) to get a full > package -- Examples: Postgres, PHP, etc. To add wireless (very common > these day), you better set aside as much time or more as doing the > initial install. > > Given that the system is rock solid, you think more people would > develop on it, at least secondarily. But no. Java - go fish. All > the development environments and features that go with it (Eclipse, > NetBean, Hibernation, Sturts, and so forth) are painful to get. You > feel like a rabbit jumping around, and then it most likely doesn't > work. That is such a turn off. > > As for the installs, to get an idea of how to package an install, look > at the current install packages that are from the Linux side. You > don't have to copy, but emulate. (Oh, the best out-of-the-box is Apple.) > > I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), > and the BSDs, and I have found the BSDs to be so yesterday that there > is little in common with the rest. > > Porting, so that applications that matter go native, we need more > installs and more people on the systems. That means more installs to > laptops. The installs have to be seamless and complete. That mean > getting more Open Source people and companies to compile and > distribute BSD. > > I am looking forward to a time when installing BSD is point and click > with not much understanding of what is going on (unless I want to go > advance and do special custom work). > > > -Curtis > > > Rob Lytle wrote: >> Hi All, >> >> My depressing analysis- YMMV. I've used FreeBSD since 1998. >> >> 1..Installing the packages off of the menu on the 3 CDROMs is an >> incredibly >> tedious miserable process. I had to switch out the CD's around 40 >> times. >> If you don't believe me, just mark a whole bunch of random packages >> after >> obtaining the 7.0 release CD's, ad then install. Its frustrating and >> almost >> like Windows, except its a bit faster as replacing CD's is faster than >> reboots. >> >> 2. When installing any given package, if a dependency is already >> there , >> the package aborts and then goes though some loop where you have to >> press >> OK half a dozen times. Thats insane. >> >> I think the CD switching problem would be to install all the packages at >> once from CD1, then CD2, then CD3. As for the second case, I don't know >> enough about the infrastructure to suggest any thing except to perhaps >> comment that code in its entirety or put in switch to bypass already >> installed dependencies. >> >> I wish I knew more about your infrastructure to fix this myself. Is it >> written in Python? Thats the only language I'm not so rusty at. I've >> programmed in 5 languages, but that was long ago. I'm old. But >> someone who >> knows the system could probably fix it fast. I think this is such an >> inherent infrastructure problem that has existed so long that a bug >> report >> would be futile. >> >> Food for thought. Thanks, >> >> Rob >> >> > _______________________________________________ > 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" > From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:26:22 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36F591065673; Wed, 2 Jul 2008 23:26:22 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id 1B66E8FC2A; Wed, 2 Jul 2008 23:26:22 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KEBiO-000Oi1-T8; Wed, 02 Jul 2008 23:26:21 +0000 Message-ID: <486C0E9B.5070608@psg.com> Date: Thu, 03 Jul 2008 08:26:19 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Curtis Penner References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> In-Reply-To: <486BFE3B.3040509@gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:26:22 -0000 > I am looking forward to a time when installing BSD is point and click if i want point and click, i use a mac (and spend a lot of time using find to see where the hell they moved things). if i want solid & performance, i run freebsd and learn to live with portupgrade. because expert people resources are very limited, i would rather that freebsd folk work on solid & performance. randy, who is embarrassed by his lack of contribution From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:34:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C40C1065673 for ; Wed, 2 Jul 2008 23:34:13 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id 1CF618FC0C for ; Wed, 2 Jul 2008 23:34:13 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id B8A9224D22; Thu, 3 Jul 2008 01:34:11 +0200 (SAST) Date: Thu, 3 Jul 2008 01:34:11 +0200 From: Aragon Gouveia To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Message-ID: <20080702233411.GA26065@phat.za.net> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <486BFE3B.3040509@gmail.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Cc: Curtis Penner Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:34:13 -0000 Hi, As just another FreeBSD user.... | By Curtis Penner | [ 2008-07-03 00:51 +0200 ] > When you do a system install it is like jumping back to the 80's. The > front-end is like something from the DOS days. You have to be tech > savvy to know what you want to do. I respectfully disagree with your opinion of the installer. Contrary to your opinion, I cringe on the odd occasions that I have to install linux or windows. Sysinstall might have some quirks and look dated, but FreeBSD is the only OS I can install in less than 5-10 minutes AND still install only what I want the way I want it. I really hope the new installers that are in the pipeline don't change that. > You have to search out all the > variations of the applications (tedious and unnecessary) to get a full > package -- Examples: Postgres, PHP, etc. Again, disagree. Sounds like you don't like freedom of choice much. For me it's one of the best parts of FreeBSD's package management. > I am looking forward to a time when installing BSD is point and click > with not much understanding of what is going on (unless I want to go > advance and do special custom work). I'm not! If you don't care what is going on, why does it matter that you have FreeBSD installed? Pick something like PCBSD or even Ubuntu - as easy and thought free as it comes. Regards, Aragon From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:57:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2709106564A; Wed, 2 Jul 2008 23:57:20 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 72E828FC19; Wed, 2 Jul 2008 23:57:20 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.2/8.14.2) with ESMTP id m62NuRSE007696; Wed, 2 Jul 2008 18:56:28 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <486C15DE.3000504@math.missouri.edu> Date: Wed, 02 Jul 2008 18:57:18 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080701 SeaMonkey/1.1.9 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <20080702233411.GA26065@phat.za.net> In-Reply-To: <20080702233411.GA26065@phat.za.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:57:20 -0000 On the whole, I rather like the installation process for FreeBSD. Generally what I really like about FreeBSD is the ease of system administration, and whenever I use Linux distributions I get rather frustrated. If, as the OP suggests, installation of packages from the FreeBSD CD's requires switching around 40 times, then that is bad. But it should be something easily fixable, without greatly modifying the rest of the process. Stephen From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:59:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61D9A106564A for ; Wed, 2 Jul 2008 23:59:58 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id 369EF8FC0C for ; Wed, 2 Jul 2008 23:59:57 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so514555wfg.7 for ; Wed, 02 Jul 2008 16:59:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=A2SSamJ4nEL9arPHr6B9TTC0NgXjLw5+yaycFLriBaY=; b=jg89FmheFBMdUpfy9P0De99tr89EIKEvgJV0uWXALBm/lnJrMEyZrHDjxMoLB2bYl/ odDhOwuwz3BRmUzOxOLbWDhl+JIDqWq9l7GIVg14Prqrwx1wNLq89e6U51HD9Aq3wkRm FAwsXNooAp/XrH1oZF8XpMxCW8azDuveTgBYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=r3Qu4ntfEL2Y7Nf2bRPoceuI/E76dyeMDrqcJH3XBYJI0GAUujxg5r01S1Wp8CS/DI t+yfiXJYa3sEnchZBPnX4uASrevB0V9MIBseN3x4aXtv7CUMpxCkqhiiwd9O1J6ieIXF SVUMI5zwi7gV4kX1WZoepAtDRRtnjLUDncYE4= Received: by 10.142.154.20 with SMTP id b20mr2039036wfe.59.1215043197617; Wed, 02 Jul 2008 16:59:57 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Wed, 2 Jul 2008 16:59:57 -0700 (PDT) Message-ID: <784966050807021659h5ba54a2dy9093f6e1ab76f297@mail.gmail.com> Date: Wed, 2 Jul 2008 16:59:57 -0700 From: "Rob Lytle" To: "Sean Cavanaugh" , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 03 Jul 2008 01:08:57 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Sysinstall is still inadequate after all of these years / thanks for responding X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2008 23:59:58 -0000 Thanks Sean, This is the first time I ever actually downloaded all 3 CD's so i didn't know what I was getting into. I had always just used the first CD for the initial install, then ports for everything else. Next time I will use the dvd. Actually that would have been perfect as I got one of those unusual 550kB/s connections from ftp, lol. But I decided this time to get as many packages as quickly as possible, then run portupgrade on them to get the latest versions. I just did a make buildworld and made the kernel. Now I'm waiting here to do the make installworld after I go shopping. Plus its so hot here in Oregon I have to put the fan on my Sony VAIO SZ460N/C laptop. Its small but overheats, esp when using the NVidea graphics, so I use the i810 instead. I'm having problems with portupgrade though. Something got screwed up so a bunch of package compiles are failing. Most all of KDE is in there but it wont start and doesn't even give error messages, even when started with the console. In contrast Windowmaker works fine, so that is what I'm using now. I got another copy of ports.tar.gz as perhaps the old copy was corrupted, so after world gets installed, I will try portupgrade again. Sincerely, Rob On Wed, Jul 2, 2008 at 1:29 PM, Sean Cavanaugh wrote: > > Date: Wed, 2 Jul 2008 11:23:48 -0700 > > From: jan6146@gmail.com > > To: freebsd-hackers@freebsd.org; freebsd-current@freebsd.org > > CC: > > Subject: Sysinstall is still inadequate after all of these years > > > > > Hi All, > > > > My depressing analysis- YMMV. I've used FreeBSD since 1998. > > > > 1..Installing the packages off of the menu on the 3 CDROMs is an > incredibly > > tedious miserable process. I had to switch out the CD's around 40 times. > > If you don't believe me, just mark a whole bunch of random packages after > > obtaining the 7.0 release CD's, ad then install. Its frustrating and > almost > > like Windows, except its a bit faster as replacing CD's is faster than > > reboots. > > > > 2. When installing any given package, if a dependency is already there , > > the package aborts and then goes though some loop where you have to press > > OK half a dozen times. Thats insane. > > > > I think the CD switching problem would be to install all the packages at > > once from CD1, then CD2, then CD3. As for the second case, I don't know > > enough about the infrastructure to suggest any thing except to perhaps > > comment that code in its entirety or put in switch to bypass already > > installed dependencies. > > > > I wish I knew more about your infrastructure to fix this myself. Is it > > written in Python? Thats the only language I'm not so rusty at. I've > > programmed in 5 languages, but that was long ago. I'm old. But someone > who > > knows the system could probably fix it fast. I think this is such an > > inherent infrastructure problem that has existed so long that a bug > report > > would be futile. > > > > Food for thought. Thanks, > > > This is the reason I install everything from ports. > > The packages were divided into understandable clusters to make them fit on > CDs. Perhaps you would benefit from getting the DVD ISO instead which has > everything together. Im sure someone on the list could provide you the link > for it or google for it. > > -Sean > > -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 00:11:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB63F1065681 for ; Thu, 3 Jul 2008 00:11:48 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id 8C34A8FC3C for ; Thu, 3 Jul 2008 00:11:48 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so517899wfg.7 for ; Wed, 02 Jul 2008 17:11:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=mEhYzfAh61t3GsRxOHGOjS6iXjJiOtpU+IyX1u70PkQ=; b=UTD9T5e7xUPT58f8HpSyticY2MfYgcRKQig4DKAo68u5cMnv4Gjg8DMXX8fj7npbg6 o+HxqNQ5K3CqYAhvb9UnGD2FH1HswFcse6KVrGYzncRtmckv2jt64k3uyyhuLSP2tAMU rYrsdoNoz9xSQRSkRMtTuJ8B35KTLzLk6dsZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=yBt3QRm3fjlfll9NHpGngaLw0QKrGXDGSVud+QBHAAL0Ho55rHATB3IhVzs/LfQWyM huI4OL5jKy2UJDZJr2eeoPtkMqua5UOgL9/OtAdWzLZ6fKKl0sRM7RAslLCqXn0ee2m0 Id45WI5k1ugKlijw7kVax+uMx7esCl56lKtc0= Received: by 10.142.51.4 with SMTP id y4mr3303095wfy.220.1215043908089; Wed, 02 Jul 2008 17:11:48 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Wed, 2 Jul 2008 17:11:47 -0700 (PDT) Message-ID: <784966050807021711l3c738640gcc2579018b66d314@mail.gmail.com> Date: Wed, 2 Jul 2008 17:11:47 -0700 From: "Rob Lytle" To: "Antoine BRUNEL" , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <486C0928.8050607@yahoo.fr> MIME-Version: 1.0 References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <486C0928.8050607@yahoo.fr> X-Mailman-Approved-At: Thu, 03 Jul 2008 01:09:23 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 00:11:48 -0000 Thanks for responding Curtis, I've used FreeBSD for a long time. In fact, when the Athlon first came out= , FreeBSD would run with it, and SUSE would not. I thought that was a good sign that FreeBSD was top notch. Plus it booted faster than any computer and/or OS I had ever used. And the memory management was incredible. I hardly ever page out to swap, even running a number of apps at once. Nothing even slows down. But after I got this new laptop I never reinstalled it. Laptops are all made so crappy in China that every year or two something breaks, I get pissed, and I buy a new one. My old Dell had to have the motherboard replaced 5 times, 4 of those because the ethernet connector came loose and they had no choice but to put a new board in. All that for a $0.10 part. But I have problems just transferring hard drives because of SATA vs. IDE. I'm not sure how to get the data from one to another without a tape drive, which it seems is expensive. I dirched Ununtu as I found out my priority bug report was never acted on and is still there from a year a go, numbered up in the 20,000's. When you manually configure your Wifi, upon the next reboot it just goes out and randomly connects to any open access point- not my WAP encrypted one here. Even Vista can be set not to do that! Sincerely, Rob On Wed, Jul 2, 2008 at 4:03 PM, Antoine BRUNEL wrote: > I complete what Curtis wrote... > > How many times do you have to install a BSD system ??? even in case of > hell, you can still remove every ports/ package, juste leaving the CSH an= d > kernel layer, then install what you need again... try to remove the "glib= c" > package from Linux (an Howto exists), and enjoy.... > > Compared to Windows / Linux (RedHat or Suse distributions), BSD still > offers a way to finely tune your system depending on your needs, instead = of > putting gigabyte software in place, "just in case of", with tons of windo= ws > managers, productivity tools, etc... > > BSD are still "harder" systems compared to other, but with more control o= n > what happens.... > > In conclusion, I can agree you in that the "sysinstall" soft is a bit > out-dated, but it respond on a need of a BSD philosophy: just installing = a > working operating system. All the later tasks have to be done by "hands". > But that's exactly what I wanted when I replaced Windows / Debian to > FreeBSD: having a full control on my system. > > So, just another useless contribution..... > > > Curtis Penner a =E9crit : > >> Let us take this further. >> >> Let's compare BSD to the Linux install solutions. Well, lets not, Linux >> is so far ahead of BSD. Linux understands the user. >> >> BSD has a better overall core OS then the other UNIX flavors. The size = to >> capability is outstanding. Once you have the core OS on the system it is >> rock steady and only getting better. The documentation is outstanding. = It >> is what others should look to. >> >> So what is wrong? >> >> It doesn't have the native 3rd party applications. Why? Not enough users= . >> Why? Because it is hard to get what you want unless you are tech savvy. >> >> When you do a system install it is like jumping back to the 80's. The >> front-end is like something from the DOS days. You have to be tech savv= y to >> know what you want to do. You have to search out all the variations of = the >> applications (tedious and unnecessary) to get a full package -- Examples= : >> Postgres, PHP, etc. To add wireless (very common these day), you better= set >> aside as much time or more as doing the initial install. >> >> Given that the system is rock solid, you think more people would develop >> on it, at least secondarily. But no. Java - go fish. All the developm= ent >> environments and features that go with it (Eclipse, NetBean, Hibernation= , >> Sturts, and so forth) are painful to get. You feel like a rabbit jumpin= g >> around, and then it most likely doesn't work. That is such a turn off. >> >> As for the installs, to get an idea of how to package an install, look a= t >> the current install packages that are from the Linux side. You don't hav= e to >> copy, but emulate. (Oh, the best out-of-the-box is Apple.) >> >> I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), an= d >> the BSDs, and I have found the BSDs to be so yesterday that there is lit= tle >> in common with the rest. >> >> Porting, so that applications that matter go native, we need more instal= ls >> and more people on the systems. That means more installs to laptops. Th= e >> installs have to be seamless and complete. That mean getting more Open >> Source people and companies to compile and distribute BSD. >> >> I am looking forward to a time when installing BSD is point and click wi= th >> not much understanding of what is going on (unless I want to go advance = and >> do special custom work). >> >> >> -Curtis >> >> >> Rob Lytle wrote: >> >>> Hi All, >>> >>> My depressing analysis- YMMV. I've used FreeBSD since 1998. >>> >>> 1..Installing the packages off of the menu on the 3 CDROMs is an >>> incredibly >>> tedious miserable process. I had to switch out the CD's around 40 time= s. >>> If you don't believe me, just mark a whole bunch of random packages aft= er >>> obtaining the 7.0 release CD's, ad then install. Its frustrating and >>> almost >>> like Windows, except its a bit faster as replacing CD's is faster than >>> reboots. >>> >>> 2. When installing any given package, if a dependency is already there= , >>> the package aborts and then goes though some loop where you have to >>> press >>> OK half a dozen times. Thats insane. >>> >>> I think the CD switching problem would be to install all the packages a= t >>> once from CD1, then CD2, then CD3. As for the second case, I don't kno= w >>> enough about the infrastructure to suggest any thing except to perhaps >>> comment that code in its entirety or put in switch to bypass already >>> installed dependencies. >>> >>> I wish I knew more about your infrastructure to fix this myself. Is i= t >>> written in Python? Thats the only language I'm not so rusty at. I've >>> programmed in 5 languages, but that was long ago. I'm old. But someon= e >>> who >>> knows the system could probably fix it fast. I think this is such an >>> inherent infrastructure problem that has existed so long that a bug >>> report >>> would be futile. >>> >>> Food for thought. Thanks, >>> >>> Rob >>> >>> >>> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> >> --=20 ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 01:21:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5331D1065688 for ; Thu, 3 Jul 2008 01:21:16 +0000 (UTC) (envelope-from mwm-dated-1215910458.f313ad@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id E01F08FC1D for ; Thu, 3 Jul 2008 01:21:15 +0000 (UTC) (envelope-from mwm-dated-1215910458.f313ad@mired.org) Received: (qmail 2538 invoked by uid 1001); 2 Jul 2008 20:54:18 -0400 Received: from bhuda.mired.org (bhuda [192.168.195.1]) by bhuda (tmda-ofmipd) with ESMTP; Wed, 02 Jul 2008 20:54:16 -0400 Date: Wed, 2 Jul 2008 20:54:15 -0400 To: Curtis Penner Message-ID: <20080702205415.0165f389@bhuda.mired.org> In-Reply-To: <486BFE3B.3040509@gmail.com> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Mike Meyer X-Mailman-Approved-At: Thu, 03 Jul 2008 02:13:16 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 01:21:16 -0000 On Wed, 02 Jul 2008 15:16:27 -0700 Curtis Penner wrote: > BSD has a better overall core OS then the other UNIX flavors. I disagree, but that's another debate. BSD is still my desktop OS of choice. > So what is wrong? > > It doesn't have the native 3rd party applications. Why? Not enough > users. Why? Because it is hard to get what you want unless you are tech > savvy. Huh? The ports collection has nearly 19 thousand entries in it. Is there another OS with *anything* like that? The blastwave folks were recently bragging that they were going to hit 1800! Yeah, if you want *proprietary* tools, you lose. As far as I can tell, that kills you on three issues: Flash, high-end graphics performance, and virtualization tools. For pretty much everything else I've run into, we seem to do ok. > When you do a system install it is like jumping back to the 80's. The > front-end is like something from the DOS days. You have to be tech > savvy to know what you want to do. You have to search out all the > variations of the applications (tedious and unnecessary) to get a full > package -- Examples: Postgres, PHP, etc. To add wireless (very common > these day), you better set aside as much time or more as doing the > initial install. I find this to be the case on *every* system. I've never managed to find a system that provided *everything* I needed in an install. So I inevitably wind up wading through a see of repositories and dependencies to get what I need. For GNU/Linux, that usually means installing the tools I need to *build* what I actually need. Tedious and unnecessary would be a step *up*. > Given that the system is rock solid, you think more people would develop > on it, at least secondarily. But no. Java - go fish. All the > development environments and features that go with it (Eclipse, NetBean, > Hibernation, Sturts, and so forth) are painful to get. You feel like a > rabbit jumping around, and then it most likely doesn't work. That is > such a turn off. Ok, I don't do Java (because I like OO programming and want to keep it that way!), but I found three of the four things in the ports tree (assuming that Sturts is actually Struts, anyway). Which means the packages should be there as well. > As for the installs, to get an idea of how to package an install, look > at the current install packages that are from the Linux side. You don't > have to copy, but emulate. (Oh, the best out-of-the-box is Apple.) I'm not sure the best out of the box is Apple, but I haven't installed new Sun hardware in a *long* time. But Apple boxes come out of the box installed - that's hard to beat. As for GNU/Linux, the only install that comes close to installing a usable system is Gentoo. The other all seem to want to compete with windows, and treat their users like idiots who need every choice made for them. > I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), > and the BSDs, and I have found the BSDs to be so yesterday that there is > little in common with the rest. Hmm. Which Solaris did you use? SXCE b89 looks an awful lot like a FreeBSD install, except they do it under X with a GUI (so you need 3/4ths of a gig just to run the installer) - including progress messages to an xterm - instead of the console. 2008.05 looks amazingly like a GNU/Linux install - all pointy/clicky, no choices about what you want, you get 3 gig of lawn ornaments which I personally had no use for on the server in question (which is how I came to learn what an SXCE install looks like). Not to mention that after being installed, it's slower than Vista even when it's got more than twice the horsepower underneath it. > Porting, so that applications that matter go native, we need more > installs and more people on the systems. That means more installs to > laptops. The installs have to be seamless and complete. That mean > getting more Open Source people and companies to compile and distribute BSD. I believe we already have a bigger, better application repository than any other current Unix or Unix-like system. However, I can't find hard numbers for rpm or deb-based distributions repositories. But "rpms" or "debs" found scattered around the net aren't a "repository"; they won't work except against what they were build against, and trying to get them to is a *real* recipe for frustration. > I am looking forward to a time when installing BSD is point and click > with not much understanding of what is going on (unless I want to go > advance and do special custom work). Is it really that simple? If we had an installer that looked as pretty as a van gogh, and all you had to do was enter your country and postal code and it then installed the base system, you wouldn't be happy (I certainly wouldn't mind such a thing)? I suspect that what you *really* want - and what the GNU/Linux distros, and Solaris 2008.05, and OSX try to provide - is a system with everything you want pre-installed, without you having to figure it out how to use a package system or anything else that looks the least bit like work. Personally, no single system can do that for me. What I want on my desktop is different from what pretty much anyone else wants on their desktop is different from what I want on a router is different from what I want on a mail server is different from what I want on a web server is different from what I want on try-python.mired.org. Things that I can't do without on some are things that ask to be pwn'ed on others, and in some cases I want the same functionality from different tools on different systems. I don't care how familiar you are with a system, it's *far* easier to add the things you know you want to a solid base than it is to remove crap that will cause you headaches later from a distro whose design criteria was maximizing installations, hence checking off as many features on a checklist as possible. On a desktop box, unneeded tools are just a waste of space; on a server, they can be an open invitation to pwn your server. That said - yeah, our installer is old and primitive. But it'll run on almost nothing (3/4ths of a GIG just to run the INSTALLER!?!?!?). There are people working on improving it, but frankly, the needed improvements are largely cosmetic, not conceptual. Any replacement for the installer should require less work but not less smarts. It needs to ask questions, because the correct answer to every general question about what to install is "it depends on what you want it for." For people who just want to muck about with a desktop, there are a couple of FreeBSD distributions with live CD's and a plethora of applications installed, etc. That's the right way to go about attracting an audience from the desktop. FreeBSD is the easiest system I know of to tailor to my needs. So long as that remains true, it will remain my OS of choice. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 03:36:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 588FC106566C; Thu, 3 Jul 2008 03:36:16 +0000 (UTC) (envelope-from millenia2000@hotmail.com) Received: from bay0-omc3-s5.bay0.hotmail.com (bay0-omc3-s5.bay0.hotmail.com [65.54.246.205]) by mx1.freebsd.org (Postfix) with ESMTP id 41E6F8FC18; Thu, 3 Jul 2008 03:36:16 +0000 (UTC) (envelope-from millenia2000@hotmail.com) Received: from BAY126-DS5 ([65.55.131.32]) by bay0-omc3-s5.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Jul 2008 20:36:15 -0700 X-Originating-IP: [69.243.62.194] X-Originating-Email: [millenia2000@hotmail.com] Message-ID: In-Reply-To: <784966050807021659h5ba54a2dy9093f6e1ab76f297@mail.gmail.com> From: "Sean Cavanaugh" To: "Rob Lytle" , , X-Unsent: 1 References: <784966050807021659h5ba54a2dy9093f6e1ab76f297@mail.gmail.com> Date: Wed, 2 Jul 2008 23:36:09 -0400 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 Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 X-OriginalArrivalTime: 03 Jul 2008 03:36:15.0920 (UTC) FILETIME=[F2B90300:01C8DCBD] Cc: Subject: Re: Sysinstall is still inadequate after all of these years / thanks for responding X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 03:36:16 -0000 From: Rob Lytle Sent: Wednesday, July 02, 2008 7:59 PM To: Sean Cavanaugh ; freebsd-hackers@freebsd.org ; freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / thanks for responding Thanks Sean, This is the first time I ever actually downloaded all 3 CD's so i didn't know what I was getting into. I had always just used the first CD for the initial install, then ports for everything else. Next time I will use the dvd. Actually that would have been perfect as I got one of those unusual 550kB/s connections from ftp, lol. But I decided this time to get as many packages as quickly as possible, then run portupgrade on them to get the latest versions. I just did a make buildworld and made the kernel. Now I'm waiting here to do the make installworld after I go shopping. Plus its so hot here in Oregon I have to put the fan on my Sony VAIO SZ460N/C laptop. Its small but overheats, esp when using the NVidea graphics, so I use the i810 instead. I'm having problems with portupgrade though. Something got screwed up so a bunch of package compiles are failing. Most all of KDE is in there but it wont start and doesn't even give error messages, even when started with the console. In contrast Windowmaker works fine, so that is what I'm using now. I got another copy of ports.tar.gz as perhaps the old copy was corrupted, so after world gets installed, I will try portupgrade again. Sincerely, Rob try 'portsnap'. it will maintain your /usr/ports folder for you. or use 'cvsup' on it. there are much better ways to maintain your ports folder without resorting to downloading the hideous ports.tar.gz file and extracting it. You also might want to remove and reinstall kde if its screwing up for you -Sean From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 04:28:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1B2E1065681 for ; Thu, 3 Jul 2008 04:28:51 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 74CD58FC1E for ; Thu, 3 Jul 2008 04:28:51 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so584234wfg.7 for ; Wed, 02 Jul 2008 21:28:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=5FYmb6FpJrW33RLdNycoPMnYk3NbISYiEnsVM61slXU=; b=XCZowAUwwG+FyMsGQasoNV1e3g78b3wwhjA47adXL7XdgHjaDRut0qszxssTzKxo08 hoFI6jp3HQ2rajv+cRH2GcB5h+1xTKoA4njHIejj4tHG8J9+O4ulxiUkuptRtUWB7U5S NT+zGSOh8LGwccmyBaRgbaMdfk/1nxBEwNSuI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=YcTehupnCtLcK4ZZNXcYvax62wandn/OwVjo5vfFf2KZPbLYKYNF7GbZ1//3ZtLg2D EDy7GPMOwiEv6eoOI4CwHp7aGA9/XC5y5CPi/WYeP1QmgcqiCS+3O0JB2lHor/yjfsOh /w0+vEWRNnHL2lV4ZWpGal8PK0pItbx7pEVFc= Received: by 10.142.221.19 with SMTP id t19mr3382409wfg.235.1215059330638; Wed, 02 Jul 2008 21:28:50 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Wed, 2 Jul 2008 21:28:50 -0700 (PDT) Message-ID: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> Date: Wed, 2 Jul 2008 21:28:50 -0700 From: "Rob Lytle" To: "Mike Meyer" , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 03 Jul 2008 05:04:21 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 04:28:51 -0000 Hi All, I'm sorry I started a kind of flame war. All I wanted was two things: 1. CD's that installed without being switched in and out dozens of times. That was fixed by the suggestion of using a DVD. I didn't even know the DVD install existed, but will do that next time. 2. Being able to use Sysinstall and not having it crash when a dependency is already present. Sometimes I like to use Sysinstall to install gigantic packages where the compile time is 26 hours, e.g KDE metapackage, and my notebook uses an Intel Core 2 Duo at 2Ghz or thereabout. That is one hell of a long compile time. For this request I will just have to wait for FreeBSD 10.0. Sincerely, Rob On Wed, Jul 2, 2008 at 5:54 PM, Mike Meyer wrote: > On Wed, 02 Jul 2008 15:16:27 -0700 > Curtis Penner wrote: > > > BSD has a better overall core OS then the other UNIX flavors. > > I disagree, but that's another debate. BSD is still my desktop OS of > choice. > > > So what is wrong? > > > > It doesn't have the native 3rd party applications. Why? Not enough > > users. Why? Because it is hard to get what you want unless you are tech > > savvy. > > Huh? The ports collection has nearly 19 thousand entries in it. Is > there another OS with *anything* like that? The blastwave folks were > recently bragging that they were going to hit 1800! > > Yeah, if you want *proprietary* tools, you lose. As far as I can tell, > that kills you on three issues: Flash, high-end graphics performance, > and virtualization tools. For pretty much everything else I've run > into, we seem to do ok. > > > When you do a system install it is like jumping back to the 80's. The > > front-end is like something from the DOS days. You have to be tech > > savvy to know what you want to do. You have to search out all the > > variations of the applications (tedious and unnecessary) to get a full > > package -- Examples: Postgres, PHP, etc. To add wireless (very common > > these day), you better set aside as much time or more as doing the > > initial install. > > I find this to be the case on *every* system. I've never managed to > find a system that provided *everything* I needed in an install. So I > inevitably wind up wading through a see of repositories and > dependencies to get what I need. For GNU/Linux, that usually means > installing the tools I need to *build* what I actually > need. Tedious and unnecessary would be a step *up*. > > > Given that the system is rock solid, you think more people would develop > > on it, at least secondarily. But no. Java - go fish. All the > > development environments and features that go with it (Eclipse, NetBean, > > Hibernation, Sturts, and so forth) are painful to get. You feel like a > > rabbit jumping around, and then it most likely doesn't work. That is > > such a turn off. > > Ok, I don't do Java (because I like OO programming and want to keep it > that way!), but I found three of the four things in the ports tree > (assuming that Sturts is actually Struts, anyway). Which means the > packages should be there as well. > > > As for the installs, to get an idea of how to package an install, look > > at the current install packages that are from the Linux side. You don't > > have to copy, but emulate. (Oh, the best out-of-the-box is Apple.) > > I'm not sure the best out of the box is Apple, but I haven't installed > new Sun hardware in a *long* time. But Apple boxes come out of the box > installed - that's hard to beat. > > As for GNU/Linux, the only install that comes close to installing a > usable system is Gentoo. The other all seem to want to compete with > windows, and treat their users like idiots who need every choice made > for them. > > > I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), > > and the BSDs, and I have found the BSDs to be so yesterday that there is > > little in common with the rest. > > Hmm. Which Solaris did you use? SXCE b89 looks an awful lot like a > FreeBSD install, except they do it under X with a GUI (so you need > 3/4ths of a gig just to run the installer) - including progress > messages to an xterm - instead of the console. 2008.05 looks amazingly > like a GNU/Linux install - all pointy/clicky, no choices about what > you want, you get 3 gig of lawn ornaments which I personally had no > use for on the server in question (which is how I came to learn what > an SXCE install looks like). Not to mention that after being > installed, it's slower than Vista even when it's got more than twice > the horsepower underneath it. > > > Porting, so that applications that matter go native, we need more > > installs and more people on the systems. That means more installs to > > laptops. The installs have to be seamless and complete. That mean > > getting more Open Source people and companies to compile and distribute > BSD. > > I believe we already have a bigger, better application repository than > any other current Unix or Unix-like system. However, I can't find hard > numbers for rpm or deb-based distributions repositories. But "rpms" or > "debs" found scattered around the net aren't a "repository"; they > won't work except against what they were build against, and trying to > get them to is a *real* recipe for frustration. > > > I am looking forward to a time when installing BSD is point and click > > with not much understanding of what is going on (unless I want to go > > advance and do special custom work). > > Is it really that simple? If we had an installer that looked as pretty > as a van gogh, and all you had to do was enter your country and postal > code and it then installed the base system, you wouldn't be happy (I > certainly wouldn't mind such a thing)? > > I suspect that what you *really* want - and what the GNU/Linux > distros, and Solaris 2008.05, and OSX try to provide - is a system > with everything you want pre-installed, without you having to figure > it out how to use a package system or anything else that looks the > least bit like work. > > Personally, no single system can do that for me. What I want on my > desktop is different from what pretty much anyone else wants on their > desktop is different from what I want on a router is different from > what I want on a mail server is different from what I want on a web > server is different from what I want on try-python.mired.org. Things > that I can't do without on some are things that ask to be pwn'ed on > others, and in some cases I want the same functionality from different > tools on different systems. > > I don't care how familiar you are with a system, it's *far* easier to > add the things you know you want to a solid base than it is to remove > crap that will cause you headaches later from a distro whose design > criteria was maximizing installations, hence checking off as many > features on a checklist as possible. On a desktop box, unneeded tools > are just a waste of space; on a server, they can be an open invitation > to pwn your server. > > That said - yeah, our installer is old and primitive. But it'll run on > almost nothing (3/4ths of a GIG just to run the > INSTALLER!?!?!?). There are people working on improving it, but > frankly, the needed improvements are largely cosmetic, not > conceptual. Any replacement for the installer should require less work > but not less smarts. It needs to ask questions, because the correct > answer to every general question about what to install is "it depends > on what you want it for." > > For people who just want to muck about with a desktop, there are a > couple of FreeBSD distributions with live CD's and a plethora of > applications installed, etc. That's the right way to go about > attracting an audience from the desktop. > > FreeBSD is the easiest system I know of to tailor to my needs. So long > as that remains true, it will remain my OS of choice. > > -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Network/Unix/Perforce consultant, email for more information. > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 07:03:02 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A5531065671 for ; Thu, 3 Jul 2008 07:03:02 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 76CAB8FC1A for ; Thu, 3 Jul 2008 07:03:01 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl97-104.kln.forthnet.gr [77.49.104.104]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-4) with ESMTP id m636iLe0009819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Jul 2008 09:44:27 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m636iLxb017982; Thu, 3 Jul 2008 09:44:21 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m636iKhs017981; Thu, 3 Jul 2008 09:44:20 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Rob Lytle" References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> Date: Thu, 03 Jul 2008 09:44:20 +0300 In-Reply-To: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> (Rob Lytle's message of "Wed, 2 Jul 2008 21:28:50 -0700") Message-ID: <87bq1fbh6j.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m636iLe0009819 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.754, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.65, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 07:03:02 -0000 On Wed, 2 Jul 2008 21:28:50 -0700, "Rob Lytle" wrote: > 2. Being able to use Sysinstall and not having it crash when a > dependency is already present. Sometimes I like to use Sysinstall to > install gigantic packages where the compile time is 26 hours, e.g KDE > metapackage, and my notebook uses an Intel Core 2 Duo at 2Ghz or > thereabout. That is one hell of a long compile time. For this > request I will just have to wait for FreeBSD 10.0. Crashing is a bug. We should fix that. Having said this, I often use portupgrade for this sort of thing. After mounting the DVD, you can see what would be installed with # mount /cdrom # env PKG_PATH=/cdrom/packages/All portupgrade -n -N -PP postfix and then you can actually *run* the installation by removing the `-n' option from the portupgrade run. From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 08:23:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B998A106568E; Thu, 3 Jul 2008 08:23:09 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from smtp.cs.uni-tuebingen.de (u-173-c156.cs.uni-tuebingen.de [134.2.173.156]) by mx1.freebsd.org (Postfix) with ESMTP id 75EC08FC19; Thu, 3 Jul 2008 08:23:09 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from u-172-c158.cs.uni-tuebingen.de ([134.2.172.158]) by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1KEJjS-0000Bm-Js; Thu, 03 Jul 2008 09:59:58 +0200 Message-ID: <486C8700.5020100@lobraun.de> Date: Thu, 03 Jul 2008 10:00:00 +0200 From: Lothar Braun User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: rwatson@FreeBSD.org References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> In-Reply-To: <20080702235800.H47773@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 08:23:09 -0000 Robert Watson wrote: > My > primary concern about some of these replacement installer projects is > that they've placed a strong focus on making them graphical -- I > actually couldn't care less about GUIs (and I think they actually hurt > my configurations, since I use serial consoles a lot), but what I do > want is a very tight and efficient install process, which I feel > sysinstall does badly on (not just for the reasons you specify). Hmm, how should a tight and efficient installation process look like in your opinion? And what are the other points that are bad in systinstall? Regards, Lothar From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 08:28:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4300B1065674; Thu, 3 Jul 2008 08:28:33 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9F68A8FC13; Thu, 3 Jul 2008 08:28:32 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0662146B03; Thu, 3 Jul 2008 04:28:31 -0400 (EDT) Date: Thu, 3 Jul 2008 09:28:30 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Lothar Braun In-Reply-To: <486C8700.5020100@lobraun.de> Message-ID: <20080703092511.T69986@fledge.watson.org> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 08:28:33 -0000 On Thu, 3 Jul 2008, Lothar Braun wrote: > Robert Watson wrote: > >> My primary concern about some of these replacement installer projects is >> that they've placed a strong focus on making them graphical -- I actually >> couldn't care less about GUIs (and I think they actually hurt my >> configurations, since I use serial consoles a lot), but what I do want is a >> very tight and efficient install process, which I feel sysinstall does >> badly on (not just for the reasons you specify). > > Hmm, how should a tight and efficient installation process look like in your > opinion? And what are the other points that are bad in systinstall? For me, it's really about minimizing the time to get to a generic install from a CD or DVD. Most of the time, I don't do a lot of customization during the install -- I configure machines using DHCP, I add most packages later, and I tend to use default disk layouts since my servers don't multi-boot and the defaults currently seem "reasonable". I don't like being asked many more questions than whether or not to enable sshd, and what to set the root password to. This means that I find our current distributions menu a bit inefficient (I don't want sub-menus, I just want checkboxes), and that the inconsistency in the handling of the space/enter/tab/cursor keys across different libdialog interfaces in the install is awkward. The current generic and express installs seem to capture a lot of my desire, in that I can get a box installed in <5m including actual time to write out the file systems, which is great. I really don't want to lose this with a new installer :-). Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 11:01:06 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC98B1065671 for ; Thu, 3 Jul 2008 11:01:06 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id 7465F8FC18 for ; Thu, 3 Jul 2008 11:01:06 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id m63B13xJ012047; Thu, 3 Jul 2008 12:01:03 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1KEMYh-0006mA-1Y; Thu, 03 Jul 2008 12:01:03 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m63B12SE032678; Thu, 3 Jul 2008 12:01:02 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m63B12Mm032677; Thu, 3 Jul 2008 12:01:02 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Rob Lytle In-Reply-To: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 03 Jul 2008 12:01:02 +0100 Message-Id: <1215082862.32135.4.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 11:01:07 -0000 On Wed, 2008-07-02 at 11:23 -0700, Rob Lytle wrote: > Hi All, > > My depressing analysis- YMMV. I've used FreeBSD since 1998. > > 1..Installing the packages off of the menu on the 3 CDROMs is an incredibly > tedious miserable process. I had to switch out the CD's around 40 times. > If you don't believe me, just mark a whole bunch of random packages after > obtaining the 7.0 release CD's, ad then install. Its frustrating and almost > like Windows, except its a bit faster as replacing CD's is faster than > reboots. There's been a few reports of this (see e.g. PR misc/123632), but I've tried recreating it myself without much success. Do you happen to know roughly which packages you installed? I'd really like to fix it, but I need to be able to recreate it first... > 2. When installing any given package, if a dependency is already there , > the package aborts and then goes though some loop where you have to press > OK half a dozen times. Thats insane. I've not seen this either, but I'll see if I can recreate it in a couple of days. Do you happen to know if there is a PR about this issue? If not, is there any chance you could submit one with more details of the error messages? Thanks, Gaivn From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 09:07:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 703811065678; Thu, 3 Jul 2008 09:07:09 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.freebsd.org (Postfix) with ESMTP id A424F8FC1F; Thu, 3 Jul 2008 09:07:08 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.4/8.13.1) with ESMTP id m638uToj002250; Thu, 3 Jul 2008 10:56:29 +0200 (CEST) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.4/8.13.1/Submit) id m638uTpp002249; Thu, 3 Jul 2008 10:56:29 +0200 (CEST) (envelope-from hk) Date: Thu, 3 Jul 2008 10:56:29 +0200 From: Holger Kipp To: Antoine BRUNEL Message-ID: <20080703085629.GA1590@intserv.int1.b.intern> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <486C0928.8050607@yahoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <486C0928.8050607@yahoo.fr> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 03 Jul 2008 11:28:26 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com, Curtis Penner Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 09:07:09 -0000 Dear Antoine Brunel, I completely 100% agree. Actually I don't see the need for a new sysinstall. It does what it needs to do. I have seen the later RH- and SUSE-Installer, but I don't want them. What's the use of a graphical installer? The only thing endusers might need is the choice of installing all required packages for a Workstation (like X, OpenOffice, KDE with all the whistles (or GNOME if you like), Firefox, etc.). There is a metaport for this already available (or was some time ago), but I have never used it. Usually installation of FreeBSD (for me) is a server installation, so I don't need X or any of the other packages. So from my point of view: - if you think the default sysinstall software needs some improvements, go for it. Apart from fixing real bugs I don't see much need to change this. - don't make a graphical sysinstall thing - at least not as default. it would hurt all sysadmins that install anything remotely. It reminds me of the oracle installer translation from text-based to gui-based (a nightmare if you're not in the same lan). - if you have only one system to install, changing CDs is not a big deal. for current hardware, use a DVD. for mass installations, use fileserver installation (that's what I did, anyway). I am more than happy with sysinstall, have used it for years (starting with 2.2.8 actually) and don't want to see a colorful chingeling whistleblowing hard-to-maintain suitable for all graphics card gui installer. If you need something like this, use PC-BSD, MacOS X or even MS Windows or Linux, I say. That about my useless/worthless (or maybe 2cents) contribution Best regards, Holger Kipp On Thu, Jul 03, 2008 at 01:03:04AM +0200, Antoine BRUNEL wrote: > I complete what Curtis wrote... > > How many times do you have to install a BSD system ??? even in case of > hell, you can still remove every ports/ package, juste leaving the CSH > and kernel layer, then install what you need again... try to remove the > "glibc" package from Linux (an Howto exists), and enjoy.... > > Compared to Windows / Linux (RedHat or Suse distributions), BSD still > offers a way to finely tune your system depending on your needs, instead > of putting gigabyte software in place, "just in case of", with tons of > windows managers, productivity tools, etc... > > BSD are still "harder" systems compared to other, but with more control > on what happens.... > > In conclusion, I can agree you in that the "sysinstall" soft is a bit > out-dated, but it respond on a need of a BSD philosophy: just installing > a working operating system. All the later tasks have to be done by > "hands". But that's exactly what I wanted when I replaced Windows / > Debian to FreeBSD: having a full control on my system. > > So, just another useless contribution..... > > > Curtis Penner a écrit : > >Let us take this further. > > > >Let's compare BSD to the Linux install solutions. Well, lets not, > >Linux is so far ahead of BSD. Linux understands the user. > > > >BSD has a better overall core OS then the other UNIX flavors. The > >size to capability is outstanding. Once you have the core OS on the > >system it is rock steady and only getting better. The documentation > >is outstanding. It is what others should look to. > > > >So what is wrong? > > > >It doesn't have the native 3rd party applications. Why? Not enough > >users. Why? Because it is hard to get what you want unless you are > >tech savvy. > > > >When you do a system install it is like jumping back to the 80's. The > >front-end is like something from the DOS days. You have to be tech > >savvy to know what you want to do. You have to search out all the > >variations of the applications (tedious and unnecessary) to get a full > >package -- Examples: Postgres, PHP, etc. To add wireless (very common > >these day), you better set aside as much time or more as doing the > >initial install. > > > >Given that the system is rock solid, you think more people would > >develop on it, at least secondarily. But no. Java - go fish. All > >the development environments and features that go with it (Eclipse, > >NetBean, Hibernation, Sturts, and so forth) are painful to get. You > >feel like a rabbit jumping around, and then it most likely doesn't > >work. That is such a turn off. > > > >As for the installs, to get an idea of how to package an install, look > >at the current install packages that are from the Linux side. You > >don't have to copy, but emulate. (Oh, the best out-of-the-box is Apple.) > > > >I have installed Linux, MacOS, HPUX, Solaris, Window (NT, XP, Vista), > >and the BSDs, and I have found the BSDs to be so yesterday that there > >is little in common with the rest. > > > >Porting, so that applications that matter go native, we need more > >installs and more people on the systems. That means more installs to > >laptops. The installs have to be seamless and complete. That mean > >getting more Open Source people and companies to compile and > >distribute BSD. > > > >I am looking forward to a time when installing BSD is point and click > >with not much understanding of what is going on (unless I want to go > >advance and do special custom work). > > > > > >-Curtis > > > > > >Rob Lytle wrote: > >>Hi All, > >> > >>My depressing analysis- YMMV. I've used FreeBSD since 1998. > >> > >>1..Installing the packages off of the menu on the 3 CDROMs is an > >>incredibly > >>tedious miserable process. I had to switch out the CD's around 40 > >>times. > >>If you don't believe me, just mark a whole bunch of random packages > >>after > >>obtaining the 7.0 release CD's, ad then install. Its frustrating and > >>almost > >>like Windows, except its a bit faster as replacing CD's is faster than > >>reboots. > >> > >>2. When installing any given package, if a dependency is already > >>there , > >>the package aborts and then goes though some loop where you have to > >>press > >>OK half a dozen times. Thats insane. > >> > >>I think the CD switching problem would be to install all the packages at > >>once from CD1, then CD2, then CD3. As for the second case, I don't know > >>enough about the infrastructure to suggest any thing except to perhaps > >>comment that code in its entirety or put in switch to bypass already > >>installed dependencies. > >> > >>I wish I knew more about your infrastructure to fix this myself. Is it > >>written in Python? Thats the only language I'm not so rusty at. I've > >>programmed in 5 languages, but that was long ago. I'm old. But > >>someone who > >>knows the system could probably fix it fast. I think this is such an > >>inherent infrastructure problem that has existed so long that a bug > >>report > >>would be futile. > >> > >>Food for thought. Thanks, > >> > >>Rob > >> > >> > >_______________________________________________ > >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" > > > _______________________________________________ > 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" From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 11:39:47 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BD2D10656A9 for ; Thu, 3 Jul 2008 11:39:47 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id F293C8FC1E for ; Thu, 3 Jul 2008 11:39:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 6337746BC3 for ; Thu, 3 Jul 2008 07:39:46 -0400 (EDT) Date: Thu, 3 Jul 2008 12:39:46 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: <20080703123851.G31251@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: cvs commit: src/sys/netinet6 frag6.c ip6_forward.c ip6_input.c (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 11:39:47 -0000 FYI, there was a brief window between a commit I made last night and a commit I made this morning where kernels with INVARIANTS might/would panic in the IPv6 input routine. Not sure how I missed this, but I did, so apologies in advance if you run into it! The below commit corrects that problem. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Thu, 3 Jul 2008 10:55:13 +0000 (UTC) From: Robert Watson To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/netinet6 frag6.c ip6_forward.c ip6_input.c rwatson 2008-07-03 10:55:13 UTC FreeBSD src repository Modified files: sys/netinet6 frag6.c ip6_forward.c ip6_input.c Log: SVN rev 180214 on 2008-07-03 10:55:13Z by rwatson Remove GIANT_REQUIRED from IPv6 input, forward, and frag6 code. The frag6 code is believed to be MPSAFE, and leaving aside the IPv6 route cache in forwarding, Giant appears not to adequately synchronize the data structures in the input or forwarding paths. Revision Changes Path 1.36 +0 -4 src/sys/netinet6/frag6.c 1.42 +1 -1 src/sys/netinet6/ip6_forward.c 1.100 +0 -2 src/sys/netinet6/ip6_input.c From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 12:10:15 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B17C106567B for ; Thu, 3 Jul 2008 12:10:15 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id DAE308FC15 for ; Thu, 3 Jul 2008 12:10:14 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so327657ywe.13 for ; Thu, 03 Jul 2008 05:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:subject :message-id:mail-followup-to:mime-version:content-type :content-disposition:user-agent:organization:x-operation-sytem:from; bh=vSVU1bh/J9og3P0ZXkeR1MuZMgdZ7p7CA1BrBwA1mzM=; b=hW0qi/jW0k0DjlQALqeWTksmjU31wkFwHJ1T6PhVlNdXdl+HSUXN32kDRWutToI6Xl K89JC/H/P1h/MKsaRA98zwicdj+PmwNy7m7JlMlB+os6Tl1CxJ/eRIxwgLIW5A2jxv+g yMbKI7Z2zYNTT5C0lRDwOIKbLAepXPJq7Y/Tg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent:organization :x-operation-sytem:from; b=wKWsCQRhFZgYPz+KHNW29owDPJQs1u/u0/aSFHIuRjTBxVnga60mOqGlLZt2uDX3hJ oYUw6Ep+2mBZuQk203Lu0UxMIBywxTU+tPipgBx7FKADO3FWzlH/uu5ye4GkE2RZtWfG 5i42ulgBJ8MCYgu1yp0RsC/kJ5TO4a8LDXOG0= Received: by 10.114.178.13 with SMTP id a13mr8128331waf.158.1215085371067; Thu, 03 Jul 2008 04:42:51 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id k2sm10942rvb.4.2008.07.03.04.42.19 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Jul 2008 04:42:50 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Thu, 3 Jul 2008 20:41:59 +0900 Date: Thu, 3 Jul 2008 20:41:58 +0900 To: current@freebsd.org Message-ID: <20080703114158.GE57570@freebsd.weongyo.org> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: Subject: Q: 802.11 vap monitor mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 12:10:15 -0000 During testing a new driver, I got a problem to test a monitor mode at 802.11 vap I'm using. # uname -a FreeBSD kkk 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Wed May 14 11:27:37 KST 2008 root@kkk:/usr/obj/usr/src/sys/GENERIC i386 # ifconfig wlan0 create wlandev upgt0 wlanmode monitor # ifconfig wlan0 up # ifconfig [...] upgt0: flags=108943 metric 0 mtu 2290 ether 00:0f:b5:dd:6f:36 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running wlan0: flags=28943 metric 0 mtu 1500 ether 00:0f:b5:dd:6f:36 inet6 fe80::20f:b5ff:fedd:6f36%wlan0 prefixlen 64 scopeid 0xd media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid "" channel 1 (2412 Mhz 11g) bssid 00:0f:b5:dd:6f:36 country US authmode OPEN privacy OFF txpower 0 scanvalid 60 protmode CTS As seeing, it looks work but the problem is happend when I ran stumbler (src/tools/tools/net80211/stumbler) program. The error message is "ioctl(BIOCSDLT): Invalid argument" that it's emitted to screen when I execute the following command: # ./stumbler wlan0 Are there something I missed? regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 13:49:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3952106567F; Thu, 3 Jul 2008 13:49:34 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from watery.cc.kogakuin.ac.jp (watery.cc.kogakuin.ac.jp [133.80.152.80]) by mx1.freebsd.org (Postfix) with ESMTP id 8B2FE8FC25; Thu, 3 Jul 2008 13:49:34 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) by watery.cc.kogakuin.ac.jp (unknown) with ESMTP id m63DZxRK033411; Thu, 3 Jul 2008 22:35:59 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Thu, 03 Jul 2008 22:34:53 +0900 (JST) Message-Id: <20080703.223453.104068461.nyan@jp.FreeBSD.org> To: ed@80386.nl From: Takahashi Yoshihiro In-Reply-To: <20080702190901.GS14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, freebsd-current@freebsd.org Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 13:49:35 -0000 In article <20080702190901.GS14567@hoeg.nl> Ed Schouten writes: > July 13 2008: > Make uart(4) the default serial port driver, instead of sio(4). > sio(4) has not been ported to the new TTY layer and is very hard > to do so. uart(4) has been proven to be more portable than > sio(4) and already supports the hardware we need. uart(4) does not support PC98 CBus and i8251 devices at all. So I wish that sio(4) is remained. --- TAKAHASHI Yoshihiro From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 14:05:38 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E273D1065673 for ; Thu, 3 Jul 2008 14:05:38 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 9E5D38FC15 for ; Thu, 3 Jul 2008 14:05:38 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id C69B473087; Thu, 3 Jul 2008 16:07:19 +0200 (CEST) Date: Thu, 3 Jul 2008 16:07:19 +0200 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20080703140719.GA72315@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Thu, 03 Jul 2008 14:20:17 +0000 Cc: usb@freebsd.org Subject: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 14:05:39 -0000 There was a discussion back in september about adding support for basic CDC tty devices in umodem.c. This lets you talk to a number of usb devices built around microcontrollers (e.g. Atmel), and puts us on par with Linux and Windows in terms of supporting these devices. Because this simply requires the small patch below to the probe/attach routine, so if there are no objections I plan to add this to the system (CURRENT then RELENG_7 and RELENG_6) in the next few days. > Index: umodem.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v > retrieving revision 1.57 > diff -u -r1.57 umodem.c > --- umodem.c 31 Jan 2005 13:58:10 -0000 1.57 > +++ umodem.c 20 Aug 2006 17:05:34 -0000 > @@ -256,6 +260,15 @@ > id->bInterfaceProtocol == UIPROTO_CDC_AT) > ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > +#if 1 > + if (ret == UMATCH_NONE && > + id->bInterfaceClass == UICLASS_CDC_DATA && > + id->bInterfaceSubClass == UISUBCLASS_DATA && > + id->bInterfaceProtocol == 0x00) > + ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > + return ret; > +#endif > + > if (ret == UMATCH_NONE) > return (ret); cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:06:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D95271065677 for ; Thu, 3 Jul 2008 15:06:33 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6131B8FC20 for ; Thu, 3 Jul 2008 15:06:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m63F6VPk078474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Jul 2008 08:06:31 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <486CEAF7.6040709@freebsd.org> Date: Thu, 03 Jul 2008 08:06:31 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: current@freebsd.org References: <20080703114158.GE57570@freebsd.weongyo.org> In-Reply-To: <20080703114158.GE57570@freebsd.weongyo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: Subject: Re: Q: 802.11 vap monitor mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:06:34 -0000 Weongyo Jeong wrote: > During testing a new driver, I got a problem to test a monitor mode at > 802.11 vap I'm using. > > # uname -a > FreeBSD kkk 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Wed May 14 11:27:37 KST > 2008 root@kkk:/usr/obj/usr/src/sys/GENERIC i386 > # ifconfig wlan0 create wlandev upgt0 wlanmode monitor > # ifconfig wlan0 up > # ifconfig > [...] > upgt0: > flags=108943 > metric 0 mtu 2290 > ether 00:0f:b5:dd:6f:36 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: running > wlan0: > flags=28943 > metric 0 mtu 1500 > ether 00:0f:b5:dd:6f:36 > inet6 fe80::20f:b5ff:fedd:6f36%wlan0 prefixlen 64 scopeid 0xd > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: running > ssid "" channel 1 (2412 Mhz 11g) bssid 00:0f:b5:dd:6f:36 > country US authmode OPEN privacy OFF txpower 0 scanvalid 60 > protmode CTS > > As seeing, it looks work but the problem is happend when I ran stumbler > (src/tools/tools/net80211/stumbler) program. > > The error message is "ioctl(BIOCSDLT): Invalid argument" that it's > emitted to screen when I execute the following command: > # ./stumbler wlan0 > > Are there something I missed? > What DLT is stumbler using? If it's requesting IEEE802_11_RADIO then this will fail as that is not available for the vap, only for the underlying device. This is an open issue that I'm looking for help with--previously an 802.11 device supported 3 DLT's: 802.3, 802.11, and radiotap but now it only supports the first 2. The net80211 layer does not have all the data required to dispatch radiotap headers (only the driver does) so we need to push the information up to net80211 for each rx'd packet (possibly expensive) or provide some net80211-level support for dispatching radiotap data through vap's. Sam From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:07:03 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7A731065691; Thu, 3 Jul 2008 15:07:03 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout5.freenet.de (mout5.freenet.de [IPv6:2001:748:100:40::2:7]) by mx1.freebsd.org (Postfix) with ESMTP id 6E71C8FC25; Thu, 3 Jul 2008 15:07:03 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.25] (helo=15.mx.freenet.de) by mout5.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #19) id 1KEQOj-0003WA-L2; Thu, 03 Jul 2008 17:07:01 +0200 Received: from ma633.m.pppool.de ([89.49.166.51]:57025 helo=peedub.jennejohn.org) by 15.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #12) id 1KEQOj-0003ED-DO; Thu, 03 Jul 2008 17:07:01 +0200 Date: Thu, 3 Jul 2008 17:07:00 +0200 From: Gary Jennejohn To: Luigi Rizzo Message-ID: <20080703170700.3b91b8c6@peedub.jennejohn.org> In-Reply-To: <20080703140719.GA72315@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: usb@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:07:04 -0000 On Thu, 3 Jul 2008 16:07:19 +0200 Luigi Rizzo wrote: > There was a discussion back in september about adding > support for basic CDC tty devices in umodem.c. > This lets you talk to a number of usb devices built around > microcontrollers (e.g. Atmel), and puts us on par with > Linux and Windows in terms of supporting these devices. > > Because this simply requires the small patch below to the > probe/attach routine, so if there are no objections I plan to add > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > few days. > > > Index: umodem.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v > > retrieving revision 1.57 > > diff -u -r1.57 umodem.c > > --- umodem.c 31 Jan 2005 13:58:10 -0000 1.57 > > +++ umodem.c 20 Aug 2006 17:05:34 -0000 > > @@ -256,6 +260,15 @@ > > id->bInterfaceProtocol == UIPROTO_CDC_AT) > > ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > > > +#if 1 > > + if (ret == UMATCH_NONE && > > + id->bInterfaceClass == UICLASS_CDC_DATA && > > + id->bInterfaceSubClass == UISUBCLASS_DATA && > > + id->bInterfaceProtocol == 0x00) > > + ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > + return ret; > > +#endif > > + > > if (ret == UMATCH_NONE) > > return (ret); > Is there any reason to keep the #if 1 ... #endif? And why not just directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than assigning it to ret first? --- Gary Jennejohn (gj@freebsd.org) From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:25:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66549106566C for ; Thu, 3 Jul 2008 15:25:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3A6C98FC22 for ; Thu, 3 Jul 2008 15:25:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m63FNRtv050383; Thu, 3 Jul 2008 08:23:34 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <486CEEEF.8030808@freebsd.org> Date: Thu, 03 Jul 2008 08:23:27 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Holger Kipp References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <486C0928.8050607@yahoo.fr> <20080703085629.GA1590@intserv.int1.b.intern> In-Reply-To: <20080703085629.GA1590@intserv.int1.b.intern> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com, Curtis Penner , Antoine BRUNEL Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:25:07 -0000 Holger Kipp wrote: > > I completely 100% agree. Actually I don't see the need for a new > sysinstall. It does what it needs to do. I have seen the later > RH- and SUSE-Installer, but I don't want them. What's the use of > a graphical installer? One big problem with the current installer: The current keyboard interaction is quite mystifying to new users. I taught a FreeBSD class for a while where I watched every single person stumble just trying to figure out how to select choices in the installer menus. I don't think a graphical installer is necessarily the answer to this. Simply obeying long-established conventions for keyboard usage (ENTER selects the thing under the cursor, for instance, instead of having to TAB to the "OK" button first) would go a long ways. Tim From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:48:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4710106564A for ; Thu, 3 Jul 2008 15:48:48 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 982DC8FC21 for ; Thu, 3 Jul 2008 15:48:48 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so765028wfg.7 for ; Thu, 03 Jul 2008 08:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=WovlCpOy1iQISe4v4fufez5saAzvki3fW0hGG6OiPVQ=; b=nKPFhAks0WAvsUvG1xxZioz/z3iXRXoFpQNp4/vD6mWu4VFAiHcGtzAo76aGG43RSI CLEMLZA3fjKEDsx5XydOcTA81XATfzMmTSG/lXPeeKLt0x/DdqfgNzmzylljPC3e5vTF QYxq16J/CsakgzbAjEiU9TWDB0oJrNqfIwxvg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=k5ZopQwc09hPAT9NE9Dm/Jvlh1KsKlQBUxDx4g6TQ+ACKKFPKgTqxJhTCq7NVHXrHg v4/u7Kj2SKf/ucuzbE5SAJg1LZPHwn1umxk9D/x9NHX5lTlrP5c79cQhjZd+bLoD//Y8 ZhUcYp49isPcyDiUHtBCLjGXKW2JZwEU+brOI= Received: by 10.143.168.4 with SMTP id v4mr28220wfo.39.1215098395460; Thu, 03 Jul 2008 08:19:55 -0700 (PDT) Received: by 10.142.231.8 with HTTP; Thu, 3 Jul 2008 08:19:55 -0700 (PDT) Message-ID: <3a142e750807030819u522cf2e0h327d044283c1223d@mail.gmail.com> Date: Thu, 3 Jul 2008 17:19:55 +0200 From: "Paul B. Mahol" To: current@freebsd.org In-Reply-To: <20080703114158.GE57570@freebsd.weongyo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080703114158.GE57570@freebsd.weongyo.org> Cc: Subject: Re: Q: 802.11 vap monitor mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:48:48 -0000 I belive that code is currently broken (last change in 2006). On 7/3/08, Weongyo Jeong wrote: > During testing a new driver, I got a problem to test a monitor mode at > 802.11 vap I'm using. > > # uname -a > FreeBSD kkk 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Wed May 14 11:27:37 KST > 2008 root@kkk:/usr/obj/usr/src/sys/GENERIC i386 > # ifconfig wlan0 create wlandev upgt0 wlanmode monitor > # ifconfig wlan0 up > # ifconfig > [...] > upgt0: > flags=108943 > metric 0 mtu 2290 > ether 00:0f:b5:dd:6f:36 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: running > wlan0: > flags=28943 > metric 0 mtu 1500 > ether 00:0f:b5:dd:6f:36 > inet6 fe80::20f:b5ff:fedd:6f36%wlan0 prefixlen 64 scopeid 0xd > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: running > ssid "" channel 1 (2412 Mhz 11g) bssid 00:0f:b5:dd:6f:36 > country US authmode OPEN privacy OFF txpower 0 scanvalid 60 > protmode CTS > > As seeing, it looks work but the problem is happend when I ran stumbler > (src/tools/tools/net80211/stumbler) program. > > The error message is "ioctl(BIOCSDLT): Invalid argument" that it's > emitted to screen when I execute the following command: > # ./stumbler wlan0 > > Are there something I missed? > > regards, > Weongyo Jeong > > _______________________________________________ > 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" > From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:50:18 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF79A1065685 for ; Thu, 3 Jul 2008 15:50:18 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.freebsd.org (Postfix) with ESMTP id 39C418FC21 for ; Thu, 3 Jul 2008 15:50:18 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 76353 invoked by uid 89); 3 Jul 2008 15:23:36 -0000 Received: by simscan 1.1.0 ppid: 76332, pid: 76344, t: 2.8511s scanners: attach: 1.1.0 clamav: 0.88.7/m:44/d:4673 spam: 3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from unknown (HELO ?212.71.117.70?) (rainer@ultra-secure.de@212.71.117.70) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 Jul 2008 15:23:33 -0000 Message-ID: <486CEEF1.9040702@ultra-secure.de> Date: Thu, 03 Jul 2008 17:23:29 +0200 From: Rainer Duffner User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.8.1.14) Gecko/20080421 SUSE/2.0.0.14-0.1 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Lothar Braun References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> In-Reply-To: <486C8700.5020100@lobraun.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, rwatson@FreeBSD.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:50:19 -0000 Lothar Braun schrieb: > Robert Watson wrote: >> My primary concern about some of these replacement installer projects >> is that they've placed a strong focus on making them graphical -- I >> actually couldn't care less about GUIs (and I think they actually >> hurt my configurations, since I use serial consoles a lot), but what >> I do want is a very tight and efficient install process, which I feel >> sysinstall does badly on (not just for the reasons you specify). > > Hmm, how should a tight and efficient installation process look like > in your opinion? And what are the other points that are bad in > systinstall? > Mass-installation via PXE-booting is a mess (how can you have to pack the install.cfg file into the mfsroot diskimage???). Take a look at kickstart+cobbler from RedHat for a system with some thought behind this process. I don't care the least about GUI or not GUI. I'd like to to able to deploy them as seamlessly as the CentOS/RHEL boxes. Rainer From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 16:18:22 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48EDB106568A; Thu, 3 Jul 2008 16:18:22 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from mail.lxnt.info (mail.lxnt.info [77.95.131.23]) by mx1.freebsd.org (Postfix) with ESMTP id 02C708FC24; Thu, 3 Jul 2008 16:18:21 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from [195.34.193.156] (helo=[192.168.254.231]) by mail.lxnt.info with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KEQrx-0006wu-PC; Thu, 03 Jul 2008 19:37:13 +0400 Message-ID: <486CF22F.3080901@lxnt.info> Date: Thu, 03 Jul 2008 19:37:19 +0400 From: Alexander Sabourenkov User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> In-Reply-To: <20080703170700.3b91b8c6@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: usb@freebsd.org, Luigi Rizzo , current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 16:18:22 -0000 Gary Jennejohn wrote: > On Thu, 3 Jul 2008 16:07:19 +0200 > Luigi Rizzo wrote: > [...] >>> +#if 1 >>> + if (ret == UMATCH_NONE && >>> + id->bInterfaceClass == UICLASS_CDC_DATA && >>> + id->bInterfaceSubClass == UISUBCLASS_DATA && >>> + id->bInterfaceProtocol == 0x00) >>> + ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; >>> + return ret; >>> +#endif >>> + >>> if (ret == UMATCH_NONE) >>> return (ret); > > Is there any reason to keep the #if 1 ... #endif? And why not just > directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than > assigning it to ret first? This patch also makes all statements below ''return ret;'' unreachable. I think it should be rewritten. -- ./lxnt From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 15:24:08 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B264F106566C; Thu, 3 Jul 2008 15:24:08 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5828FC18; Thu, 3 Jul 2008 15:24:08 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 4C6FA7308E; Thu, 3 Jul 2008 17:25:51 +0200 (CEST) Date: Thu, 3 Jul 2008 17:25:51 +0200 From: Luigi Rizzo To: Gary Jennejohn Message-ID: <20080703152551.GA73103@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080703170700.3b91b8c6@peedub.jennejohn.org> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Thu, 03 Jul 2008 16:21:45 +0000 Cc: usb@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 15:24:08 -0000 On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > On Thu, 3 Jul 2008 16:07:19 +0200 > Luigi Rizzo wrote: > > > There was a discussion back in september about adding > > support for basic CDC tty devices in umodem.c. > > This lets you talk to a number of usb devices built around > > microcontrollers (e.g. Atmel), and puts us on par with > > Linux and Windows in terms of supporting these devices. > > > > Because this simply requires the small patch below to the > > probe/attach routine, so if there are no objections I plan to add > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > few days. > > > > > Index: umodem.c > > > =================================================================== > > > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v > > > retrieving revision 1.57 > > > diff -u -r1.57 umodem.c > > > --- umodem.c 31 Jan 2005 13:58:10 -0000 1.57 > > > +++ umodem.c 20 Aug 2006 17:05:34 -0000 > > > @@ -256,6 +260,15 @@ > > > id->bInterfaceProtocol == UIPROTO_CDC_AT) > > > ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > > > > > +#if 1 > > > + if (ret == UMATCH_NONE && > > > + id->bInterfaceClass == UICLASS_CDC_DATA && > > > + id->bInterfaceSubClass == UISUBCLASS_DATA && > > > + id->bInterfaceProtocol == 0x00) > > > + ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > > + return ret; > > > +#endif > > > + > > > if (ret == UMATCH_NONE) > > > return (ret); > > > > Is there any reason to keep the #if 1 ... #endif? And why not just > directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than > assigning it to ret first? in fact there are also missing braces that need to be added -- as is, the code after the #endif is completely disabled. thanks for the comment, but don't worry, the commit will be done the right way. cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 16:56:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB598106567D; Thu, 3 Jul 2008 16:56:46 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from smtp.cs.uni-tuebingen.de (u-173-c156.cs.uni-tuebingen.de [134.2.173.156]) by mx1.freebsd.org (Postfix) with ESMTP id 60E788FC1C; Thu, 3 Jul 2008 16:56:46 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from u-172-c158.cs.uni-tuebingen.de ([134.2.172.158]) by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1KES6u-0000QQ-Lj; Thu, 03 Jul 2008 18:56:44 +0200 Message-ID: <486D04CE.6080101@lobraun.de> Date: Thu, 03 Jul 2008 18:56:46 +0200 From: Lothar Braun User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Robert Watson References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> In-Reply-To: <20080703092511.T69986@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 16:56:46 -0000 Robert Watson wrote: > On Thu, 3 Jul 2008, Lothar Braun wrote: > >> Robert Watson wrote: >> >>> My primary concern about some of these replacement installer projects >>> is that they've placed a strong focus on making them graphical -- I >>> actually couldn't care less about GUIs (and I think they actually >>> hurt my configurations, since I use serial consoles a lot), but what >>> I do want is a very tight and efficient install process, which I feel >>> sysinstall does badly on (not just for the reasons you specify). >> >> Hmm, how should a tight and efficient installation process look like >> in your opinion? And what are the other points that are bad in >> systinstall? > > For me, it's really about minimizing the time to get to a generic > install from a CD or DVD. Most of the time, I don't do a lot of > customization during the install -- I configure machines using DHCP, I > add most packages later, and I tend to use default disk layouts since my > servers don't multi-boot and the defaults currently seem "reasonable". > > I don't like being asked many more questions than whether or not to > enable sshd, and what to set the root password to. This means that I > find our current distributions menu a bit inefficient (I don't want > sub-menus, I just want checkboxes), and that the inconsistency in the > handling of the space/enter/tab/cursor keys across different libdialog > interfaces in the install is awkward. The current generic and express > installs seem to capture a lot of my desire, in that I can get a box > installed in <5m including actual time to write out the file systems, > which is great. I really don't want to lose this with a new installer :-). What about having two utilities for the installation process? Something like a very small (non-gui/non-X) version of "sysinstall" that just installs a base system and only has the functionality to - partition/label a disk - configure the network (if needed for installation) - install the base system (or parts of it) - install a boot manager and a second utility "sysconf" that provides the other stuff like post installation system configuration (sshd, mouse), installing packages, etc. The second utility could have an X-based GUI without disturbing the installation process of serial console users or people that don't like X on their machines. Would that be a good idea? Best regards, Lothar From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 17:23:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82A72106566C for ; Thu, 3 Jul 2008 17:23:42 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu (math.missouri.edu [128.206.184.200]) by mx1.freebsd.org (Postfix) with ESMTP id 4EBFB8FC13 for ; Thu, 3 Jul 2008 17:23:42 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from [128.206.184.213] (cauchy.math.missouri.edu [128.206.184.213]) by math.missouri.edu (8.13.1/8.13.1) with ESMTP id m63HNfuD057174; Thu, 3 Jul 2008 12:23:41 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <486D0AE9.5010906@math.missouri.edu> Date: Thu, 03 Jul 2008 12:22:49 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080701 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Lothar Braun References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486D04CE.6080101@lobraun.de> In-Reply-To: <486D04CE.6080101@lobraun.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88/7630/Thu Jul 3 11:29:37 2008 on math.missouri.edu X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Robert Watson Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 17:23:42 -0000 Lothar Braun wrote: > What about having two utilities for the installation process? Something > like a very small (non-gui/non-X) version of "sysinstall" that just > installs a base system and only has the functionality to > > - partition/label a disk > - configure the network (if needed for installation) > - install the base system (or parts of it) > - install a boot manager > > and a second utility "sysconf" that provides the other stuff like post > installation system configuration (sshd, mouse), installing packages, > etc. The second utility could have an X-based GUI without disturbing the > installation process of serial console users or people that don't like X > on their machines. > > Would that be a good idea? Why not leave "sysconf" as a curses based interface? To my mind, the difference between X-based and curses is cosmetic. (Plus one of "sysconf"s duties will be to install X, so it would be a bit self-referential.) Next, it seemed to me that the OP's main complaint was that he had to change the CD's about 40 times when installing packages. Why not just fix that? From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 18:36:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D64041065678 for ; Thu, 3 Jul 2008 18:36:39 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id 7C50A8FC14 for ; Thu, 3 Jul 2008 18:36:39 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Jul 2008 14:14:32 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 1C2B111705; Thu, 3 Jul 2008 14:14:32 -0400 (EDT) Date: Thu, 3 Jul 2008 14:14:31 -0400 From: Ed Maste To: freebsd-current@freebsd.org Message-ID: <20080703181431.GA10858@sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 03 Jul 2008 18:14:32.0311 (UTC) FILETIME=[A4382870:01C8DD38] Subject: head panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 18:36:39 -0000 I haven't looked into this yet, but just got the following panic on boot from a GENERIC kernel built from svn head ~ 1 hour ago: Loading configuration files. panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184 cpuid = 0 KDB: enter: panic [thread pid 35 tid 100069 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> db> bt Tracing pid 35 tid 100069 td 0xc7119230 kdb_enter(c0b46154,c0b46154,c0b44be1,e93899a4,0,...) at kdb_enter+0x3a panic(c0b44be1,c0b64e7b,c0b3daac,b8,e93899e0,...) at panic+0x12c _mtx_assert(c0c89570,0,c0b3daac,b8,2000,...) at _mtx_assert+0x127 g_dev_open(c707ad00,1,2000,c7119230,4,...) at g_dev_open+0xb4 devfs_open(e9389acc,c7119230,e9389ba8,0,e9389af4,...) at devfs_open+0xdf VOP_OPEN_APV(c0c17580,e9389acc,c7119230,e9389a54,c710a860,...) at VOP_OPEN_APV+0xa5 vn_open_cred(e9389ba8,e9389c5c,9cd,c648b800,c70d7818,...) at vn_open_cred+0x429 vn_open(e9389ba8,e9389c5c,9cd,c70d7818,0,...) at vn_open+0x33 kern_openat(c7119230,ffffff9c,bfbfef70,0,1,...) at kern_openat+0x106 kern_open(c7119230,bfbfef70,0,0,80489df,...) at kern_open+0x35 open(c7119230,e9389cf8,c,c7119230,c0c1aad8,...) at open+0x30 syscall(e9389d38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (5, FreeBSD ELF32, open), eip = 0x28159cb3, esp = 0xbfbfee2c, ebp = 0xbfbfee88 --- - Ed From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 18:53:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57821106564A; Thu, 3 Jul 2008 18:53:32 +0000 (UTC) (envelope-from tim@clewlow.org) Received: from clewlow.org (clewlow.org [210.215.149.194]) by mx1.freebsd.org (Postfix) with ESMTP id AE7B78FC13; Thu, 3 Jul 2008 18:53:31 +0000 (UTC) (envelope-from tim@clewlow.org) Received: from 192.168.1.100 (localhost [127.0.0.1]) by clewlow.org (Postfix) with ESMTP id 5F3081C0845; Fri, 4 Jul 2008 04:37:28 +1000 (EST) Received: from 192.168.1.10 (SquirrelMail authenticated user tim) by 192.168.1.100 with HTTP; Fri, 4 Jul 2008 04:37:28 +1000 (EST) Message-ID: <52853.192.168.1.10.1215110248.squirrel@192.168.1.100> In-Reply-To: <486D04CE.6080101@lobraun.de> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486D04CE.6080101@lobraun.de> Date: Fri, 4 Jul 2008 04:37:28 +1000 (EST) From: "Tim Clewlow" To: "Lothar Braun" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Robert Watson Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 18:53:32 -0000 > Robert Watson wrote: >> On Thu, 3 Jul 2008, Lothar Braun wrote: >> >>> Robert Watson wrote: >>> >>>> My primary concern about some of these replacement installer >>>> projects >>>> is that they've placed a strong focus on making them graphical >>>> -- I >>>> actually couldn't care less about GUIs (and I think they >>>> actually >>>> hurt my configurations, since I use serial consoles a lot), but >>>> what >>>> I do want is a very tight and efficient install process, which I >>>> feel >>>> sysinstall does badly on (not just for the reasons you specify). >>> >>> Hmm, how should a tight and efficient installation process look >>> like >>> in your opinion? And what are the other points that are bad in >>> systinstall? >> >> For me, it's really about minimizing the time to get to a generic >> install from a CD or DVD. Most of the time, I don't do a lot of >> customization during the install -- I configure machines using >> DHCP, I >> add most packages later, and I tend to use default disk layouts >> since my >> servers don't multi-boot and the defaults currently seem >> "reasonable". >> >> I don't like being asked many more questions than whether or not >> to >> enable sshd, and what to set the root password to. This means >> that I >> find our current distributions menu a bit inefficient (I don't >> want >> sub-menus, I just want checkboxes), and that the inconsistency in >> the >> handling of the space/enter/tab/cursor keys across different >> libdialog >> interfaces in the install is awkward. The current generic and >> express >> installs seem to capture a lot of my desire, in that I can get a >> box >> installed in <5m including actual time to write out the file >> systems, >> which is great. I really don't want to lose this with a new >> installer :-). > > What about having two utilities for the installation process? > Something > like a very small (non-gui/non-X) version of "sysinstall" that just > installs a base system and only has the functionality to > > - partition/label a disk > - configure the network (if needed for installation) > - install the base system (or parts of it) > - install a boot manager > > and a second utility "sysconf" that provides the other stuff like > post > installation system configuration (sshd, mouse), installing > packages, > etc. The second utility could have an X-based GUI without disturbing > the > installation process of serial console users or people that don't > like X > on their machines. > > Would that be a good idea? > > Best regards, > Lothar I understand the desire to have an automated installer to make things real easy for first time installation for new users. But many people, including myself, will want to retain the current ability to specify exactly what we want as well. So, why not have a single menu at the start with 2 options: 1 - automatic desktop install (new user) 2 - traditional installer (veteran user) Perhaps the automatic installer can just use whatever disk space it finds (with suitable warnings) and attempt to install everything, ie equivalent of choosing All at the 'select distributions' stage. Maybe even do DHCP for net config. This would give a first time user a working system with a nice shiny X to make them feel good about choosing FreeBSD. Yes, I know they could just go to pcbsd, but I would prefer to have a new user at least attempt to learn proper sysadmin skills on vanilla FreeBSD. And if a new user gives up just because the installer is too confusing (especially the partitioner - it is wonderfully powerful, but it does take a bit of getting used to) then I think that is a shame. My cents. Tim. This email has been checked for viruses. It has sufficient. From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 18:58:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85AE2106567B for ; Thu, 3 Jul 2008 18:58:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id DE4988FC1B for ; Thu, 3 Jul 2008 18:58:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63IwYDZ044067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jul 2008 21:58:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63IwY3a056838; Thu, 3 Jul 2008 21:58:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m63IwX5V056837; Thu, 3 Jul 2008 21:58:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 3 Jul 2008 21:58:33 +0300 From: Kostik Belousov To: Ed Maste Message-ID: <20080703185833.GQ17123@deviant.kiev.zoral.com.ua> References: <20080703181431.GA10858@sandvine.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Tm3avfvRG8umVcF7" Content-Disposition: inline In-Reply-To: <20080703181431.GA10858@sandvine.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: head panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 18:58:48 -0000 --Tm3avfvRG8umVcF7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 03, 2008 at 02:14:31PM -0400, Ed Maste wrote: > I haven't looked into this yet, but just got the following panic on boot > from a GENERIC kernel built from svn head ~ 1 hour ago: >=20 > Loading configuration files. > panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:1= 84 > cpuid =3D 0 > KDB: enter: panic > [thread pid 35 tid 100069 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> >=20 > db> bt > Tracing pid 35 tid 100069 td 0xc7119230 > kdb_enter(c0b46154,c0b46154,c0b44be1,e93899a4,0,...) at kdb_enter+0x3a > panic(c0b44be1,c0b64e7b,c0b3daac,b8,e93899e0,...) at panic+0x12c > _mtx_assert(c0c89570,0,c0b3daac,b8,2000,...) at _mtx_assert+0x127 > g_dev_open(c707ad00,1,2000,c7119230,4,...) at g_dev_open+0xb4 > devfs_open(e9389acc,c7119230,e9389ba8,0,e9389af4,...) at devfs_open+0xdf > VOP_OPEN_APV(c0c17580,e9389acc,c7119230,e9389a54,c710a860,...) at VOP_OPE= N_APV+0xa5 > vn_open_cred(e9389ba8,e9389c5c,9cd,c648b800,c70d7818,...) at vn_open_cred= +0x429 > vn_open(e9389ba8,e9389c5c,9cd,c70d7818,0,...) at vn_open+0x33 > kern_openat(c7119230,ffffff9c,bfbfef70,0,1,...) at kern_openat+0x106 > kern_open(c7119230,bfbfef70,0,0,80489df,...) at kern_open+0x35 > open(c7119230,e9389cf8,c,c7119230,c0c1aad8,...) at open+0x30 > syscall(e9389d38) at syscall+0x2a3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (5, FreeBSD ELF32, open), eip =3D 0x28159cb3, esp =3D 0xbfbfe= e2c, ebp =3D 0xbfbfee88 --- Do you have sysctl debug.mpsafevfs=3D0 ? I see no other possibility for this to happen. If yes, the panic is a consequence of the r178834. --Tm3avfvRG8umVcF7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhtIVkACgkQC3+MBN1Mb4jwKgCfXzsOehS96Uc5JLqK4f/rNkhp cEIAoN5SqZ5EChoxiXTmuWAPCPa5VfS+ =BmS/ -----END PGP SIGNATURE----- --Tm3avfvRG8umVcF7-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:16:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A080110656C9 for ; Thu, 3 Jul 2008 19:16:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id AFFC88FC22 for ; Thu, 3 Jul 2008 19:16:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 19283 invoked by uid 399); 3 Jul 2008 19:16:11 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 3 Jul 2008 19:16:11 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <486D2579.1080400@FreeBSD.org> Date: Thu, 03 Jul 2008 12:16:09 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <486C0928.8050607@yahoo.fr> <20080703085629.GA1590@intserv.int1.b.intern> <486CEEEF.8030808@freebsd.org> In-Reply-To: <486CEEEF.8030808@freebsd.org> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:16:15 -0000 Tim Kientzle wrote: > I don't think a graphical installer is necessarily > the answer to this. Simply obeying long-established > conventions for keyboard usage (ENTER selects the > thing under the cursor, for instance, instead of > having to TAB to the "OK" button first) would go > a long ways. The version of dialog we have in the system is prehistoric. The newer version is a lot better in the POLA department, and $SOMEONE was working on an update, but I don't know what happened to that effort. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:17:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A400106567D for ; Thu, 3 Jul 2008 19:17:50 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id C224E8FC1B for ; Thu, 3 Jul 2008 19:17:49 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Jul 2008 15:16:48 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 842B611610; Thu, 3 Jul 2008 15:16:48 -0400 (EDT) Date: Thu, 3 Jul 2008 15:16:48 -0400 From: Ed Maste To: Kostik Belousov Message-ID: <20080703191648.GA39891@sandvine.com> References: <20080703181431.GA10858@sandvine.com> <20080703185833.GQ17123@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080703185833.GQ17123@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 03 Jul 2008 19:16:48.0715 (UTC) FILETIME=[574A29B0:01C8DD41] Cc: freebsd-current@freebsd.org Subject: remove debug.mpsafevfs tunable? (was Re: head panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:17:50 -0000 On Thu, Jul 03, 2008 at 09:58:33PM +0300, Kostik Belousov wrote: > On Thu, Jul 03, 2008 at 02:14:31PM -0400, Ed Maste wrote: > > > > Loading configuration files. > > panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 35 tid 100069 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > db> > > [...] > > Do you have sysctl debug.mpsafevfs=0 ? It turns out that due to an artifact of my lab environment, the tunable debug.mpsafevfs=0 was being set -- thanks for the suggestion! Since it seems the tunable doesn't work properly anymore, and probably isn't at needed at all, should we just remove it? -Ed From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:23:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AB31106566C for ; Thu, 3 Jul 2008 19:23:39 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id CEAC78FC1F for ; Thu, 3 Jul 2008 19:23:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 29835 invoked by uid 399); 3 Jul 2008 19:23:38 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 3 Jul 2008 19:23:38 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <486D2738.7020709@FreeBSD.org> Date: Thu, 03 Jul 2008 12:23:36 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> In-Reply-To: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:23:39 -0000 Mike Makonnen has some very interesting ideas on this topic: http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081400.html FWIW, I think that there are 3 basic requirements for a new installer: 1. It should be library-based and therefore be capable of supporting at least a few different UIs (see above). 2. At least one of those UIs should be functional over a standard serial console. 3. It should be scriptable. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:27:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E85A1065671; Thu, 3 Jul 2008 19:27:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id C6AF58FC1A; Thu, 3 Jul 2008 19:27:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63JRdl6045095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jul 2008 22:27:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63JRcRK058902; Thu, 3 Jul 2008 22:27:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m63JRcvP058901; Thu, 3 Jul 2008 22:27:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 3 Jul 2008 22:27:38 +0300 From: Kostik Belousov To: Ed Maste Message-ID: <20080703192738.GR17123@deviant.kiev.zoral.com.ua> References: <20080703181431.GA10858@sandvine.com> <20080703185833.GQ17123@deviant.kiev.zoral.com.ua> <20080703191648.GA39891@sandvine.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="c8bPn4FL4u+7TADa" Content-Disposition: inline In-Reply-To: <20080703191648.GA39891@sandvine.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: remove debug.mpsafevfs tunable? (was Re: head panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:27:43 -0000 --c8bPn4FL4u+7TADa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 03, 2008 at 03:16:48PM -0400, Ed Maste wrote: > On Thu, Jul 03, 2008 at 09:58:33PM +0300, Kostik Belousov wrote: >=20 > > On Thu, Jul 03, 2008 at 02:14:31PM -0400, Ed Maste wrote: > > > > > > Loading configuration files. > > > panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev= .c:184 > > > cpuid =3D 0 > > > KDB: enter: panic > > > [thread pid 35 tid 100069 ] > > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > > db> > > > [...] > > > > Do you have sysctl debug.mpsafevfs=3D0 ? >=20 > It turns out that due to an artifact of my lab environment, the tunable > debug.mpsafevfs=3D0 was being set -- thanks for the suggestion! >=20 > Since it seems the tunable doesn't work properly anymore, and probably > isn't at needed at all, should we just remove it? I would not object against it. --c8bPn4FL4u+7TADa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhtKCoACgkQC3+MBN1Mb4hUzACgz+79b1H7LfEQpMepFdBD5oCc CO4AnAxaK/4tbXImHmNS7obYIgjmh+DM =J36i -----END PGP SIGNATURE----- --c8bPn4FL4u+7TADa-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:34:37 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AC461065688 for ; Thu, 3 Jul 2008 19:34:37 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.freebsd.org (Postfix) with ESMTP id CC5048FC1B for ; Thu, 3 Jul 2008 19:34:36 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail18.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m63JY7mu006019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jul 2008 05:34:09 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m63JY77W031093; Fri, 4 Jul 2008 05:34:07 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m63JY6ow031092; Fri, 4 Jul 2008 05:34:07 +1000 (EST) (envelope-from peter) Date: Fri, 4 Jul 2008 05:34:06 +1000 From: Peter Jeremy To: Ed Schouten Message-ID: <20080703193406.GS29380@server.vk2pj.dyndns.org> References: <20080702190901.GS14567@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5L6AZ1aJH5mDrqCQ" Content-Disposition: inline In-Reply-To: <20080702190901.GS14567@hoeg.nl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Arch , FreeBSD Current Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:34:37 -0000 --5L6AZ1aJH5mDrqCQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jul-02 21:09:01 +0200, Ed Schouten wrote: >+ The new pseudo-terminal driver is capable of garbage collecting unused > PTY's. Because PTY's are never recycled, they are a lot more robust > (they are always initialized the same, no need to revoke() them before > usage, etc). When you say 'never recycled', does this include the PTY number? If so, long running busy systems are going to get some fairly large numbers. When will the PTY number wrap? What is the impact on tools (eg ps, w) that assume they can represent a PTY in a small number of digits? What about utmp(5) which uses PTY number in the index? >- Not all drivers have been ported to the new TTY layer yet. These > drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), > uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), > umodem(4), dcons(4). > >Even though drivers are very important to have, I am convinced we can >get these working not long after the code as been integrated. ... > If you really care about one of these drivers, >please port it to the new TTY layer as soon as possible! IMHO, this is not a reasonable approach: "Hi everyone. I'm going to break infrastructure that a whole bunch of drivers depend on. If you don't fix your drivers in the next few weeks then I'll disconnect them". Either you need to provide compatibility shims (possibly temporary and not MPSAFE) or you need to be far more pro-active in assisting with porting existing consumers of the TTY layer. >TTY layer into our kernel. I would really appreciate it if I could get >this code in before the end of the summer break, because I've got heaps >of spare time to fix any problems then. That's all very nice but what about the maintainers of all the other drivers that you are impacting? > sio(4) has not been ported to the new TTY layer and is very hard > to do so. This is the only mention of how much effort is involved in porting a driver to use the MPSAFE TTY layer and "very hard" is not a good start. I can't quickly find any documentation on how to go about porting an existing driver - definitely there are no section 9 man pages describing the new API in your patchset. IMHO, if you can't commit fixed drivers along with the MPSAFE TTY layer, a more reasonable schedule is to replace the existing TTY layer with an MPSAFE TTY layer that includes compatibility shims. If the shims make things non-MPSAFE (which is likely) then warn that they will be going away in (say) six months. This gives developers a more reasonable timeframe in which to update, as well as working drivers whilst they adapt them. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --5L6AZ1aJH5mDrqCQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhtKa4ACgkQ/opHv/APuIcUoQCgvbCXHvJ4XbBUfRb9scImg/D7 dmMAoIHMk6BMCiTO5ZVyVuLFEIZpEhFX =2AQg -----END PGP SIGNATURE----- --5L6AZ1aJH5mDrqCQ-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:39:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC7DD106566C; Thu, 3 Jul 2008 19:39:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4DB8FC0A; Thu, 3 Jul 2008 19:39:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63JcuZ9045406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jul 2008 22:38:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m63JcusC059280; Thu, 3 Jul 2008 22:38:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m63JcuP7059279; Thu, 3 Jul 2008 22:38:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 3 Jul 2008 22:38:56 +0300 From: Kostik Belousov To: Doug Barton Message-ID: <20080703193856.GS17123@deviant.kiev.zoral.com.ua> References: <486BFFE5.1010808@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m3NGSFsSaj96nZIx" Content-Disposition: inline In-Reply-To: <486BFFE5.1010808@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: Panic using rsync to msdosfs filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:39:01 -0000 --m3NGSFsSaj96nZIx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 02, 2008 at 03:23:33PM -0700, Doug Barton wrote: > I have a western digital passport USB hard drive that I use for=20 > backups. It's always worked fine in FreeBSD and Windows doing straight=20 > copies. Today I tried to get fancy and use rsync and it blew up on me. >=20 > It is a large disk (160G) and I use the following options in fstab: > /dev/da0s1 /mnt/wd msdosfs rw,noauto,-olarge,-m775 0 0 >=20 > Using the following command line for rsync I get a panic as soon as I=20 > hit return: rsync -vv --backup -u -rlt source/ destination/ >=20 > I'm using -current as of r180191. Here is the stack trace: > Unread portion of the kernel message buffer: > panic: stack overflow detected; backtrace may be corrupted > cpuid =3D 1 > Uptime: 1h52m1s > Physical memory: 2029 MB > Dumping 133 MB: 118 102 86 70 54 38 22 6 >=20 > Reading symbols from /boot/modules/nvidia.ko...Reading symbols from=20 > /boot/modules/nvidia.ko.symbols...done. > done. > Loaded symbols for /boot/modules/nvidia.ko > Reading symbols from /boot/kernel/acpi.ko...Reading symbols from=20 > /boot/kernel/acpi.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/acpi.ko > Reading symbols from /boot/kernel/if_bge.ko...Reading symbols from=20 > /boot/kernel/if_bge.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/if_bge.ko > Reading symbols from /boot/kernel/linux.ko...Reading symbols from=20 > /boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > Reading symbols from /boot/kernel/msdosfs.ko...Reading symbols from=20 > /boot/kernel/msdosfs.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/msdosfs.ko > #0 doadump () at pcpu.h:196 > 196 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); > (kgdb) where > #0 doadump () at pcpu.h:196 > #1 0xc057a9ce in boot (howto=3D260) > at /usr/local/src/sys/kern/kern_shutdown.c:418 > #2 0xc057ac93 in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/local/src/sys/kern/kern_shutdown.c:572 > #3 0xc059c5b2 in __stack_chk_fail () > at /usr/local/src/sys/kern/stack_protector.c:17 > #4 0xc652384a in msdosfs_rename (ap=3D0xc644aca4) > at=20 > /usr/local/src/sys/modules/msdosfs/../../fs/msdosfs/msdosfs_vnops.c:1286 > #5 0xc07b4df5 in VOP_RENAME_APV (vop=3D0xc6525cc0, a=3D0xe9e59c1c) > at vnode_if.c:1184 > #6 0xc0605619 in kern_renameat (td=3D0xc58f1d20, oldfd=3D-100, > old=3D0xbfbfc4a0
, newfd=3D-100, > new=3D0xbfbfcca0
,=20 > pathseg=3DUIO_USERSPACE) > at vnode_if.h:622 > #7 0xc06057a6 in kern_rename (td=3D0xc58f1d20, > from=3D0xbfbfc4a0
, > to=3D0xbfbfcca0
,=20 > pathseg=3DUIO_USERSPACE) > at /usr/local/src/sys/kern/vfs_syscalls.c:3526 > #8 0xc06057d9 in rename (td=3D0xc58f1d20, uap=3D0xe9e59cf8) > at /usr/local/src/sys/kern/vfs_syscalls.c:3503 > #9 0xc07a6283 in syscall (frame=3D0xe9e59d38) > at /usr/local/src/sys/i386/i386/trap.c:1081 > #10 0xc078bb80 in Xint0x80_syscall () > at /usr/local/src/sys/i386/i386/exception.s:261 > #11 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) >=20 >=20 > Let me know what I can do to help. Looks like this is the first casuality of the -fstack-protector. Try this: diff --git a/sys/fs/msdosfs/msdosfs_vnops.c b/sys/fs/msdosfs/msdosfs_vnops.c index 8a1484f..fe673e0 100644 --- a/sys/fs/msdosfs/msdosfs_vnops.c +++ b/sys/fs/msdosfs/msdosfs_vnops.c @@ -982,7 +982,7 @@ msdosfs_rename(ap) struct componentname *tcnp =3D ap->a_tcnp; struct componentname *fcnp =3D ap->a_fcnp; struct denode *ip, *xp, *dp, *zp; - u_char toname[11], oldname[11]; + u_char toname[12], oldname[11]; u_long from_diroffset, to_diroffset; u_char to_count; int doingdirectory =3D 0, newparent =3D 0; --m3NGSFsSaj96nZIx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhtKs8ACgkQC3+MBN1Mb4jiqwCg3PqZVb05N3zDt8nkCOx0BcuY j0AAoLYAFZEYyRWCZ4VVwX0zSfcLVq5x =d1D1 -----END PGP SIGNATURE----- --m3NGSFsSaj96nZIx-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 19:52:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EFAE1065671; Thu, 3 Jul 2008 19:52:51 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id EF5408FC17; Thu, 3 Jul 2008 19:52:50 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1KEUCi-0002Ch-0t; Thu, 03 Jul 2008 21:10:52 +0200 Message-ID: <486D2438.2060006@gwdg.de> Date: Thu, 03 Jul 2008 21:10:48 +0200 From: Rainer Hurling User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <486BFFE5.1010808@FreeBSD.org> In-Reply-To: <486BFFE5.1010808@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Doug Barton Subject: Re: Panic using rsync to msdosfs filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 19:52:51 -0000 It seems, that I get the same panic ('stack overflow detected') when *moving* a file on a msdos file system (fat32) like this: mv file_old file_new On 03.07.2008 00:23 (UTC+1), Doug Barton wrote: > I have a western digital passport USB hard drive that I use for backups. > It's always worked fine in FreeBSD and Windows doing straight copies. > Today I tried to get fancy and use rsync and it blew up on me. > > It is a large disk (160G) and I use the following options in fstab: > /dev/da0s1 /mnt/wd msdosfs rw,noauto,-olarge,-m775 0 0 My drive is connected and mounted as following: ad6: 476940MB at ata3-master SATA300 /dev/ad6s5 on /WINDAT (msdosfs, local) I observe this behaviour on different systems, but only with CURRENT newer than June 24. Also, let me know, if I can help. Thanks in advance, Rainer Hurling > Using the following command line for rsync I get a panic as soon as I > hit return: rsync -vv --backup -u -rlt source/ destination/ > > I'm using -current as of r180191. Here is the stack trace: > Unread portion of the kernel message buffer: > panic: stack overflow detected; backtrace may be corrupted > cpuid = 1 > Uptime: 1h52m1s > Physical memory: 2029 MB > Dumping 133 MB: 118 102 86 70 54 38 22 6 > > Reading symbols from /boot/modules/nvidia.ko...Reading symbols from > /boot/modules/nvidia.ko.symbols...done. > done. > Loaded symbols for /boot/modules/nvidia.ko > Reading symbols from /boot/kernel/acpi.ko...Reading symbols from > /boot/kernel/acpi.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/acpi.ko > Reading symbols from /boot/kernel/if_bge.ko...Reading symbols from > /boot/kernel/if_bge.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/if_bge.ko > Reading symbols from /boot/kernel/linux.ko...Reading symbols from > /boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > Reading symbols from /boot/kernel/msdosfs.ko...Reading symbols from > /boot/kernel/msdosfs.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/msdosfs.ko > #0 doadump () at pcpu.h:196 > 196 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > (kgdb) where > #0 doadump () at pcpu.h:196 > #1 0xc057a9ce in boot (howto=260) > at /usr/local/src/sys/kern/kern_shutdown.c:418 > #2 0xc057ac93 in panic (fmt=Variable "fmt" is not available. > ) at /usr/local/src/sys/kern/kern_shutdown.c:572 > #3 0xc059c5b2 in __stack_chk_fail () > at /usr/local/src/sys/kern/stack_protector.c:17 > #4 0xc652384a in msdosfs_rename (ap=0xc644aca4) > at > /usr/local/src/sys/modules/msdosfs/../../fs/msdosfs/msdosfs_vnops.c:1286 > #5 0xc07b4df5 in VOP_RENAME_APV (vop=0xc6525cc0, a=0xe9e59c1c) > at vnode_if.c:1184 > #6 0xc0605619 in kern_renameat (td=0xc58f1d20, oldfd=-100, > old=0xbfbfc4a0
, newfd=-100, > new=0xbfbfcca0
, > pathseg=UIO_USERSPACE) > at vnode_if.h:622 > #7 0xc06057a6 in kern_rename (td=0xc58f1d20, > from=0xbfbfc4a0
, > to=0xbfbfcca0
, > pathseg=UIO_USERSPACE) > at /usr/local/src/sys/kern/vfs_syscalls.c:3526 > #8 0xc06057d9 in rename (td=0xc58f1d20, uap=0xe9e59cf8) > at /usr/local/src/sys/kern/vfs_syscalls.c:3503 > #9 0xc07a6283 in syscall (frame=0xe9e59d38) > at /usr/local/src/sys/i386/i386/trap.c:1081 > #10 0xc078bb80 in Xint0x80_syscall () > at /usr/local/src/sys/i386/i386/exception.s:261 > #11 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > > > Let me know what I can do to help. > > Doug > From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 20:30:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23CE41065678 for ; Thu, 3 Jul 2008 20:30:27 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id BCF618FC13 for ; Thu, 3 Jul 2008 20:30:26 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 25987 invoked by uid 399); 3 Jul 2008 20:30:26 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 3 Jul 2008 20:30:26 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <486D36E0.6080005@FreeBSD.org> Date: Thu, 03 Jul 2008 13:30:24 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: Kostik Belousov References: <486BFFE5.1010808@FreeBSD.org> <20080703193856.GS17123@deviant.kiev.zoral.com.ua> In-Reply-To: <20080703193856.GS17123@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Panic using rsync to msdosfs filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 20:30:27 -0000 Kostik Belousov wrote: > Looks like this is the first casuality of the -fstack-protector. D'oh! I seem to have a talent for such things. :-/ > Try this: > > diff --git a/sys/fs/msdosfs/msdosfs_vnops.c b/sys/fs/msdosfs/msdosfs_vnops.c > index 8a1484f..fe673e0 100644 > --- a/sys/fs/msdosfs/msdosfs_vnops.c > +++ b/sys/fs/msdosfs/msdosfs_vnops.c > @@ -982,7 +982,7 @@ msdosfs_rename(ap) > struct componentname *tcnp = ap->a_tcnp; > struct componentname *fcnp = ap->a_fcnp; > struct denode *ip, *xp, *dp, *zp; > - u_char toname[11], oldname[11]; > + u_char toname[12], oldname[11]; > u_long from_diroffset, to_diroffset; > u_char to_count; > int doingdirectory = 0, newparent = 0; So far so good! I managed to complete my rsync run with that patch in, and now I'm churning the disk with other stuff to make sure. So far so good! Thanks for getting on this one so fast. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 20:52:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 829DA1065680; Thu, 3 Jul 2008 20:52:21 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 34D998FC13; Thu, 3 Jul 2008 20:52:21 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 234051CC64; Thu, 3 Jul 2008 22:52:20 +0200 (CEST) Date: Thu, 3 Jul 2008 22:52:20 +0200 From: Ed Schouten To: Peter Jeremy Message-ID: <20080703205220.GW14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mz5eWKkhz39mMVQV" Content-Disposition: inline In-Reply-To: <20080703193406.GS29380@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Arch , FreeBSD Current , Philip Paeps Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 20:52:21 -0000 --mz5eWKkhz39mMVQV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Peter, * Peter Jeremy wrote: > On 2008-Jul-02 21:09:01 +0200, Ed Schouten wrote: > >+ The new pseudo-terminal driver is capable of garbage collecting unused > > PTY's. Because PTY's are never recycled, they are a lot more robust > > (they are always initialized the same, no need to revoke() them before > > usage, etc). >=20 > When you say 'never recycled', does this include the PTY number? If > so, long running busy systems are going to get some fairly large > numbers. When will the PTY number wrap? What is the impact on tools > (eg ps, w) that assume they can represent a PTY in a small number of > digits? What about utmp(5) which uses PTY number in the index? PTY's are deallocated when unused, which means the PTY number is reused when possible. We still enfore the 1000 PTY limit, because utmp(5) only supports line names of eight bytes long ("pts/999\0"). > >- Not all drivers have been ported to the new TTY layer yet. These > > drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), > > uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), > > umodem(4), dcons(4). > > > >Even though drivers are very important to have, I am convinced we can > >get these working not long after the code as been integrated. ... > > If you really care about one of these drivers, > >please port it to the new TTY layer as soon as possible! >=20 > IMHO, this is not a reasonable approach: "Hi everyone. I'm going to > break infrastructure that a whole bunch of drivers depend on. If you > don't fix your drivers in the next few weeks then I'll disconnect > them". Either you need to provide compatibility shims (possibly > temporary and not MPSAFE) or you need to be far more pro-active in > assisting with porting existing consumers of the TTY layer. Well, even though I'd rather let other people assess me, I think I've been very proactive so far. As you can see, I sent my email to the list two days ago. In those two days I've fixed both umodem(4) and uftdi(4) to work with the new TTY layer again. > >TTY layer into our kernel. I would really appreciate it if I could get > >this code in before the end of the summer break, because I've got heaps > >of spare time to fix any problems then. >=20 > That's all very nice but what about the maintainers of all the other > drivers that you are impacting? >=20 > > sio(4) has not been ported to the new TTY layer and is very hard > > to do so. >=20 > This is the only mention of how much effort is involved in porting a > driver to use the MPSAFE TTY layer and "very hard" is not a good start. > I can't quickly find any documentation on how to go about porting an > existing driver - definitely there are no section 9 man pages describing > the new API in your patchset. Well, sio(4) isn't impossible to port to the new TTY layer, but the first thing I noticed when I was hacking on the TTY layer during my internship, was that the uart(4) code was so easy to read, I only had to alter a single 396 line C file containing all the TTY interaction, while the sio(4) was somewhat (tenfold) more complex. But I just got told sio(4) is required for pc98, because uart(4) is not supported there. This means I'll seriously consider porting sio(4) one of these days. It's no biggie, even though I think someone could better take the effort to extend uart(4). The same with dcons(4). Even though I don't have any hardware to test it personally, I'll try to make sure we'll get it working in time. > IMHO, if you can't commit fixed drivers along with the MPSAFE TTY > layer, a more reasonable schedule is to replace the existing TTY layer > with an MPSAFE TTY layer that includes compatibility shims. If the > shims make things non-MPSAFE (which is likely) then warn that they > will be going away in (say) six months. This gives developers a more > reasonable timeframe in which to update, as well as working drivers > whilst they adapt them. So let us take a look at the list again: > sio(4), cy(4), digi(4), ubser(4), uftdi(4), nmdm(4), ng_h4(4), > ng_tty(4), snp(4), rp(4), rc(4), si(4), umodem(4), dcons(4). Removing the drivers which have been fixed, or will be fixed in time: > cy(4), digi(4), ubser(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), > rc(4), si(4). After I've committed the new TTY layer, I'm going to extend its design, so we can have hooks again, similar to the old line discipline idea. This has already been discussed. I'm also planning on reviving drivers like nmdm(4) and snp(4) by then. This means we've only got these drivers left: > cy(4), digi(4), rp(4), rc(4), si(4). Who actually owns one of these devices? If you do, please contact me. If I didn't make myself clear enough: I *am* willing to (assist in porting|port) these drivers. --=20 Ed Schouten WWW: http://80386.nl/ --mz5eWKkhz39mMVQV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhtPAQACgkQ52SDGA2eCwVu3ACfUjReo68tT2bsXGyTlN61V5N4 btkAn1mJmQeu4u06jwN5qqMuKMnIPneR =nG3/ -----END PGP SIGNATURE----- --mz5eWKkhz39mMVQV-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 21:09:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 155841065672; Thu, 3 Jul 2008 21:09:50 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id C33308FC0C; Thu, 3 Jul 2008 21:09:49 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m63L9QJF080937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jul 2008 14:09:27 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <486D4006.2050303@freebsd.org> Date: Thu, 03 Jul 2008 14:09:26 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Ed Schouten References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> In-Reply-To: <20080703205220.GW14567@hoeg.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: Peter Jeremy , FreeBSD Current , FreeBSD Arch Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 21:09:50 -0000 Ed Schouten wrote: > Hello Peter, > > * Peter Jeremy wrote: > >> On 2008-Jul-02 21:09:01 +0200, Ed Schouten wrote: >> >>> + The new pseudo-terminal driver is capable of garbage collecting unused >>> PTY's. Because PTY's are never recycled, they are a lot more robust >>> (they are always initialized the same, no need to revoke() them before >>> usage, etc). >>> >> When you say 'never recycled', does this include the PTY number? If >> so, long running busy systems are going to get some fairly large >> numbers. When will the PTY number wrap? What is the impact on tools >> (eg ps, w) that assume they can represent a PTY in a small number of >> digits? What about utmp(5) which uses PTY number in the index? >> > > PTY's are deallocated when unused, which means the PTY number is reused > when possible. We still enfore the 1000 PTY limit, because utmp(5) only > supports line names of eight bytes long ("pts/999\0"). > > >>> - Not all drivers have been ported to the new TTY layer yet. These >>> drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), >>> uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), >>> umodem(4), dcons(4). >>> >>> Even though drivers are very important to have, I am convinced we can >>> get these working not long after the code as been integrated. ... >>> If you really care about one of these drivers, >>> please port it to the new TTY layer as soon as possible! >>> >> IMHO, this is not a reasonable approach: "Hi everyone. I'm going to >> break infrastructure that a whole bunch of drivers depend on. If you >> don't fix your drivers in the next few weeks then I'll disconnect >> them". Either you need to provide compatibility shims (possibly >> temporary and not MPSAFE) or you need to be far more pro-active in >> assisting with porting existing consumers of the TTY layer. >> > > Well, even though I'd rather let other people assess me, I think I've > been very proactive so far. As you can see, I sent my email to the list > two days ago. In those two days I've fixed both umodem(4) and uftdi(4) > to work with the new TTY layer again. > > >>> TTY layer into our kernel. I would really appreciate it if I could get >>> this code in before the end of the summer break, because I've got heaps >>> of spare time to fix any problems then. >>> >> That's all very nice but what about the maintainers of all the other >> drivers that you are impacting? >> >> >>> sio(4) has not been ported to the new TTY layer and is very hard >>> to do so. >>> >> This is the only mention of how much effort is involved in porting a >> driver to use the MPSAFE TTY layer and "very hard" is not a good start. >> I can't quickly find any documentation on how to go about porting an >> existing driver - definitely there are no section 9 man pages describing >> the new API in your patchset. >> > > Well, sio(4) isn't impossible to port to the new TTY layer, but the > first thing I noticed when I was hacking on the TTY layer during my > internship, was that the uart(4) code was so easy to read, I only had to > alter a single 396 line C file containing all the TTY interaction, while > the sio(4) was somewhat (tenfold) more complex. > > But I just got told sio(4) is required for pc98, because uart(4) is not > supported there. This means I'll seriously consider porting sio(4) one > of these days. It's no biggie, even though I think someone could better > take the effort to extend uart(4). > I would suggest first investigating how difficult it is to port uart to pc98. Given that we're broadening our platform support having a single serial driver seems preferable. > The same with dcons(4). Even though I don't have any hardware to test it > personally, I'll try to make sure we'll get it working in time. > I believe dcons is important and there are many people that can pitch in on this driver so I'm less worried about it. FWIW I'm 100% behind you on moving this stuff forward. This is a large project and you cannot be expected to do it by yourself. In the case of platform-specific requirements (like pc98) where you won't have access to equipment I think it's fair to request platform maintainers help. > >> IMHO, if you can't commit fixed drivers along with the MPSAFE TTY >> layer, a more reasonable schedule is to replace the existing TTY layer >> with an MPSAFE TTY layer that includes compatibility shims. If the >> shims make things non-MPSAFE (which is likely) then warn that they >> will be going away in (say) six months. This gives developers a more >> reasonable timeframe in which to update, as well as working drivers >> whilst they adapt them. >> > > So let us take a look at the list again: > > >> sio(4), cy(4), digi(4), ubser(4), uftdi(4), nmdm(4), ng_h4(4), >> ng_tty(4), snp(4), rp(4), rc(4), si(4), umodem(4), dcons(4). >> > > Removing the drivers which have been fixed, or will be fixed in time: > > >> cy(4), digi(4), ubser(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), >> rc(4), si(4). >> > > After I've committed the new TTY layer, I'm going to extend its design, > so we can have hooks again, similar to the old line discipline idea. > This has already been discussed. I'm also planning on reviving drivers > like nmdm(4) and snp(4) by then. This means we've only got these > drivers left: > > >> cy(4), digi(4), rp(4), rc(4), si(4). >> > > Who actually owns one of these devices? If you do, please contact me. If > I didn't make myself clear enough: I *am* willing to (assist in > porting|port) these drivers. > > digi is perhaps most important in this list but I think you should expect other folks to help. Sam From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 21:32:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92BA8106574C for ; Thu, 3 Jul 2008 21:32:52 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 629AB8FC1A for ; Thu, 3 Jul 2008 21:32:52 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [192.168.1.101] (cpe-74-77-179-53.buffalo.res.rr.com [74.77.179.53]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id m63LEGh5091567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jul 2008 17:14:17 -0400 (EDT) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: freebsd-stable , freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4YWWbfY2t8wPF9KwiZZm" Date: Thu, 03 Jul 2008 17:14:10 -0400 Message-Id: <1215119650.75067.10.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1335; Body=0 Fuz1=0 Fuz2=0 Cc: Subject: cvsup server reachable via IPv6... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 21:32:52 -0000 --=-4YWWbfY2t8wPF9KwiZZm Content-Type: text/plain Content-Transfer-Encoding: quoted-printable If any of you have been wishing there was an IPv6-capable cvsup server you could use (with csup as the client obviously since cvsup doesn't do IPv6...) give cvsup18.freebsd.org a try. With the help of a few other folks I got nudged into giving inetd/netcat a try as a means to feed IPv6 connections to the cvsupd server process. If you try it and have problems let me know. cvsup18 is my "little server" (handles between 200 and 300 connects a day) but if this seems to work OK I can give it a try on my "big server" (handles between 3000 and 4000 connects a day...). --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-4YWWbfY2t8wPF9KwiZZm Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkhtQSIACgkQ/G14VSmup/aNzwCeJA8yBnFpHNm2I58WKgM3xD01 ir4AniJzE9I0dkgpKpQdhq93UM2DwHTS =C40w -----END PGP SIGNATURE----- --=-4YWWbfY2t8wPF9KwiZZm-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 21:51:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70BA6106574C for ; Thu, 3 Jul 2008 21:51:40 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from smtp7.tech.numericable.fr (smtp7.tech.numericable.fr [82.216.111.43]) by mx1.freebsd.org (Postfix) with ESMTP id 4007B8FC15 for ; Thu, 3 Jul 2008 21:51:40 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from brunel.pagan.fr (cable-83.217.146.118.coditel.net [83.217.146.118]) by smtp7.tech.numericable.fr (Postfix) with ESMTP id 6A89A16380B for ; Thu, 3 Jul 2008 23:51:38 +0200 (CEST) Message-ID: <486D49EB.7070906@yahoo.fr> Date: Thu, 03 Jul 2008 23:51:39 +0200 From: Antoine BRUNEL User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Question to Sam about the ath 5424 wifi driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 21:51:40 -0000 Sorry, I did not found your direct email address... But my question is: - I currently owns a laptop with an Atheros 5424/2424 embedded wireless controler ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) ath0: mem 0xd4200000-0xd420ffff irq 19 at device 0.0 on pci6 ath0@pci0:6:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5006 family 802.11abg Wireless NIC' With the CURRENT version of FreeBSD kernel, I still get the 9.XXX version for the ath driver. Which is not working with my card. But using your modified version: * $Id: //depot/sw/branches/sam_hal/version.h#35 $ */ #define ATH_HAL_VERSION "0.10.5.6" The wireless is working fine (this mail a proof of it). So, my question is: why don't you include this version into the main branch of .CURRENT 8.0 FreeBSD ?? actually, when you fetch sources, you get version: #define ATH_HAL_VERSION "0.9.20.3" Do you still have bugs / things to resolve ?? not enough time ?? If I can help in any way.... thanks a lot by advance, and for your driver which is working very fine... From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 22:07:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEB901065685; Thu, 3 Jul 2008 22:07:14 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [198.124.252.66]) by mx1.freebsd.org (Postfix) with ESMTP id 8359A8FC0C; Thu, 3 Jul 2008 22:07:14 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id JCG75638; Thu, 03 Jul 2008 14:55:38 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 6F3114504E; Thu, 3 Jul 2008 14:55:37 -0700 (PDT) To: "Rob Lytle" In-Reply-To: Your message of "Wed, 02 Jul 2008 21:28:50 PDT." <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1215122137_50574P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 03 Jul 2008 14:55:37 -0700 From: "Kevin Oberman" Message-Id: <20080703215537.6F3114504E@ptavv.es.net> Cc: freebsd-hackers@freebsd.org, Mike Meyer , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 22:07:15 -0000 --==_Exmh_1215122137_50574P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Wed, 2 Jul 2008 21:28:50 -0700 > From: "Rob Lytle" > Sender: owner-freebsd-current@freebsd.org > > Hi All, > > I'm sorry I started a kind of flame war. All I wanted was two things: 1. > CD's that installed without being switched in and out dozens of times. That > was fixed by the suggestion of using a DVD. I didn't even know the DVD > install existed, but will do that next time. You call this a flame war? It's been pretty civil and there are no scorch marks on my display. I agree that the disk swapping is not a good thing, but I simply avoid it by never installing packages from sysinstall. I only use sysinstall for FreeBSD. Once I have FreeBSD installed, I update my ports tree with csup (but portsnap is probably a better way) and install ruby and portupgrade. Then I simply install the ports/packages I want using 'portinstall -P'. This assures that I have the latest ports and not something stale. I can speed the process by copying all of the packages from CD to my system (/usr/ports/packages/All). That way, only ports that have been updated since the release will be downloaded and I only have to change CDs a couple of times. > 2. Being able to use Sysinstall and not having it crash when a dependency > is already present. Sometimes I like to use Sysinstall to install gigantic > packages where the compile time is 26 hours, e.g KDE metapackage, and my > notebook uses an Intel Core 2 Duo at 2Ghz or thereabout. That is one hell > of a long compile time. For this request I will just have to wait for > FreeBSD 10.0. I have not seen this, but I don't sue sysinstall to install packages/ports. -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1215122137_50574P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIbUrZkn3rs5h7N1ERAueoAJ97OM7ukkvgyB8g6GKyXQqb3llYOwCdFOWb VeJSQh+TendhnsxT3t/1rd4= =uYML -----END PGP SIGNATURE----- --==_Exmh_1215122137_50574P-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 22:19:56 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1517C10656D6; Thu, 3 Jul 2008 22:19:56 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from smtp4.tech.numericable.fr (smtp4.tech.numericable.fr [82.216.111.40]) by mx1.freebsd.org (Postfix) with ESMTP id A2AC98FC16; Thu, 3 Jul 2008 22:19:55 +0000 (UTC) (envelope-from antoinebrunel@yahoo.fr) Received: from brunel.pagan.fr (cable-83.217.146.118.coditel.net [83.217.146.118]) by smtp4.tech.numericable.fr (Postfix) with ESMTP id 5DF2212A813; Fri, 4 Jul 2008 00:19:52 +0200 (CEST) Message-ID: <486D5089.6000900@yahoo.fr> Date: Fri, 04 Jul 2008 00:19:53 +0200 From: Antoine BRUNEL User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Kevin Oberman References: <20080703215537.6F3114504E@ptavv.es.net> In-Reply-To: <20080703215537.6F3114504E@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, Mike Meyer , Rob Lytle , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 22:19:56 -0000 Hi all I suggest this "flame" to stop right now... because everybody is ok finally.... I agree with Rob in the fact that 'sysinstall' is a bit disturbing tool with its way of working: the "enter" key, the error messages if HTTP source is unavailable, etc.... and I confess I had to re-install my laptop 3 or 4 times before getting what I wanted from sysinstall. Maybe this tool should be upgraded, but I think it should not follow the way other installerd did.... somebody spokes about the Oracle installer... It was a real hell for you: how to install an Oracle database onto an HP 7 inch terminal, without X and/or Java installed ?? I hope FreeBSD will never get way, like Windows or Linux.... How about to give a try at the actual Debian ncurse installer ??? still in text based environment, but very powerful .... Kevin Oberman a écrit : >> Date: Wed, 2 Jul 2008 21:28:50 -0700 >> From: "Rob Lytle" >> Sender: owner-freebsd-current@freebsd.org >> >> Hi All, >> >> I'm sorry I started a kind of flame war. All I wanted was two things: 1. >> CD's that installed without being switched in and out dozens of times. That >> was fixed by the suggestion of using a DVD. I didn't even know the DVD >> install existed, but will do that next time. >> > > You call this a flame war? It's been pretty civil and there are no scorch > marks on my display. > > I agree that the disk swapping is not a good thing, but I simply avoid > it by never installing packages from sysinstall. I only use sysinstall > for FreeBSD. > > Once I have FreeBSD installed, I update my ports tree with csup (but > portsnap is probably a better way) and install ruby and > portupgrade. Then I simply install the ports/packages I want using > 'portinstall -P'. This assures that I have the latest ports and not > something stale. I can speed the process by copying all of the packages > from CD to my system (/usr/ports/packages/All). That way, only ports > that have been updated since the release will be downloaded and I only > have to change CDs a couple of times. > > > >> 2. Being able to use Sysinstall and not having it crash when a dependency >> is already present. Sometimes I like to use Sysinstall to install gigantic >> packages where the compile time is 26 hours, e.g KDE metapackage, and my >> notebook uses an Intel Core 2 Duo at 2Ghz or thereabout. That is one hell >> of a long compile time. For this request I will just have to wait for >> FreeBSD 10.0. >> > > I have not seen this, but I don't sue sysinstall to install > packages/ports. > From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 23:04:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB19D1065673 for ; Thu, 3 Jul 2008 23:04:01 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 438098FC1D for ; Thu, 3 Jul 2008 23:04:01 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so798526uge.37 for ; Thu, 03 Jul 2008 16:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=ABM+R/HYabgPI02hrHb52sf5LY0TVpvBUL9EJwFYdgg=; b=u0BltNTb2xy6x+b2OML5768gsJxekHb6e8FtoCwh8Puo2UOUA1VT/KbIqbuC6pLc+j 0YlbJvZTN2JSwhkXxuAjx78XWpihr4RcxuY0Ddz6dX8W9teeKpGVVqhn8KMtIlZ8DNaU EJHJ+nXMWK3uBjzvXbuOKFODjP+8Dm3m1/abg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=FW6wK7u007euI+6JRO/k+XcY5z8Cdvr6f5QQNGSqLfMivvJvzpG/s01Pr1Gv7+a0E6 6+xVviVBgTfqLsshBigqWaBvuTuRqYU5EnIVnoqeJwVzbubX+MyG9PxwNP0FFDP0APy6 VLM06Jq+EO3MsrftoEJK/0Ra5XcwDMSpNPe+A= Received: by 10.66.221.19 with SMTP id t19mr2056466ugg.69.1215124748531; Thu, 03 Jul 2008 15:39:08 -0700 (PDT) Received: by 10.66.248.12 with HTTP; Thu, 3 Jul 2008 15:39:08 -0700 (PDT) Message-ID: Date: Thu, 3 Jul 2008 23:39:08 +0100 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Doug Barton" In-Reply-To: <486D2738.7020709@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486D2738.7020709@FreeBSD.org> X-Google-Sender-Auth: 218bec4666938724 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 23:04:01 -0000 2008/7/3 Doug Barton : > 1. It should be library-based and therefore be capable of supporting at > least a few different UIs (see above). > 2. At least one of those UIs should be functional over a standard serial > console. > 3. It should be scriptable. I was thinking of doing it, but nobody provided any constructive ideas and a lot of other installers started popping up, like the bsdinstaller et al, so I wasn't gonna waste any time on that front, and instead just ended up with a massive script that 'works for me'(TM) which does funky things like geom and ccache/distcc world build of the system it's installing onto. I had the first req. up and kind of expanded it into pretty cool stuff that essentially allowed the whole of system to be managed by providing custom plugins, but the monolithic world makes things a lot difficult to make the installer fancy. I'll happily revive the project if it's not going to be a total waste of time (read: others will be interested in contributing ideas and testing it). Cheers, Igor From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 01:49:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 959B11065670; Fri, 4 Jul 2008 01:49:49 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.72]) by mx1.freebsd.org (Postfix) with ESMTP id 7A9D18FCA1; Fri, 4 Jul 2008 01:49:49 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp012-bge351000.mac.com (asmtp012-bge351000 [10.150.69.75]) by smtpoutm.mac.com (Xserve/smtpout009/MantshX 4.0) with ESMTP id m641nnsG010336; Thu, 3 Jul 2008 18:49:49 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp012.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3G00KC7L30VF20@asmtp012.mac.com>; Thu, 03 Jul 2008 18:49:49 -0700 (PDT) Message-id: <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> From: Marcel Moolenaar To: Sam Leffler In-reply-to: <486D4006.2050303@freebsd.org> Date: Thu, 03 Jul 2008 18:49:47 -0700 References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> <486D4006.2050303@freebsd.org> X-Mailer: Apple Mail (2.926) Cc: FreeBSD Arch , Ed Schouten , FreeBSD Current , Peter Jeremy Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 01:49:49 -0000 On Jul 3, 2008, at 2:09 PM, Sam Leffler wrote: >> But I just got told sio(4) is required for pc98, because uart(4) is >> not >> supported there. This means I'll seriously consider porting sio(4) >> one >> of these days. It's no biggie, even though I think someone could >> better >> take the effort to extend uart(4). >> > > I would suggest first investigating how difficult it is to port uart > to pc98. Given that we're broadening our platform support having a > single serial driver seems preferable. I looked into it in 2003 but since I don't have any hardware, I wasn't the one able to do it. I think the fundamental problem is that the BRG is not part of the UART itself and needs a separate handle or even (tag, handle) pair to access. That's as far as I know the only big thing about the work. For me not having access to the hardware is a showstopper for looking into it myself. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 02:21:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25F46106564A; Fri, 4 Jul 2008 02:21:49 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au [211.29.133.51]) by mx1.freebsd.org (Postfix) with ESMTP id A84F38FC1E; Fri, 4 Jul 2008 02:21:48 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m642LPmI027222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jul 2008 12:21:27 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m642LP3j032579; Fri, 4 Jul 2008 12:21:25 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m642LPWp032578; Fri, 4 Jul 2008 12:21:25 +1000 (EST) (envelope-from peter) Date: Fri, 4 Jul 2008 12:21:25 +1000 From: Peter Jeremy To: Ed Schouten Message-ID: <20080704022125.GA32475@server.vk2pj.dyndns.org> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20080703205220.GW14567@hoeg.nl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Arch , FreeBSD Current Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 02:21:49 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Ed, Thanks for your response. On 2008-Jul-03 22:52:20 +0200, Ed Schouten wrote: >Well, even though I'd rather let other people assess me, I think I've >been very proactive so far. As you can see, I sent my email to the list >two days ago. In those two days I've fixed both umodem(4) and uftdi(4) >to work with the new TTY layer again. And I don't expect you to do all the work yourself - you can't be expected to test hardware you don't have. But where is the documentation to let someone else adapt the drivers? >> cy(4), digi(4), rp(4), rc(4), si(4). > >Who actually owns one of these devices? If you do, please contact me. If >I didn't make myself clear enough: I *am* willing to (assist in >porting|port) these drivers. I have access to a Digi Xem boards at work and have poked around inside the digi(4) code in the past. My difficulty is that the cards are all in use and upgrading to a FreeBSD-current that doesn't support them and then porting the driver is probably not an option (whereas converting it from using shims to access the TTY layer to doing so directly would probably be acceptable - because I can get the board going again in a hurry if needed). I can't help with any of the others, sorry. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhtiSUACgkQ/opHv/APuIcPxACgoXjGnN5twMkRBUf63f+nXmMJ S8wAoIpB4WxR0j4p/+KJOwJqeFZmtNQc =9A2i -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 02:54:55 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BD6E1065677 for ; Fri, 4 Jul 2008 02:54:55 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 592E08FC18 for ; Fri, 4 Jul 2008 02:54:55 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1455147rvf.43 for ; Thu, 03 Jul 2008 19:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:subject :message-id:mail-followup-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent:organization :x-operation-sytem:from; bh=03QaGi1knQrwDDrbM6M7qhh76Stn8cI5I4x+zpgwEDk=; b=EAJK4SG2/wM4vCw1uovRn+NfVhaK4R5yE5+TePIyWZFT7Kdlv3kUPI6DHKffFg8fqU iIGXx9a9kdFeFmTY/4tNMi++eYgo9SBi8vTyVQ1AaZG+/krYptKZzisg1D7mfbrhikVK JPmWROW2Gq4o2o2V97X2JVk4S35kE+xw7lV5w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:subject:message-id:mail-followup-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :organization:x-operation-sytem:from; b=KjQiiDRda1XquFOqhd4XQDWYjIHDXbMpg+ygXEdwHFqjlpH2PEcJxvqqaFKvhVaUOH 7tUG/iT1wUXk1FOdvavTWe0yxaXRPvVH0HDXEjuskqW6DxvzqmtIN3uMCx1IXUwd/Np+ 7Wqa+e8TGV2+m0DAaegZORwNyYAYMWsoK4KDc= Received: by 10.115.78.1 with SMTP id f1mr2337597wal.150.1215140094951; Thu, 03 Jul 2008 19:54:54 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id k35sm1140481waf.15.2008.07.03.19.54.23 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Jul 2008 19:54:54 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Fri, 4 Jul 2008 11:54:01 +0900 Date: Fri, 4 Jul 2008 11:54:01 +0900 To: current@freebsd.org Message-ID: <20080704025401.GF57570@freebsd.weongyo.org> Mail-Followup-To: current@freebsd.org References: <20080703114158.GE57570@freebsd.weongyo.org> <486CEAF7.6040709@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <486CEAF7.6040709@freebsd.org> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: Subject: Re: Q: 802.11 vap monitor mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 02:54:55 -0000 On Thu, Jul 03, 2008 at 08:06:31AM -0700, Sam Leffler wrote: > Weongyo Jeong wrote: > >During testing a new driver, I got a problem to test a monitor mode at > >802.11 vap I'm using. > > > ># uname -a > >FreeBSD kkk 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Wed May 14 11:27:37 KST > >2008 root@kkk:/usr/obj/usr/src/sys/GENERIC i386 > ># ifconfig wlan0 create wlandev upgt0 wlanmode monitor > ># ifconfig wlan0 up > ># ifconfig > >[...] > >upgt0: > >flags=108943 > >metric 0 mtu 2290 > > ether 00:0f:b5:dd:6f:36 > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > > > status: running > >wlan0: > >flags=28943 > >metric 0 mtu 1500 > > ether 00:0f:b5:dd:6f:36 > > inet6 fe80::20f:b5ff:fedd:6f36%wlan0 prefixlen 64 scopeid 0xd > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > > > status: running > > ssid "" channel 1 (2412 Mhz 11g) bssid 00:0f:b5:dd:6f:36 > > country US authmode OPEN privacy OFF txpower 0 scanvalid 60 > > protmode CTS > > > >As seeing, it looks work but the problem is happend when I ran stumbler > >(src/tools/tools/net80211/stumbler) program. > > > >The error message is "ioctl(BIOCSDLT): Invalid argument" that it's > >emitted to screen when I execute the following command: > ># ./stumbler wlan0 > > > >Are there something I missed? > > > What DLT is stumbler using? If it's requesting IEEE802_11_RADIO then DLT was DLT_IEEE802_11_RADIO so it looks the stumbler code is broken as Paul B. Mahol mentioned. > this will fail as that is not available for the vap, only for the > underlying device. This is an open issue that I'm looking for help > with--previously an 802.11 device supported 3 DLT's: 802.3, 802.11, and > radiotap but now it only supports the first 2. The net80211 layer does > not have all the data required to dispatch radiotap headers (only the > driver does) so we need to push the information up to net80211 for each > rx'd packet (possibly expensive) or provide some net80211-level support > for dispatching radiotap data through vap's. regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 04:26:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4FD01065677 for ; Fri, 4 Jul 2008 04:26:17 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id 735A78FC14 for ; Fri, 4 Jul 2008 04:26:17 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so962385wfg.7 for ; Thu, 03 Jul 2008 21:26:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=AgLZQOkDjhJZFmRAKI6UEyJ6YPU7QfdVsimTsD5B92o=; b=f6HOxGExcl7wH3bNEU/GkQ4STRLWS2mr/YkIoQ5X84Db5sg2im4HsKsYYr+gHmNiOM hSblC5zu5OWIopZDEoW5vfDkt4NaSB/y/8NYcGtocqnz0hIYoF2xB22gDloj/BoDef2F D0Gvf1B9YqVNsrEGKL/FLLxpGm87MJp4L1NT4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=KPtKAFkctuwo0TRJirXJvLHm67+EtvD1TjBjmZNxEPathAXgHVt95PDWek8zhPU420 ujBuXEqhYjeWbS7TJ7oo1CM4wQx6345k6qZvJMqCKXSriUgmOq58Eb/4HHZkmultJRDX DK8HlwDw2G7RSfpw1V4mGJZwcmzdwBpvp4E1k= Received: by 10.142.162.9 with SMTP id k9mr107033wfe.93.1215145577049; Thu, 03 Jul 2008 21:26:17 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Thu, 3 Jul 2008 21:26:16 -0700 (PDT) Message-ID: <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> Date: Thu, 3 Jul 2008 21:26:16 -0700 From: "Rob Lytle" To: "Kevin Oberman" , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <20080703215537.6F3114504E@ptavv.es.net> MIME-Version: 1.0 References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> X-Mailman-Approved-At: Fri, 04 Jul 2008 04:28:04 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 04:26:17 -0000 Hi Kevin, The sysinstall dependency problem has existed for 10 years, so I doubt that its unique to me. It has occurred in every installation I have ever done. I use portupgrade for all ports. i strongly disagree with using ports for huge packages. I don't have the time to waste compiling. Plus, you are presented with numerous nag screens so you have to babysit the whole process. Rob. On Thu, Jul 3, 2008 at 2:55 PM, Kevin Oberman wrote: > > Date: Wed, 2 Jul 2008 21:28:50 -0700 > > From: "Rob Lytle" > > Sender: owner-freebsd-current@freebsd.org > > > > Hi All, > > > > I'm sorry I started a kind of flame war. All I wanted was two things: > 1. > > CD's that installed without being switched in and out dozens of times. > That > > was fixed by the suggestion of using a DVD. I didn't even know the DVD > > install existed, but will do that next time. > > You call this a flame war? It's been pretty civil and there are no scorch > marks on my display. > > I agree that the disk swapping is not a good thing, but I simply avoid > it by never installing packages from sysinstall. I only use sysinstall > for FreeBSD. > > Once I have FreeBSD installed, I update my ports tree with csup (but > portsnap is probably a better way) and install ruby and > portupgrade. Then I simply install the ports/packages I want using > 'portinstall -P'. This assures that I have the latest ports and not > something stale. I can speed the process by copying all of the packages > from CD to my system (/usr/ports/packages/All). That way, only ports > that have been updated since the release will be downloaded and I only > have to change CDs a couple of times. > > > > 2. Being able to use Sysinstall and not having it crash when a > dependency > > is already present. Sometimes I like to use Sysinstall to install > gigantic > > packages where the compile time is 26 hours, e.g KDE metapackage, and my > > notebook uses an Intel Core 2 Duo at 2Ghz or thereabout. That is one > hell > > of a long compile time. For this request I will just have to wait for > > FreeBSD 10.0. > > I have not seen this, but I don't sue sysinstall to install > packages/ports. > -- > 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 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 04:33:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DE2C1065685; Fri, 4 Jul 2008 04:33:07 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 3845A8FC0A; Fri, 4 Jul 2008 04:33:07 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.2/8.14.2) with ESMTP id m644W8jk072941; Thu, 3 Jul 2008 23:32:08 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <486DA7FC.8050304@math.missouri.edu> Date: Thu, 03 Jul 2008 23:33:00 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080702 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Rob Lytle References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> In-Reply-To: <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 04:33:07 -0000 Rob Lytle wrote: > Hi Kevin, > > The sysinstall dependency problem has existed for 10 years, so I doubt that > its unique to me. It has occurred in every installation I have ever done. > > I use portupgrade for all ports. > > i strongly disagree with using ports for huge packages. I don't have the > time to waste compiling. Plus, you are presented with numerous nag screens > so you have to babysit the whole process. You can get rid of the nag screens by putting "BATCH=yes" into /etc/make.conf. (Not that this negates your other points.) From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 04:38:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1732E1065673 for ; Fri, 4 Jul 2008 04:38:54 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by mx1.freebsd.org (Postfix) with ESMTP id D65B88FC18 for ; Fri, 4 Jul 2008 04:38:53 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so965404wfg.7 for ; Thu, 03 Jul 2008 21:38:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=U3uuSj89k648vIGYMtB86zy8DW93EnWR1AzdGWZyKU4=; b=XFYtkXS8BoB5PLOqBiy2epZ1QBJ2wEEGXir7efCj/XxU3HW5pQQ/kOQAWfqhrZ43C9 GWfGh/2hMha6R1TKY9ZtOeYT//ev1lv8qEz0Bsg/MdJDzFBIKVtW2NVp36avsK4CSdv1 FOk7wAvYEFDhyW4MrZARmPyB2Gkj10Qb97zvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=e85qGRk/euMlegi86GURceDNjAG19XPqMzk//KHc2HbLa4H8KUdTuyUkE95Hlqb59Q 2CuL8JymahANYyXG5jMqkVEpVxJ9nIPYmfl4F5aOcR0bjCKSk43LoNi7Fx7rUWWAVlhv w+0VzzvPwO4w3QljIyYmpbiswb56Ev0kns6XM= Received: by 10.143.18.21 with SMTP id v21mr107370wfi.185.1215146333511; Thu, 03 Jul 2008 21:38:53 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Thu, 3 Jul 2008 21:38:53 -0700 (PDT) Message-ID: <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> Date: Thu, 3 Jul 2008 21:38:53 -0700 From: "Rob Lytle" To: "Stephen Montgomery-Smith" In-Reply-To: <486DA7FC.8050304@math.missouri.edu> MIME-Version: 1.0 References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> X-Mailman-Approved-At: Fri, 04 Jul 2008 04:57:39 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 04:38:54 -0000 On Thu, Jul 3, 2008 at 9:33 PM, Stephen Montgomery-Smith < stephen@math.missouri.edu> wrote: > Rob Lytle wrote: > >> Hi Kevin, >> >> The sysinstall dependency problem has existed for 10 years, so I doubt >> that >> its unique to me. It has occurred in every installation I have ever done. >> >> I use portupgrade for all ports. >> >> i strongly disagree with using ports for huge packages. I don't have the >> time to waste compiling. Plus, you are presented with numerous nag >> screens >> so you have to babysit the whole process. >> > > You can get rid of the nag screens by putting "BATCH=yes" into > /etc/make.conf. (Not that this negates your other points.) What the hell does "yes" mean? That all option boxes are checked, or none at all? I have never seen this explained anywhere. Rob -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 05:09:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C99C41065683; Fri, 4 Jul 2008 05:09:53 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 92C4E8FC0A; Fri, 4 Jul 2008 05:09:53 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.2/8.14.2) with ESMTP id m6458xSg074281; Fri, 4 Jul 2008 00:09:00 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <486DB09F.4080803@math.missouri.edu> Date: Fri, 04 Jul 2008 00:09:51 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080702 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Rob Lytle References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> In-Reply-To: <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 05:09:53 -0000 Rob Lytle wrote: > On Thu, Jul 3, 2008 at 9:33 PM, Stephen Montgomery-Smith < > stephen@math.missouri.edu> wrote: > >> Rob Lytle wrote: >> >>> Hi Kevin, >>> >>> The sysinstall dependency problem has existed for 10 years, so I doubt >>> that >>> its unique to me. It has occurred in every installation I have ever done. >>> >>> I use portupgrade for all ports. >>> >>> i strongly disagree with using ports for huge packages. I don't have the >>> time to waste compiling. Plus, you are presented with numerous nag >>> screens >>> so you have to babysit the whole process. >>> >> You can get rid of the nag screens by putting "BATCH=yes" into >> /etc/make.conf. (Not that this negates your other points.) > > > What the hell does "yes" mean? That all option boxes are checked, or none > at all? I have never seen this explained anywhere. It means it acts as though you didn't change any of the check boxes at all. (So either the default, or if it was previously set in /var/db/ports, then what that is.) It is explained in "man ports" but not in great detail. From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 05:33:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 036B7106566C; Fri, 4 Jul 2008 05:33:17 +0000 (UTC) (envelope-from simoncpu@infoweapons.com) Received: from infoweapons.com (mail0.infoweapons.net [204.2.248.50]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2098FC0A; Fri, 4 Jul 2008 05:33:16 +0000 (UTC) (envelope-from simoncpu@infoweapons.com) Received: from ([58.71.34.138]) by mail0.infoweapons.com with ESMTP with TLS id 4321444.460049; Fri, 04 Jul 2008 01:17:50 -0400 Message-ID: <486DB3CB.9000906@infoweapons.com> Date: Fri, 04 Jul 2008 13:23:23 +0800 From: "Simon Cornelius P. Umacob" Organization: Infoweapons Corporation User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: Rob Lytle References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> In-Reply-To: <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Stephen Montgomery-Smith , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 05:33:17 -0000 Rob Lytle wrote: >>> >> You can get rid of the nag screens by putting "BATCH=yes" into >> /etc/make.conf. (Not that this negates your other points.) > > > What the hell does "yes" mean? That all option boxes are checked, or none > at all? I have never seen this explained anywhere. > It means, "yeah, whatever, as long as it will work." :) [ simon.cpu ] -- And /usr/games/fortune futurama says: "Planet Express: our crew is replaceable, your package isn't." -Advertisement From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 05:43:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD7041065674; Fri, 4 Jul 2008 05:43:12 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6998FC1A; Fri, 4 Jul 2008 05:43:12 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1KEe44-0004zJ-0d; Fri, 04 Jul 2008 07:42:36 +0200 Message-ID: <486DB848.8000408@gwdg.de> Date: Fri, 04 Jul 2008 07:42:32 +0200 From: Rainer Hurling User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Kostik Belousov References: <486BFFE5.1010808@FreeBSD.org> <20080703193856.GS17123@deviant.kiev.zoral.com.ua> In-Reply-To: <20080703193856.GS17123@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Doug Barton , freebsd-current@freebsd.org Subject: Re: Panic using rsync to msdosfs filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 05:43:13 -0000 The panic when moving files on msdosfs also disappeared. Thank you for the patch. Rainer Hurling On 03.07.2008 21:38 (UTC+1), Kostik Belousov wrote: > On Wed, Jul 02, 2008 at 03:23:33PM -0700, Doug Barton wrote: >> I have a western digital passport USB hard drive that I use for >> backups. It's always worked fine in FreeBSD and Windows doing straight >> copies. Today I tried to get fancy and use rsync and it blew up on me. >> >> It is a large disk (160G) and I use the following options in fstab: >> /dev/da0s1 /mnt/wd msdosfs rw,noauto,-olarge,-m775 0 0 >> >> Using the following command line for rsync I get a panic as soon as I >> hit return: rsync -vv --backup -u -rlt source/ destination/ >> >> I'm using -current as of r180191. Here is the stack trace: >> Unread portion of the kernel message buffer: >> panic: stack overflow detected; backtrace may be corrupted >> cpuid = 1 >> Uptime: 1h52m1s >> Physical memory: 2029 MB >> Dumping 133 MB: 118 102 86 70 54 38 22 6 >> >> Reading symbols from /boot/modules/nvidia.ko...Reading symbols from >> /boot/modules/nvidia.ko.symbols...done. >> done. >> Loaded symbols for /boot/modules/nvidia.ko >> Reading symbols from /boot/kernel/acpi.ko...Reading symbols from >> /boot/kernel/acpi.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/acpi.ko >> Reading symbols from /boot/kernel/if_bge.ko...Reading symbols from >> /boot/kernel/if_bge.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/if_bge.ko >> Reading symbols from /boot/kernel/linux.ko...Reading symbols from >> /boot/kernel/linux.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/linux.ko >> Reading symbols from /boot/kernel/msdosfs.ko...Reading symbols from >> /boot/kernel/msdosfs.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/msdosfs.ko >> #0 doadump () at pcpu.h:196 >> 196 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); >> (kgdb) where >> #0 doadump () at pcpu.h:196 >> #1 0xc057a9ce in boot (howto=260) >> at /usr/local/src/sys/kern/kern_shutdown.c:418 >> #2 0xc057ac93 in panic (fmt=Variable "fmt" is not available. >> ) at /usr/local/src/sys/kern/kern_shutdown.c:572 >> #3 0xc059c5b2 in __stack_chk_fail () >> at /usr/local/src/sys/kern/stack_protector.c:17 >> #4 0xc652384a in msdosfs_rename (ap=0xc644aca4) >> at >> /usr/local/src/sys/modules/msdosfs/../../fs/msdosfs/msdosfs_vnops.c:1286 >> #5 0xc07b4df5 in VOP_RENAME_APV (vop=0xc6525cc0, a=0xe9e59c1c) >> at vnode_if.c:1184 >> #6 0xc0605619 in kern_renameat (td=0xc58f1d20, oldfd=-100, >> old=0xbfbfc4a0
, newfd=-100, >> new=0xbfbfcca0
, >> pathseg=UIO_USERSPACE) >> at vnode_if.h:622 >> #7 0xc06057a6 in kern_rename (td=0xc58f1d20, >> from=0xbfbfc4a0
, >> to=0xbfbfcca0
, >> pathseg=UIO_USERSPACE) >> at /usr/local/src/sys/kern/vfs_syscalls.c:3526 >> #8 0xc06057d9 in rename (td=0xc58f1d20, uap=0xe9e59cf8) >> at /usr/local/src/sys/kern/vfs_syscalls.c:3503 >> #9 0xc07a6283 in syscall (frame=0xe9e59d38) >> at /usr/local/src/sys/i386/i386/trap.c:1081 >> #10 0xc078bb80 in Xint0x80_syscall () >> at /usr/local/src/sys/i386/i386/exception.s:261 >> #11 0x00000033 in ?? () >> Previous frame inner to this frame (corrupt stack?) >> >> >> Let me know what I can do to help. > > Looks like this is the first casuality of the -fstack-protector. > Try this: > > diff --git a/sys/fs/msdosfs/msdosfs_vnops.c b/sys/fs/msdosfs/msdosfs_vnops.c > index 8a1484f..fe673e0 100644 > --- a/sys/fs/msdosfs/msdosfs_vnops.c > +++ b/sys/fs/msdosfs/msdosfs_vnops.c > @@ -982,7 +982,7 @@ msdosfs_rename(ap) > struct componentname *tcnp = ap->a_tcnp; > struct componentname *fcnp = ap->a_fcnp; > struct denode *ip, *xp, *dp, *zp; > - u_char toname[11], oldname[11]; > + u_char toname[12], oldname[11]; > u_long from_diroffset, to_diroffset; > u_char to_count; > int doingdirectory = 0, newparent = 0; From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 06:16:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F4D51065671 for ; Fri, 4 Jul 2008 06:16:05 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from mail.rubicom.hu (mail.rubicom.hu [89.147.80.28]) by mx1.freebsd.org (Postfix) with ESMTP id 1F9E98FC19 for ; Fri, 4 Jul 2008 06:16:04 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from localhost ([127.0.0.1] helo=mail.rubicom.hu) by mail.rubicom.hu with smtp (Exim 4.63) (envelope-from ) id 1KEdm7-0004Kb-U4 for freebsd-current@freebsd.org; Fri, 04 Jul 2008 07:24:04 +0200 Received: from ip5993549e.rubicom.hu ([89.147.84.158] helo=baranyfelhocske.buza.adamsfamily.xx) by mail.rubicom.hu with esmtp (Exim 4.63) (envelope-from ) id 1KEdlv-0004Ht-8A for freebsd-current@freebsd.org; Fri, 04 Jul 2008 07:23:51 +0200 Received: from baranyfelhocske.buza.adamsfamily.xx (localhost [127.0.0.1]) by baranyfelhocske.buza.adamsfamily.xx (8.14.2/8.14.2) with ESMTP id m645Np0i002830 for ; Fri, 4 Jul 2008 07:23:51 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from sziszi@localhost) by baranyfelhocske.buza.adamsfamily.xx (8.14.2/8.14.2/Submit) id m645Npmh002829 for freebsd-current@freebsd.org; Fri, 4 Jul 2008 07:23:51 +0200 (CEST) (envelope-from sziszi@bsd.hu) X-Authentication-Warning: baranyfelhocske.buza.adamsfamily.xx: sziszi set sender to sziszi@bsd.hu using -f Date: Fri, 4 Jul 2008 07:23:51 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Message-ID: <20080704052350.GA2654@baranyfelhocske.buza.adamsfamily.xx> References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> <486DB09F.4080803@math.missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <486DB09F.4080803@math.missouri.edu> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 06:16:05 -0000 On Fri, Jul 04, 2008 at 12:09:51AM -0500, Stephen Montgomery-Smith wrote: > Rob Lytle wrote: > > On Thu, Jul 3, 2008 at 9:33 PM, Stephen Montgomery-Smith < > > stephen@math.missouri.edu> wrote: <...> > >> You can get rid of the nag screens by putting "BATCH=yes" into > >> /etc/make.conf. (Not that this negates your other points.) > > > > > > What the hell does "yes" mean? That all option boxes are checked, or none > > at all? I have never seen this explained anywhere. > > It means it acts as though you didn't change any of the check boxes at > all. (So either the default, or if it was previously set in > /var/db/ports, then what that is.) > > It is explained in "man ports" but not in great detail. Of course, doing "make config-recursive" is even better. That way you actually do have a chance to set the options, but on all screens in one go. After that, you can just get up and leave it to work. If you use portupgrade, you can also use /usr/local/etc/pkgtools.conf to record your preferences for options, they will be then used for all subsequent upgrades. Also, luckily the options do not change with every version upgrade, so it is quite possible to set them once using "make configure-recursive" and then only change them if there is a reason to, because your choices are recorded and automatically used by the ports by default. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 09:22:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B19801065677; Fri, 4 Jul 2008 09:22:45 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 702F78FC21; Fri, 4 Jul 2008 09:22:45 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id C82851CC64; Fri, 4 Jul 2008 11:22:44 +0200 (CEST) Date: Fri, 4 Jul 2008 11:22:44 +0200 From: Ed Schouten To: Peter Jeremy Message-ID: <20080704092244.GY14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> <20080704022125.GA32475@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sKosZo66cxuwvnFI" Content-Disposition: inline In-Reply-To: <20080704022125.GA32475@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Arch , FreeBSD Current , Philip Paeps Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 09:22:45 -0000 --sKosZo66cxuwvnFI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Peter, * Peter Jeremy wrote: > On 2008-Jul-03 22:52:20 +0200, Ed Schouten wrote: > >Well, even though I'd rather let other people assess me, I think I've > >been very proactive so far. As you can see, I sent my email to the list > >two days ago. In those two days I've fixed both umodem(4) and uftdi(4) > >to work with the new TTY layer again. >=20 > And I don't expect you to do all the work yourself - you can't be > expected to test hardware you don't have. But where is the documentation > to let someone else adapt the drivers? Well, right now documentation on the KPI is one of the things that is missing. As you mentioned in your first email, I am planning to add several man9 pages, but so far I haven't found any time to write them. I think there are already various (very small) drivers that could be used as examples. Below is a list of files, including their size in lines: | 241 /sys/dev/ofw/ofw_console.c | 181 /sys/ia64/ia64/ssc.c | 371 /sys/sun4v/sun4v/hvcons.c > >> cy(4), digi(4), rp(4), rc(4), si(4). > > > >Who actually owns one of these devices? If you do, please contact me. If > >I didn't make myself clear enough: I *am* willing to (assist in > >porting|port) these drivers. >=20 > I have access to a Digi Xem boards at work and have poked around > inside the digi(4) code in the past. My difficulty is that the cards > are all in use and upgrading to a FreeBSD-current that doesn't support > them and then porting the driver is probably not an option (whereas > converting it from using shims to access the TTY layer to doing so > directly would probably be acceptable - because I can get the board > going again in a hurry if needed). The problem with the old TTY layer, is that drivers tend to access the internals of the TTY structure very often. A good example of this is the clists, where TTY drivers tamper around inside the clist and cblock structures. There is not much room to implement a compatibility layer there. The digi(4) code shouldn't be very hard to port. As I said before, I am considering making most drivers at least compile before the code hits the tree, which should make it a lot easier for people to get their things working again. Yours, --=20 Ed Schouten WWW: http://80386.nl/ --sKosZo66cxuwvnFI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkht6+QACgkQ52SDGA2eCwXz7wCfRAlAhWFJgjBxW7hZUBExfOPi HrkAninxCBEUUS7jyOACE+BnpysrUCDW =b5xi -----END PGP SIGNATURE----- --sKosZo66cxuwvnFI-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 09:35:53 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19A201065674 for ; Fri, 4 Jul 2008 09:35:53 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id A5EC68FC22 for ; Fri, 4 Jul 2008 09:35:52 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m649ZpGr082250 for ; Fri, 4 Jul 2008 13:35:51 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Fri, 4 Jul 2008 13:35:51 +0400 (MSD) From: Dmitry Morozovsky To: freebsd-current@FreeBSD.org Message-ID: <20080704133344.Y35668@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Fri, 04 Jul 2008 13:35:51 +0400 (MSD) Cc: Subject: Re: profiling broken on RELENG_7/i386 (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 09:35:53 -0000 Colleagues, As HEAD is affected too, I think discussion should be moved to -current@ The bug is triggered by the following test program: #include int main(int argc, char *argv[]) { int ch; while ((ch = getopt(argc, argv, "")) != -1) { } return (0); } Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ ---------- Forwarded message ---------- Date: Fri, 4 Jul 2008 13:26:57 +0400 (MSD) From: Dmitry Morozovsky To: freebsd-hackers@freebsd.org Cc: oleg@rinet.ru Subject: Re: profiling broken on RELENG_7/i386 On Fri, 4 Jul 2008, Dmitry Morozovsky wrote: DM> It seems we step on a bug in gcc in RELENG_7/i386 DM> DM> It is triggered at least by profiling program which uses getopt(3): [snip] DM> other ref platforms seem to be ok. Nah, HEAD/i386 also has this bug, though backtrace is a bit different: marck@ref8-i386:~/tmp/gprof> make clean all rm -f test test.o Warning: Object directory not changed from original /dumpster/home/marck/tmp/gprof cc -O2 -pipe -march=prescott -g -pg -fstack-protector -c test.c cc -O2 -pipe -march=prescott -g -pg -fstack-protector -o test test.o marck@ref8-i386:~/tmp/gprof> ./test Segmentation fault (core dumped) marck@ref8-i386:~/tmp/gprof> gdb test test.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Core was generated by `test'. Program terminated with signal 11, Segmentation fault. #0 0x08048242 in getopt () (gdb) bt #0 0x08048242 in getopt () #1 0x080481f9 in main (argc=0, argv=0x0) at test.c:9 (gdb) l 9 while ((ch = getopt(argc, argv, "")) != -1) { 10 } 11 12 return (0); 13 } (gdb) marck@ref8-i386:~/tmp/gprof> truss ./test __sysctl(0xbf7fe728,0x2,0x8071ff0,0xbf7fe730,0x0,0x0) = 0 (0x0) __sysctl(0xbf7fe67c,0x2,0x80776a8,0xbf7fe684,0x0,0x0) = 0 (0x0) __sysctl(0xbf7fe6cc,0x2,0xbf7fe6d8,0xbf7fe6dc,0x0,0x0) = 0 (0x0) readlink("/etc/malloc.conf","DMaj",1024) = 4 (0x4) issetugid(0x806c233,0xbf7fe737,0x400,0xbf7fe730,0x0,0x0) = 0 (0x0) break(0x8100000) = 0 (0x0) break(0x8200000) = 0 (0x0) sysarch(0xa,0xbf7feba0,0xbf7febc8,0x8048555,0x8102040,0xc) = 0 (0x0) break(0x822c69c) = 0 (0x0) profil(0x8208988,0x11e8a,0x8048148,0x8000,0x0,0x0) = 0 (0x0) __sysctl(0xbf7feb9c,0x2,0x8072140,0xbf7feba4,0x0,0x0) = 0 (0x0) SIGNAL 11 (SIGSEGV) {HEAD,RELENG_7}/amd64 and RELENG_6/* seem to perform well Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 09:37:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E39110656C3 for ; Fri, 4 Jul 2008 09:37:51 +0000 (UTC) (envelope-from peter@wemm.org) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 02A4C8FC15 for ; Fri, 4 Jul 2008 09:37:50 +0000 (UTC) (envelope-from peter@wemm.org) Received: by an-out-0708.google.com with SMTP id b33so264111ana.13 for ; Fri, 04 Jul 2008 02:37:50 -0700 (PDT) Received: by 10.100.139.20 with SMTP id m20mr272649and.135.1215162777449; Fri, 04 Jul 2008 02:12:57 -0700 (PDT) Received: by 10.100.45.17 with HTTP; Fri, 4 Jul 2008 02:12:57 -0700 (PDT) Message-ID: Date: Fri, 4 Jul 2008 02:12:57 -0700 From: "Peter Wemm" To: "Ed Schouten" In-Reply-To: <20080703205220.GW14567@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> Cc: Peter Jeremy , FreeBSD Current , FreeBSD Arch Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 09:37:51 -0000 On Thu, Jul 3, 2008 at 1:52 PM, Ed Schouten wrote: [..] >> cy(4), digi(4), rp(4), rc(4), si(4). > > Who actually owns one of these devices? If you do, please contact me. If > I didn't make myself clear enough: I *am* willing to (assist in > porting|port) these drivers. I use si extensively. For example: si0: port 0xd800-0xd87f mem 0xefffd000-0xefffd07f,0xeffe0000-0xeffeffff irq 18 at device 8.0 on pci1 si0: [GIANT-LOCKED] si0: PLX register 0x50: 0x18044000 changed to 0x18260000 si0: card: SXPCI, ports: 8, modules: 1, type: 40 (XIO) I'll be happy to take a shot at it but I'll need a few hints or worked examples. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 09:59:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89D9E106567E for ; Fri, 4 Jul 2008 09:59:20 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1122D8FC23 for ; Fri, 4 Jul 2008 09:59:19 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m649xItd082653; Fri, 4 Jul 2008 13:59:18 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Fri, 4 Jul 2008 13:59:18 +0400 (MSD) From: Dmitry Morozovsky To: Marcel Moolenaar In-Reply-To: Message-ID: <20080704135827.H35668@woozle.rinet.ru> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Fri, 04 Jul 2008 13:59:18 +0400 (MSD) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 09:59:20 -0000 On Tue, 1 Jul 2008, Marcel Moolenaar wrote: MM> > - I have spent few hours figuring out why serial interfaces MM> > covered by puc(4) do not come up at boot time. The issue was I tried MM> > to use kernel module instead of compiling puc(4) into the kernel. MM> > Will it be good to have explicit note about it in the man page? MM> MM> Well, no. There's a very simple rule: MM> MM> If driver C is a child of a driver P and driver P is MM> loaded as a module, then driver C must be loaded as MM> a module as well. MM> MM> In this case uart(4) and ppc(4) are children of puc(4) MM> and both are compiled into the kernel by default. So, MM> you must either compile puc(4) into the kernel or MM> build uart(4) and puc(4) as modules as well. MM> MM> In other words: there's no problem with puc(4) being MM> loaded as a module. It's a generic problem with our MM> modules vs. compiled-in case. doesn't splitting uart out of kernel broke serial console? Last time I checked it did. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 05:33:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15791106567D for ; Fri, 4 Jul 2008 05:33:05 +0000 (UTC) (envelope-from freebsd-nospam@yaxom.com) Received: from gw.yaxom.com (gw.yaxom.com [59.167.217.197]) by mx1.freebsd.org (Postfix) with SMTP id 3FC198FC15 for ; Fri, 4 Jul 2008 05:33:03 +0000 (UTC) (envelope-from freebsd-nospam@yaxom.com) Received: (qmail 86533 invoked from network); 4 Jul 2008 15:06:21 +1000 Received: from joker.yaxom.com (172.16.1.10) by iliad.yaxom.com with SMTP; 4 Jul 2008 15:06:21 +1000 Received: (qmail 49491 invoked by uid 1001); 4 Jul 2008 15:06:21 +1000 Message-ID: Date: Fri, 4 Jul 2008 15:06:21 +1000 From: Greg Black To: Rob Lytle References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> User-Agent: Mutt/1.4.2.2i; gjb-muttsend.sh 1.7 2004-10-05 X-Uptime: 98 days X-Operating-System: FreeBSD 6.2-RELEASE-p5 i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.yaxom.com/gjb.html X-Blog: http://www.yaxom.com/gjb/blog/ X-Image-URL: http://www.yaxom.com/gjb/gjb-auug048.gif X-PGP-Key-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-Request-PGP: http://www.yaxom.com/keys/4B04B7D6.asc X-Mailman-Approved-At: Fri, 04 Jul 2008 10:52:20 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 05:33:05 -0000 On 2008-07-03, Rob Lytle wrote: > > You can get rid of the nag screens by putting "BATCH=yes" into > > /etc/make.conf. (Not that this negates your other points.) > > What the hell does "yes" mean? That all option boxes are checked, or none > at all? I have never seen this explained anywhere. Instead of all this vociferous whining, how about just doing a bit of reading of the documentation? The ports(7) page might be a place to start. From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 05:58:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC2C106568B for ; Fri, 4 Jul 2008 05:58:23 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id 9A82E8FC21 for ; Fri, 4 Jul 2008 05:58:22 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so983685wfg.7 for ; Thu, 03 Jul 2008 22:58:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=YhCQPadCXOvRmIvYawgdW3v2OJSl9Bk9lj+imuqIkKw=; b=pKivR2/oHMP6ByAxiMwlpMDmLH3Cyt4MKIEQHwx/IjqmYzzriYl8zzsY1uBWIj6eWD C6dm47yoREhs7KJSsjeHIUUQ93HYZtyKRXKWiVNchzXTivb39E/ZYClJgHsCJLLYFVLA L+gTRK5E1/fqtujbtmmqvDKdDmg60gA4dedmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=czngo1qrlp4LDyYvHkVAXxfuya9k77jZV7vzjcEiMdyYumx1ttjNWkSp+IXqsvNyTW yERJCb+jklHuCi+fZXDe/CVjhZ2o31UmJCy+qN2FdGyhfvE68L+7elQ7JCRT323SE5CI ERUfMOoUp20OuJOgU80ZGi/xcvp1vIXqD5gFc= Received: by 10.142.142.14 with SMTP id p14mr114615wfd.104.1215151102196; Thu, 03 Jul 2008 22:58:22 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Thu, 3 Jul 2008 22:58:22 -0700 (PDT) Message-ID: <784966050807032258n230bc0bx461b652c8ae6da71@mail.gmail.com> Date: Thu, 3 Jul 2008 22:58:22 -0700 From: "Rob Lytle" To: "Greg Black" In-Reply-To: MIME-Version: 1.0 References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> X-Mailman-Approved-At: Fri, 04 Jul 2008 10:58:04 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 05:58:23 -0000 On Thu, Jul 3, 2008 at 10:06 PM, Greg Black wrote: > On 2008-07-03, Rob Lytle wrote: > > > > You can get rid of the nag screens by putting "BATCH=yes" into > > > /etc/make.conf. (Not that this negates your other points.) > > > > What the hell does "yes" mean? That all option boxes are checked, or > none > > at all? I have never seen this explained anywhere. > > Instead of all this vociferous whining, how about just doing a bit of > reading of the documentation? The ports(7) page might be a place to > start. > That would have been wonderful, groovy, etc if I had known there was a ports page. Rob. -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 06:04:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AA481065670 for ; Fri, 4 Jul 2008 06:04:11 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 036AE8FC17 for ; Fri, 4 Jul 2008 06:04:10 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so985249wfg.7 for ; Thu, 03 Jul 2008 23:04:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=lJDA/UjCJQbH1+DpcvwNWBQpYXxqJ4qEBVgf9hpt2WQ=; b=rmAV7BDwUp50ReK+EVRayG10w1kky4E8Uir0/lTXxmbTGBRGF/sWzWDIbir59sOrCk WAXiO1DPF6quFVRscVeaiJ6hgU1xmiUWvDLs54wAO2EmqwKGx9dnDH91KAAuDGVhMn7w FBRs9FDQ5FJsi/IAy5t42Rc49BA/2ZCfSJ59c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=poX9JP+47Vce0vvJZ2IrwurFHM3U9SjOyC/+3sxH3HQeoFDt+3oDrAMTSxS8J6aRHU QNNcBmM3DzUCBLtHCOxhf0GejjfQEuL1Aa9RYkM+o8jnWY1IwKOZWL17zPfDMpciaarg fxLEMK9TACMzkdK2FMmJAjIQsVQLpnB3tKXMc= Received: by 10.142.240.9 with SMTP id n9mr115722wfh.79.1215151450208; Thu, 03 Jul 2008 23:04:10 -0700 (PDT) Received: by 10.142.107.20 with HTTP; Thu, 3 Jul 2008 23:04:10 -0700 (PDT) Message-ID: <784966050807032304x48b575d3jddfe3844d7196b38@mail.gmail.com> Date: Thu, 3 Jul 2008 23:04:10 -0700 From: "Rob Lytle" To: "Greg Black" In-Reply-To: <784966050807032258n230bc0bx461b652c8ae6da71@mail.gmail.com> MIME-Version: 1.0 References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> <784966050807032258n230bc0bx461b652c8ae6da71@mail.gmail.com> X-Mailman-Approved-At: Fri, 04 Jul 2008 10:58:20 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 06:04:11 -0000 On Thu, Jul 3, 2008 at 10:58 PM, Rob Lytle wrote: > > > On Thu, Jul 3, 2008 at 10:06 PM, Greg Black > wrote: > >> On 2008-07-03, Rob Lytle wrote: >> >> > > You can get rid of the nag screens by putting "BATCH=yes" into >> > > /etc/make.conf. (Not that this negates your other points.) >> > >> > What the hell does "yes" mean? That all option boxes are checked, or >> none >> > at all? I have never seen this explained anywhere. >> >> Instead of all this vociferous whining, how about just doing a bit of >> reading of the documentation? The ports(7) page might be a place to >> start. >> > > That would have been wonderful, groovy, etc if I had known there was a > ports page. Rob. > And another thing, just because FreeBSD is not perfect, don't blame it on me or use derogatory language. I'm not perfect either and I deserve to be treated with respect. Some day someone will search the archives and find this thread, answering their problem so they don't have to go through this miserable process like I have. It makes me less likely to use the mailing lists, more likely to delete the FreeBSD partition, and install OpenBSD which has impeccable documentation. Rob. > > > -- > ---------------------------------------------------------- > http://www.youtube.com/user/whiteflluffyclouds > (Ham radio videos) > -- ---------------------------------------------------------- http://www.youtube.com/user/whiteflluffyclouds (Ham radio videos) From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 07:06:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A02111065671 for ; Fri, 4 Jul 2008 07:06:26 +0000 (UTC) (envelope-from aggelidis.news@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6A1DB8FC0A for ; Fri, 4 Jul 2008 07:06:26 +0000 (UTC) (envelope-from aggelidis.news@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1001053wfg.7 for ; Fri, 04 Jul 2008 00:06:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=pem+L5XDpIBk9KvF08KA1eUlZqC5m4bl4eCa8fvHZG0=; b=Rxk5K/IZtza60TFqx6nL88Lh5aABapUcKHMKAipVq6wjTXomZuGzzVXBXNXuH8nEVr 9gx86hebBFUPK+KR+0ZOgdw7SDt1izLtgHHKx8g7Nn1UasvnIa609luU5ZSlrDUD2yuY 8McFjiIUcVDx6sDsKjiDqYozvvRNx8uNNOw7o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Zi5ylgnmFqLPpspnB67WLYfHkCnz44bZ8GA825YYWQ+14ily9qdqB38BeVuCG5z2aR 1tU46an0bQdbIU/kv5a8P/04iVCab6L86uNur89ZSDVoWxGTWVW6QXN9Yy8SnD925exh VFNoD0a0eOWLzLXr9bo3jHGKxItTWmqq3GgFU= Received: by 10.142.53.19 with SMTP id b19mr117601wfa.167.1215153517294; Thu, 03 Jul 2008 23:38:37 -0700 (PDT) Received: by 10.143.10.10 with HTTP; Thu, 3 Jul 2008 23:38:37 -0700 (PDT) Message-ID: <30fc78250807032338p2388be7ax56e1ae38aaafadd8@mail.gmail.com> Date: Fri, 4 Jul 2008 09:38:37 +0300 From: "Aggelidis Nikos" To: freebsd-hackers@freebsd.org In-Reply-To: <486DB3CB.9000906@infoweapons.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> <486DB3CB.9000906@infoweapons.com> X-Mailman-Approved-At: Fri, 04 Jul 2008 10:58:30 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 07:06:26 -0000 > I'm sorry I started a kind of flame war. All I wanted was two things: 1. > CD's that installed without being switched in and out dozens of times. That > was fixed by the suggestion of using a DVD. I didn't even know the DVD > install existed, but will do that next time. > I also had the same problem {cd switching} to get around it, i created an installation DVD with all the contents of cd1-2-3. You can find such guide > I can speed the process by copying all of the packages > from CD to my system (/usr/ports/packages/All). That way, only ports > that have been updated since the release will be downloaded and I only > have to change CDs a couple of times. > i hadn't thought of this, seems like a nice trick... Isn't it possible that the advice given in these threads find its way into the handbook? {i use freebsd for less than a month, so if this is a stupid suggestion, please ignore it :) } -nicolas From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:14:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5F9F1065676; Fri, 4 Jul 2008 12:14:38 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 74AC58FC18; Fri, 4 Jul 2008 12:14:38 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 4F08E2085; Fri, 4 Jul 2008 14:14:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Rob Lytle" References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> Date: Fri, 04 Jul 2008 14:14:35 +0200 In-Reply-To: <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> (Rob Lytle's message of "Thu\, 3 Jul 2008 21\:26\:16 -0700") Message-ID: <868wwhhmms.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:14:38 -0000 "Rob Lytle" writes: > i strongly disagree with using ports for huge packages. I don't have the > time to waste compiling. Plus, you are presented with numerous nag scree= ns > so you have to babysit the whole process. This is why there are precompiled packages on ftp.freebsd.org which you can install with 'pkg_add -r'. You can install them from any FTP mirror, actually; just point PACKAGEROOT at the mirror: export PACKAGEROOT=3Dftp://ftp.no.freebsd.org DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:17:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AD511065677; Fri, 4 Jul 2008 12:17:58 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id E84278FC17; Fri, 4 Jul 2008 12:17:57 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KEkEe-0004Zi-3l; Fri, 04 Jul 2008 12:17:56 +0000 Message-ID: <486E14F2.3060906@psg.com> Date: Fri, 04 Jul 2008 21:17:54 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <868wwhhmms.fsf@ds4.des.no> In-Reply-To: <868wwhhmms.fsf@ds4.des.no> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Rob Lytle Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:17:58 -0000 > This is why there are precompiled packages on ftp.freebsd.org which you > can install with 'pkg_add -r'. You can install them from any FTP > mirror, actually; just point PACKAGEROOT at the mirror: why isn't this stuff in the docs? oh, it is! silly me. is the problem that there are just too much doc or two little reading? From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:31:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2981A1065671 for ; Fri, 4 Jul 2008 12:31:52 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id ECB458FC14 for ; Fri, 4 Jul 2008 12:31:51 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1086567wfg.7 for ; Fri, 04 Jul 2008 05:31:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=9aH/q0QJNNYiupRJeKoLC4BQ+r4Gs9k0xzRYss6PTGc=; b=ZDO/nwfnwsxyIjwPcQrRBNu/w7Uk7VFmSAtfFa0UmfeX9qOqsIrUxr6lsdNjGo3UiE wuDudwZf3+1VyL7MvvslhAPbDfEXdSUJB2O9o5DgU93o3iieTA+CUxtt+L4JfXq2GDxe 3Uag7EppLhoEIbs5b+Gv2dZz2UguczbrUflmU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MOzGnxA8vdYG+UXAhwWjN7TskGA8cOXXnRSNmyXI+BGVaRHXCa4LchmLrEcC/WbgDR u/EGDJ6WRVGcNxmT7CgI95oaVAJ/yyUy0FMxUZ1mkHlOg5TDSr5c1LV7m27BtRL8QGaE TRuQ0DeVYBEsNLFH3xVlHUHGOHkDudK6/8AOM= Received: by 10.142.173.8 with SMTP id v8mr224458wfe.63.1215174711636; Fri, 04 Jul 2008 05:31:51 -0700 (PDT) Received: by 10.142.231.8 with HTTP; Fri, 4 Jul 2008 05:31:51 -0700 (PDT) Message-ID: <3a142e750807040531k27938f0ay9bd9923ec57f3f1@mail.gmail.com> Date: Fri, 4 Jul 2008 14:31:51 +0200 From: "Paul B. Mahol" To: "Randy Bush" In-Reply-To: <486E14F2.3060906@psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <868wwhhmms.fsf@ds4.des.no> <486E14F2.3060906@psg.com> Cc: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , freebsd-current@freebsd.org, Rob Lytle , freebsd-hackers@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:31:52 -0000 On 7/4/08, Randy Bush wrote: >> This is why there are precompiled packages on ftp.freebsd.org which you >> can install with 'pkg_add -r'. You can install them from any FTP >> mirror, actually; just point PACKAGEROOT at the mirror: > > why isn't this stuff in the docs? oh, it is! silly me. is the problem > that there are just too much doc or two little reading? > > It is in pkg_add(1), If you are talking about handbook only PACKAGESITE is documented: should get fixed. > _______________________________________________ > 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" > From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:32:40 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38C9C1065670; Fri, 4 Jul 2008 12:32:40 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id D78448FC12; Fri, 4 Jul 2008 12:32:39 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m64CVulE033146; Fri, 4 Jul 2008 06:31:56 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 04 Jul 2008 06:33:48 -0600 (MDT) Message-Id: <20080704.063348.-1967689426.imp@bsdimp.com> To: ed@80386.nl From: "M. Warner Losh" In-Reply-To: <20080702190901.GS14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org, freebsd-current@FreeBSD.org, philip@FreeBSD.org Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:32:40 -0000 In message: <20080702190901.GS14567@hoeg.nl> Ed Schouten writes: : - Not all drivers have been ported to the new TTY layer yet. These : drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), : uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), : umodem(4), dcons(4). I have cy hardware available. I also have uftdi and umodem hardware. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:36:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17FD61065673; Fri, 4 Jul 2008 12:36:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B46968FC1B; Fri, 4 Jul 2008 12:36:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m64CZ3ud033182; Fri, 4 Jul 2008 06:35:03 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 04 Jul 2008 06:36:55 -0600 (MDT) Message-Id: <20080704.063655.-1977529554.imp@bsdimp.com> To: ed@80386.nl From: "M. Warner Losh" In-Reply-To: <20080703205220.GW14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: peterjeremy@optushome.com.au, freebsd-current@freebsd.org, arch@freebsd.org Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:36:15 -0000 In message: <20080703205220.GW14567@hoeg.nl> Ed Schouten writes: : > cy(4), digi(4), rp(4), rc(4), si(4). : : Who actually owns one of these devices? If you do, please contact me. If : I didn't make myself clear enough: I *am* willing to (assist in : porting|port) these drivers. I can send you cy(4) hardware (both PCI and ISA) if you'd like. I have no time, however, to assist in the porting. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 12:36:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAFAA10656EB; Fri, 4 Jul 2008 12:36:23 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 89F638FC2B; Fri, 4 Jul 2008 12:36:23 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m64CXlbI033174; Fri, 4 Jul 2008 06:33:47 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 04 Jul 2008 06:35:40 -0600 (MDT) Message-Id: <20080704.063540.1210476607.imp@bsdimp.com> To: xcllnt@mac.com From: "M. Warner Losh" In-Reply-To: <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> References: <20080703205220.GW14567@hoeg.nl> <486D4006.2050303@freebsd.org> <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, sam@freebsd.org, freebsd-current@freebsd.org, ed@80386.nl Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 12:36:23 -0000 In message: <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> Marcel Moolenaar writes: : : On Jul 3, 2008, at 2:09 PM, Sam Leffler wrote: : : >> But I just got told sio(4) is required for pc98, because uart(4) is : >> not : >> supported there. This means I'll seriously consider porting sio(4) : >> one : >> of these days. It's no biggie, even though I think someone could : >> better : >> take the effort to extend uart(4). : >> : > : > I would suggest first investigating how difficult it is to port uart : > to pc98. Given that we're broadening our platform support having a : > single serial driver seems preferable. : : I looked into it in 2003 but since I don't have any hardware, : I wasn't the one able to do it. I think the fundamental problem : is that the BRG is not part of the UART itself and needs a : separate handle or even (tag, handle) pair to access. That's as : far as I know the only big thing about the work. : : For me not having access to the hardware is a showstopper for : looking into it myself. Do you need physical access? I have a pc98 machine I can put back on the network. It has the 8251 chip in it. It also has a 16550 part as well since it is a later model which had both... I believe that uart works for the 16550 part, but haven't tried it lately... Warner From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 13:12:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6AD1106567A; Fri, 4 Jul 2008 13:12:53 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from watery.cc.kogakuin.ac.jp (watery.cc.kogakuin.ac.jp [133.80.152.80]) by mx1.freebsd.org (Postfix) with ESMTP id 814268FC2F; Fri, 4 Jul 2008 13:12:53 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) by watery.cc.kogakuin.ac.jp (unknown) with ESMTP id m64DCSnN088088; Fri, 4 Jul 2008 22:12:28 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Fri, 04 Jul 2008 22:10:43 +0900 (JST) Message-Id: <20080704.221043.226715262.nyan@jp.FreeBSD.org> To: imp@bsdimp.com From: Takahashi Yoshihiro In-Reply-To: <20080704.063540.1210476607.imp@bsdimp.com> References: <486D4006.2050303@freebsd.org> <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> <20080704.063540.1210476607.imp@bsdimp.com> X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ed@80386.nl, arch@freebsd.org, sam@freebsd.org, xcllnt@mac.com, freebsd-current@freebsd.org Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 13:12:54 -0000 In article <20080704.063540.1210476607.imp@bsdimp.com> "M. Warner Losh" writes: > Do you need physical access? I have a pc98 machine I can put back on > the network. It has the 8251 chip in it. It also has a 16550 part as > well since it is a later model which had both... > > I believe that uart works for the 16550 part, but haven't tried it > lately... The uart probably works for some 16550 based devices but does not work for other one like multi-port devices. --- TAKAHASHI Yoshihiro From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 14:41:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE5721065671 for ; Fri, 4 Jul 2008 14:41:39 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id 4C57E8FC0A for ; Fri, 4 Jul 2008 14:41:39 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA03.westchester.pa.mail.comcast.net with comcast id lo151Z0050bG4ec530DB00; Fri, 04 Jul 2008 14:41:38 +0000 Received: from mail.cokane.org ([24.60.133.163]) by OMTA03.westchester.pa.mail.comcast.net with comcast id lqhe1Z0033Xh0XL3Pqheid; Fri, 04 Jul 2008 14:41:38 +0000 X-Authority-Analysis: v=1.0 c=1 a=Q3YcSn_Cu3GmsPkbGIkA:9 a=yQLDE9hupRXwOqXHYPhLv_vgdw4A:4 a=LY0hPdMaydYA:10 a=03jPog0GlyZC3kp9EycA:9 a=L-G6u1T390UKRmHcO0PoAD8W19UA:4 a=rPt6xJ-oxjAA:10 Received: by mail.cokane.org (Postfix, from userid 103) id 20BCE1DB2FA; Fri, 4 Jul 2008 10:41:38 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id E9A071DB2F9; Fri, 4 Jul 2008 10:41:26 -0400 (EDT) From: Coleman Kane To: "M. Warner Losh" In-Reply-To: <20080704.063348.-1967689426.imp@bsdimp.com> References: <20080702190901.GS14567@hoeg.nl> <20080704.063348.-1967689426.imp@bsdimp.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TQtiRStEYAm1HmHL//GI" Organization: FreeBSD Project Date: Fri, 04 Jul 2008 10:39:19 -0400 Message-Id: <1215182359.2446.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Cc: ed@80386.nl, freebsd-current@FreeBSD.org, philip@FreeBSD.org, arch@FreeBSD.org Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 14:41:39 -0000 --=-TQtiRStEYAm1HmHL//GI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2008-07-04 at 06:33 -0600, M. Warner Losh wrote: > In message: <20080702190901.GS14567@hoeg.nl> > Ed Schouten writes: > : - Not all drivers have been ported to the new TTY layer yet. These > : drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), > : uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), > : umodem(4), dcons(4). >=20 > I have cy hardware available. I also have uftdi and umodem hardware. >=20 > Warner FWIW, I think that many mobile phones of the Motorola variety, when used with the USB adapter, will use the umodem driver. I am not sure of other phones though, as I've only gone through about 4 generations of Motorola hardware since ~2003. --=20 Coleman Kane --=-TQtiRStEYAm1HmHL//GI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkhuNhQACgkQcMSxQcXat5doggCePH15vk8CZ5cZsNAuv60Ad+Xx Zu4An3wX4ND7efBxj/6BqPL9+zHGUVGn =eH4C -----END PGP SIGNATURE----- --=-TQtiRStEYAm1HmHL//GI-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 15:40:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7792B1065678; Fri, 4 Jul 2008 15:40:16 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id 5AFD38FC12; Fri, 4 Jul 2008 15:40:16 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id KWS74415; Fri, 04 Jul 2008 08:40:15 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id D60EE4500E; Fri, 4 Jul 2008 08:40:13 -0700 (PDT) To: "Rob Lytle" In-Reply-To: Your message of "Thu, 03 Jul 2008 21:26:16 PDT." <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1215186013_19456P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 04 Jul 2008 08:40:13 -0700 From: "Kevin Oberman" Message-Id: <20080704154013.D60EE4500E@ptavv.es.net> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 15:40:16 -0000 --==_Exmh_1215186013_19456P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 3 Jul 2008 21:26:16 -0700 > From: "Rob Lytle" > > Hi Kevin, > > The sysinstall dependency problem has existed for 10 years, so I doubt that > its unique to me. It has occurred in every installation I have ever done. > > I use portupgrade for all ports. > > i strongly disagree with using ports for huge packages. I don't have the > time to waste compiling. Plus, you are presented with numerous nag screens > so you have to babysit the whole process. Please don't top post! I never said that you should build from ports. I said that you should not use sysinstall to install packages. I said that you can copy the packages from the CDs to /usr/ports/packages/All/ and use 'portinstall -P' to install all of them that are still current and to download those that are not. This simply eliminates all of the disc shuffling. If the nag screens annoy you, use BATCH=yes to build ports with default values. That gives you the same build as the package system uses. -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1215186013_19456P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIbkRdkn3rs5h7N1ERAkVIAKC5/YaClS78ClLsjS/1tI7vSQohPwCfQXJX j/nwfprLN28jz6V9qSeXx9M= =jKtZ -----END PGP SIGNATURE----- --==_Exmh_1215186013_19456P-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 17:23:06 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1E35106564A for ; Fri, 4 Jul 2008 17:23:06 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 835B78FC12 for ; Fri, 4 Jul 2008 17:23:06 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m64GwVUb069258 for ; Fri, 4 Jul 2008 09:58:31 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m64GwOei011364 for ; Fri, 4 Jul 2008 09:58:24 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (sdsl-104-228.dsl.bway.net [216.220.104.228]) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m64GwIS4090785 for ; Fri, 4 Jul 2008 09:58:22 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Fri, 04 Jul 2008 12:58:07 -0400 Message-ID: From: gnn@freebsd.org To: current@freebsd.org User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 862747 - 2805bb7658f9 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: Subject: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 17:23:06 -0000 Hi, I've been working on the following brain teasing (breaking?) problem for about a week now. What I'm seeing is that on large memory machines, those with more than 4G of RAM, the ungzipping/untarring of files fails due to gzip thinking the file is corrupt. The way to reproduce this is: 1) Create a bunch of gzip/tar balls in the 1-20MB range. 2) Reboot FreeBSD 7.0 release 3) Run gzip -t over all the files. I have hundreds of these files to run this over, and a full check takes about 3 hours, but I usually see some form of corruption within the first 20 minutes. Other important factors: 1) This is on very modern, 2P/4Core (8 cores total) hardware 2) The disks are 1TB SATA set up in JBOD. 3) The machines have 16G of RAM. 4) Corruption is seen only after a reboot, if the machines continue to run corruption is never seen again, until another reboot. 5) The systems are all Xeon running amd64 6) The disk controller is an AMCC 9650, but we do see this very rarely with the on board controlller. 7) All boards are http://www.supermicro.com/products/motherboard/Xeon1333/5400/X7DWU.cfm 8) All machines have 3 1TB drives. 9) The corruption is in 4K chunks. That is N x 4K. 10) Files are not normally corrupted on disk, but this can happen. I have already tried a few of the obvious things, such as making sure that we sync pages before we shutdown the twa driver. Given what I have seen I believe this is something that happens from startup, and not at shutdown. Thoughts? Best, George From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 18:19:58 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 131A5106567D; Fri, 4 Jul 2008 18:19:58 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3B0F58FC15; Fri, 4 Jul 2008 18:19:56 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <486E69CC.50205@FreeBSD.org> Date: Fri, 04 Jul 2008 20:19:56 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: gnn@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 18:19:58 -0000 gnn@freebsd.org wrote: > Hi, > > I've been working on the following brain teasing (breaking?) problem > for about a week now. What I'm seeing is that on large memory > machines, those with more than 4G of RAM, the ungzipping/untarring of > files fails due to gzip thinking the file is corrupt. The way to > reproduce this is: > > 1) Create a bunch of gzip/tar balls in the 1-20MB range. > 2) Reboot FreeBSD 7.0 release > 3) Run gzip -t over all the files. > > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. > > Other important factors: > > 1) This is on very modern, 2P/4Core (8 cores total) hardware > 2) The disks are 1TB SATA set up in JBOD. > 3) The machines have 16G of RAM. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. > 5) The systems are all Xeon running amd64 > 6) The disk controller is an AMCC 9650, but we do see this very rarely > with the on board controlller. > 7) All boards are As a negative data point, I have a number of 2*4 core amd64 systems with 8GB of RAM and ATA disks that do not see data corruption (at boot or after it). Kris From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 19:10:44 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81372106568A for ; Fri, 4 Jul 2008 19:10:44 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 45C698FC14 for ; Fri, 4 Jul 2008 19:10:44 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 87CFE5B4B; Fri, 4 Jul 2008 12:10:43 -0700 (PDT) To: gnn@freebsd.org In-reply-to: Your message of "Fri, 04 Jul 2008 12:58:07 EDT." Date: Fri, 04 Jul 2008 12:10:43 -0700 From: Bakul Shah Message-Id: <20080704191043.87CFE5B4B@mail.bitblocks.com> Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 19:10:44 -0000 On Fri, 04 Jul 2008 12:58:07 EDT gnn@freebsd.org wrote: > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. > ... > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. This sounds like a hardware problem.... May be heat related or due to a marginal power supply? Try using a beefier supply on one of the systems or removing something to reduce load. Or increase the load by making disks do lots of seeking while you are running unzip and running other things at the same time. To isolate heat related problems we used to blow cold air (or hot air) on suspected components and see if the problem goes away or gets worse. From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 19:21:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BE68106567A; Fri, 4 Jul 2008 19:21:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0B89B8FC0C; Fri, 4 Jul 2008 19:21:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m64JLk0Y068377; Fri, 4 Jul 2008 15:21:47 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 4 Jul 2008 15:21:25 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807041521.25711.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Fri, 04 Jul 2008 15:21:47 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7638/Fri Jul 4 07:41:46 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: gnn@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 19:21:54 -0000 On Friday 04 July 2008 12:58:07 pm gnn@freebsd.org wrote: > Hi, > > I've been working on the following brain teasing (breaking?) problem > for about a week now. What I'm seeing is that on large memory > machines, those with more than 4G of RAM, the ungzipping/untarring of > files fails due to gzip thinking the file is corrupt. The way to > reproduce this is: > > 1) Create a bunch of gzip/tar balls in the 1-20MB range. > 2) Reboot FreeBSD 7.0 release > 3) Run gzip -t over all the files. > > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. > > Other important factors: > > 1) This is on very modern, 2P/4Core (8 cores total) hardware > 2) The disks are 1TB SATA set up in JBOD. > 3) The machines have 16G of RAM. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. > 5) The systems are all Xeon running amd64 > 6) The disk controller is an AMCC 9650, but we do see this very rarely > with the on board controlller. If this is one of the ATA controllers where it tries to use 63k transfers (126 * DEV_BSIZE) instead of 64k, then change it to 32k (64 * DEV_BSIZE). W/o this fix I see massive data corruption (couldn't even build a kernel with the fix, had to reinstall the box) on HT1000 ATA chipsets. Crashdumps also don't seem to work reliably w/o changing that. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 19:31:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2145A106564A for ; Fri, 4 Jul 2008 19:31:45 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.81]) by mx1.freebsd.org (Postfix) with ESMTP id 062598FC16 for ; Fri, 4 Jul 2008 19:31:44 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp017-bge351000.mac.com (asmtp017-bge351000 [10.150.69.80]) by smtpoutm.mac.com (Xserve/smtpout018/MantshX 4.0) with ESMTP id m64JVi4I002742 for ; Fri, 4 Jul 2008 12:31:44 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp017.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3H00LX1Y8VB880@asmtp017.mac.com> for freebsd-current@freebsd.org; Fri, 04 Jul 2008 12:31:44 -0700 (PDT) Message-id: <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> From: Marcel Moolenaar To: Dmitry Morozovsky In-reply-to: <20080704135827.H35668@woozle.rinet.ru> Date: Fri, 04 Jul 2008 12:31:41 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> X-Mailer: Apple Mail (2.926) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 19:31:45 -0000 On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: > doesn't splitting uart out of kernel broke serial console? Last time > I checked > it did. Yes, it does. The serial console is setup/initialized and used before pre-loaded modules are linked and/or usable. We don't have the support in place that allows you to boot without console until pre-loaded modules are initialized, at which time add a low-level console device is setup. It's not that hard to do, I think. So, currently low-level console drivers, such as dcons(4), sio(4) and uart(4) need to be compiled into the kernel. Consequently any devices/busses to which any of these can attach must be compiled into the kernel as well. Of these acpi(4) and puc(4) are good examples. acpi(4) is a good example because we use hints to work around the issue and have sio(4) attach to isa(4) instead... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 19:42:37 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 069F01065677; Fri, 4 Jul 2008 19:42:37 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.69]) by mx1.freebsd.org (Postfix) with ESMTP id DB2EC8FC12; Fri, 4 Jul 2008 19:42:36 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp016-bge351000.mac.com (asmtp016-bge351000 [10.150.69.79]) by smtpoutm.mac.com (Xserve/smtpout006/MantshX 4.0) with ESMTP id m64JgafL025753; Fri, 4 Jul 2008 12:42:36 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3H00LASYQZWJ90@asmtp016.mac.com>; Fri, 04 Jul 2008 12:42:36 -0700 (PDT) Message-id: From: Marcel Moolenaar To: "M. Warner Losh" In-reply-to: <20080704.063540.1210476607.imp@bsdimp.com> Date: Fri, 04 Jul 2008 12:42:35 -0700 References: <20080703205220.GW14567@hoeg.nl> <486D4006.2050303@freebsd.org> <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> <20080704.063540.1210476607.imp@bsdimp.com> X-Mailer: Apple Mail (2.926) Cc: arch@freebsd.org, sam@freebsd.org, freebsd-current@freebsd.org, ed@80386.nl Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 19:42:37 -0000 On Jul 4, 2008, at 5:35 AM, M. Warner Losh wrote: > : I looked into it in 2003 but since I don't have any hardware, > : I wasn't the one able to do it. I think the fundamental problem > : is that the BRG is not part of the UART itself and needs a > : separate handle or even (tag, handle) pair to access. That's as > : far as I know the only big thing about the work. > : > : For me not having access to the hardware is a showstopper for > : looking into it myself. > > Do you need physical access? No, not at all. As long as the USART is connected to another UART that I can access and as long as I can load/unload the uart(4) module, I should be able to write the support for it. Even only restricted sudo(1) should be fine. > I have a pc98 machine I can put back on > the network. It has the 8251 chip in it. It also has a 16550 part as > well since it is a later model which had both... Perfect. A null-modem cable between the two of them and I should be all set. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 19:50:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1161106567A; Fri, 4 Jul 2008 19:50:33 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.82]) by mx1.freebsd.org (Postfix) with ESMTP id 852D18FC25; Fri, 4 Jul 2008 19:50:33 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp019-bge351000.mac.com (asmtp019-bge351000 [10.150.69.82]) by smtpoutm.mac.com (Xserve/smtpout019/MantshX 4.0) with ESMTP id m64JoXrA022517; Fri, 4 Jul 2008 12:50:33 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3H00DT3Z48Q020@asmtp019.mac.com>; Fri, 04 Jul 2008 12:50:33 -0700 (PDT) Message-id: <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> From: Marcel Moolenaar To: Takahashi Yoshihiro In-reply-to: <20080704.221043.226715262.nyan@jp.FreeBSD.org> Date: Fri, 04 Jul 2008 12:50:31 -0700 References: <486D4006.2050303@freebsd.org> <993E865A-A426-4036-9E09-A87D7474DE80@mac.com> <20080704.063540.1210476607.imp@bsdimp.com> <20080704.221043.226715262.nyan@jp.FreeBSD.org> X-Mailer: Apple Mail (2.926) Cc: ed@80386.nl, arch@freebsd.org, sam@freebsd.org, imp@bsdimp.com, freebsd-current@freebsd.org Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 19:50:34 -0000 On Jul 4, 2008, at 6:10 AM, Takahashi Yoshihiro wrote: > In article <20080704.063540.1210476607.imp@bsdimp.com> > "M. Warner Losh" writes: > >> Do you need physical access? I have a pc98 machine I can put back on >> the network. It has the 8251 chip in it. It also has a 16550 part >> as >> well since it is a later model which had both... >> >> I believe that uart works for the 16550 part, but haven't tried it >> lately... > > The uart probably works for some 16550 based devices but does not work > for other one like multi-port devices. The design principle of uart(4) is that it does not know about multi-port hardware. It controls a single serial port only. For multi-port hardware you must have multiple nodes on a bus or use an umbrella driver, such as puc(4), quicc(4) or scc(4). Those drivers provide attachments for every port. I suspect that support for multi-port devices is not to hard to do on pc98... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:01:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25A131065672 for ; Fri, 4 Jul 2008 21:01:24 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id D35F28FC0C for ; Fri, 4 Jul 2008 21:01:23 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1KEs1W-0000Mz-A0; Fri, 04 Jul 2008 23:36:54 +0300 Message-ID: <486E89E0.8010301@icyb.net.ua> Date: Fri, 04 Jul 2008 23:36:48 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.14 (X11/20080615) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <889.1203600472@critter.freebsd.dk> <47CC55B0.4020607@icyb.net.ua> In-Reply-To: <47CC55B0.4020607@icyb.net.ua> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: newfs_msdos and dvd-ram (fwsectors, fwheads) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:01:24 -0000 on 03/03/2008 21:46 Andriy Gapon said the following: > on 21/02/2008 15:27 Poul-Henning Kamp said the following: >> In message <47BD6F39.7080105@icyb.net.ua>, Andriy Gapon writes: >>> 2) fake those properties in newfs_msdof; >>> benefit: this would help with other physical devices that can host >>> FAT; >> This is the way to do it, but it might make sense to make a library >> routine do it, to get consistent behaviour. BTW, the same issue applies to md device too. I.e. if you would like to create a FAT image in a file, newfs_msdos won't let you. > I opened a PR for this approach in a simple form. > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/121182 > > What could be a good place to put thing for re-use/sharing? libutil? -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:06:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D7F7106566C for ; Fri, 4 Jul 2008 21:06:27 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.76]) by mx1.freebsd.org (Postfix) with ESMTP id 405338FC15 for ; Fri, 4 Jul 2008 21:06:26 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp019-bge351000.mac.com (asmtp019-bge351000 [10.150.69.82]) by smtpoutm.mac.com (Xserve/smtpout013/MantshX 4.0) with ESMTP id m64L6QMG015964; Fri, 4 Jul 2008 14:06:26 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3I00D7N2MPQ070@asmtp019.mac.com>; Fri, 04 Jul 2008 14:06:26 -0700 (PDT) Message-id: <80837A4B-A49A-44A4-AFBA-819DD1ED9DD4@mac.com> From: Marcel Moolenaar To: Andriy Gapon In-reply-to: <486E89E0.8010301@icyb.net.ua> Date: Fri, 04 Jul 2008 14:06:25 -0700 References: <889.1203600472@critter.freebsd.dk> <47CC55B0.4020607@icyb.net.ua> <486E89E0.8010301@icyb.net.ua> X-Mailer: Apple Mail (2.926) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: newfs_msdos and dvd-ram (fwsectors, fwheads) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:06:27 -0000 On Jul 4, 2008, at 1:36 PM, Andriy Gapon wrote: > on 03/03/2008 21:46 Andriy Gapon said the following: >> on 21/02/2008 15:27 Poul-Henning Kamp said the following: >>> In message <47BD6F39.7080105@icyb.net.ua>, Andriy Gapon writes: >>>> 2) fake those properties in newfs_msdof; >>>> benefit: this would help with other physical devices that can host >>>> FAT; >>> This is the way to do it, but it might make sense to make a library >>> routine do it, to get consistent behaviour. > > BTW, the same issue applies to md device too. > I.e. if you would like to create a FAT image in a file, newfs_msdos > won't let you. > >> I opened a PR for this approach in a simple form. >> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/121182 >> What could be a good place to put thing for re-use/sharing? libutil? Note that this problem is already solved with GPart. As long as you have some partitioning scheme on the media, GPart will synthesize CHS parameters. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:12:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8EC31065671 for ; Fri, 4 Jul 2008 21:12:49 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0CF8FC0C for ; Fri, 4 Jul 2008 21:12:48 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m64LCl1X097432; Sat, 5 Jul 2008 01:12:47 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 5 Jul 2008 01:12:47 +0400 (MSD) From: Dmitry Morozovsky To: Marcel Moolenaar In-Reply-To: <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> Message-ID: <20080705011154.G97379@woozle.rinet.ru> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sat, 05 Jul 2008 01:12:47 +0400 (MSD) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:12:49 -0000 On Fri, 4 Jul 2008, Marcel Moolenaar wrote: MM> > doesn't splitting uart out of kernel broke serial console? Last time I MM> > checked MM> > it did. MM> MM> Yes, it does. The serial console is setup/initialized and MM> used before pre-loaded modules are linked and/or usable. MM> We don't have the support in place that allows you to boot MM> without console until pre-loaded modules are initialized, MM> at which time add a low-level console device is setup. MM> It's not that hard to do, I think. MM> MM> So, currently low-level console drivers, such as dcons(4), MM> sio(4) and uart(4) need to be compiled into the kernel. MM> Consequently any devices/busses to which any of these can MM> attach must be compiled into the kernel as well. Of these MM> acpi(4) and puc(4) are good examples. acpi(4) is a good MM> example because we use hints to work around the issue and MM> have sio(4) attach to isa(4) instead... Well, than, what is the reason to keep puc(4) out of GENERIC then? ;-P Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:31:45 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5754E106567A for ; Fri, 4 Jul 2008 21:31:45 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.swip.net [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id DADF28FC14 for ; Fri, 4 Jul 2008 21:31:44 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=c6BnHM9TFBspsvL6eGoA:9 a=ejmT3T01ZoOlCTrhhJEdPEFQvR4A:4 a=lRjT1wxQ3FAA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 824222574; Fri, 04 Jul 2008 23:31:42 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 4 Jul 2008 23:33:15 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> In-Reply-To: <20080703152551.GA73103@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807042333.17859.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:31:45 -0000 On Thursday 03 July 2008, Luigi Rizzo wrote: > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > Luigi Rizzo wrote: > > > There was a discussion back in september about adding > > > support for basic CDC tty devices in umodem.c. > > > This lets you talk to a number of usb devices built around > > > microcontrollers (e.g. Atmel), and puts us on par with > > > Linux and Windows in terms of supporting these devices. > > > > > > Because this simply requires the small patch below to the > > > probe/attach routine, so if there are no objections I plan to add > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > few days. What about flow control? Is flow control required for these devices? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:34:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86202106567D for ; Fri, 4 Jul 2008 21:34:05 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 087BB8FC27 for ; Fri, 4 Jul 2008 21:34:04 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m64LY3mC097870; Sat, 5 Jul 2008 01:34:03 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 5 Jul 2008 01:34:03 +0400 (MSD) From: Dmitry Morozovsky To: Marcel Moolenaar In-Reply-To: <3F7F280F-C3ED-4E2E-9865-66A11FC3F03F@mac.com> Message-ID: <20080705013317.D97379@woozle.rinet.ru> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> <20080705011154.G97379@woozle.rinet.ru> <3F7F280F-C3ED-4E2E-9865-66A11FC3F03F@mac.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sat, 05 Jul 2008 01:34:03 +0400 (MSD) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:34:05 -0000 On Fri, 4 Jul 2008, Marcel Moolenaar wrote: MM> It's in GENERIC on ia64 :-) MM> MM> If no one has any strong objections, I'll add puc(4) to GENERIC MM> for all platforms. The most obvious decision, I hope! ;-P Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:54:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCDF81065677 for ; Fri, 4 Jul 2008 21:54:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 445448FC16 for ; Fri, 4 Jul 2008 21:54:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m64Ls0I8069516; Fri, 4 Jul 2008 17:54:01 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 4 Jul 2008 17:33:24 -0400 User-Agent: KMail/1.9.7 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> In-Reply-To: <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807041733.25301.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Fri, 04 Jul 2008 17:54:01 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7639/Fri Jul 4 14:44:12 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Alexey Shuvaev , Marcel Moolenaar , Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:54:08 -0000 On Friday 04 July 2008 03:31:41 pm Marcel Moolenaar wrote: > > On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: > > > doesn't splitting uart out of kernel broke serial console? Last time > > I checked > > it did. > > Yes, it does. The serial console is setup/initialized and > used before pre-loaded modules are linked and/or usable. > We don't have the support in place that allows you to boot > without console until pre-loaded modules are initialized, > at which time add a low-level console device is setup. > It's not that hard to do, I think. > > So, currently low-level console drivers, such as dcons(4), > sio(4) and uart(4) need to be compiled into the kernel. > Consequently any devices/busses to which any of these can > attach must be compiled into the kernel as well. Of these > acpi(4) and puc(4) are good examples. acpi(4) is a good > example because we use hints to work around the issue and > have sio(4) attach to isa(4) instead... Actually, sio does attach to acpi0. What happens for sio is that the low-level console stuff is just doing bare-bones inb/outb anyway. sioX devices do attach to acpi0 though just fine. Note that in the common case acpi is a module on i386 yet it still manages to work fine. :) Also note that the hints for sio0 aren't actually used, just the 'flags' are applied. Thus, you can have: hint.sio.0.at="isa0" hint.sio.0.port="0x3f8" hint.sio.0.irq="4" hint.sio.0.flags=0x10 But if ACPI lists COM2 before COM1 in the namespace you end up with: sio0 at port 0x2f8 irq 3 (used as serial console!) sio1 at port 0x3f8 irq 4 This is why I wanted to wire devices using the resources in hints so that people would reliably get a serial console on COM1 == sio0 with the existing hints. As it is, people have to engage in far uglier hacks currently since there is no in-tree solution. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:38:16 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8797106564A; Fri, 4 Jul 2008 21:38:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 750158FC17; Fri, 4 Jul 2008 21:38:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id EB33D73087; Fri, 4 Jul 2008 23:39:59 +0200 (CEST) Date: Fri, 4 Jul 2008 23:39:59 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080704213959.GA1706@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807042333.17859.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Fri, 04 Jul 2008 21:56:43 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:38:16 -0000 On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > On Thursday 03 July 2008, Luigi Rizzo wrote: > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > Luigi Rizzo wrote: > > > > There was a discussion back in september about adding > > > > support for basic CDC tty devices in umodem.c. > > > > This lets you talk to a number of usb devices built around > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > Because this simply requires the small patch below to the > > > > probe/attach routine, so if there are no objections I plan to add > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > few days. > > What about flow control? Is flow control required for these devices? the ones I am talking about don't implement any form of flow control. I suppose they would otherwise match the previous check. luigi From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 21:38:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8797106564A; Fri, 4 Jul 2008 21:38:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 750158FC17; Fri, 4 Jul 2008 21:38:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id EB33D73087; Fri, 4 Jul 2008 23:39:59 +0200 (CEST) Date: Fri, 4 Jul 2008 23:39:59 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080704213959.GA1706@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807042333.17859.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Fri, 04 Jul 2008 21:56:52 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 21:38:16 -0000 On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > On Thursday 03 July 2008, Luigi Rizzo wrote: > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > Luigi Rizzo wrote: > > > > There was a discussion back in september about adding > > > > support for basic CDC tty devices in umodem.c. > > > > This lets you talk to a number of usb devices built around > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > Because this simply requires the small patch below to the > > > > probe/attach routine, so if there are no objections I plan to add > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > few days. > > What about flow control? Is flow control required for these devices? the ones I am talking about don't implement any form of flow control. I suppose they would otherwise match the previous check. luigi From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:06:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57FCB106567E; Fri, 4 Jul 2008 22:06:50 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.68]) by mx1.freebsd.org (Postfix) with ESMTP id 2E88D8FC1F; Fri, 4 Jul 2008 22:06:49 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp014-bge351000.mac.com (asmtp014-bge351000 [10.150.69.77]) by smtpoutm.mac.com (Xserve/smtpout005/MantshX 4.0) with ESMTP id m64M6nhO015303; Fri, 4 Jul 2008 15:06:49 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp014.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3I00F355FCOZ10@asmtp014.mac.com>; Fri, 04 Jul 2008 15:06:49 -0700 (PDT) Message-id: <70771DF0-71BB-453F-949E-6A50DD7D0D71@mac.com> From: Marcel Moolenaar To: John Baldwin In-reply-to: <200807041733.25301.jhb@freebsd.org> Date: Fri, 04 Jul 2008 15:06:48 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> <200807041733.25301.jhb@freebsd.org> X-Mailer: Apple Mail (2.926) Cc: Alexey Shuvaev , freebsd-current@freebsd.org, Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:06:50 -0000 On Jul 4, 2008, at 2:33 PM, John Baldwin wrote: > On Friday 04 July 2008 03:31:41 pm Marcel Moolenaar wrote: >> >> On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: >> >>> doesn't splitting uart out of kernel broke serial console? Last time >>> I checked >>> it did. >> >> Yes, it does. The serial console is setup/initialized and >> used before pre-loaded modules are linked and/or usable. >> We don't have the support in place that allows you to boot >> without console until pre-loaded modules are initialized, >> at which time add a low-level console device is setup. >> It's not that hard to do, I think. >> >> So, currently low-level console drivers, such as dcons(4), >> sio(4) and uart(4) need to be compiled into the kernel. >> Consequently any devices/busses to which any of these can >> attach must be compiled into the kernel as well. Of these >> acpi(4) and puc(4) are good examples. acpi(4) is a good >> example because we use hints to work around the issue and >> have sio(4) attach to isa(4) instead... > > Actually, sio does attach to acpi0. What happens for sio is that the > low-level console stuff is just doing bare-bones inb/outb anyway. > sioX > devices do attach to acpi0 though just fine. That's because sio(4) compiles-in the acpi bus attachment even if acpi is not compiled-in. That's cheating :-) -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:27:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 562911065672; Fri, 4 Jul 2008 22:27:15 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 8221A8FC18; Fri, 4 Jul 2008 22:27:14 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=KXcwBZ9UBvJSBEwOnWIA:9 a=JGbGACQMaNx_TWaKKlx5FTPUAzEA:4 a=lRjT1wxQ3FAA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 825515259; Sat, 05 Jul 2008 00:27:12 +0200 From: Hans Petter Selasky To: Luigi Rizzo Date: Sat, 5 Jul 2008 00:28:47 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807050028.48942.hselasky@c2i.net> Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:27:15 -0000 On Friday 04 July 2008, Luigi Rizzo wrote: > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > Luigi Rizzo wrote: > > > > > There was a discussion back in september about adding > > > > > support for basic CDC tty devices in umodem.c. > > > > > This lets you talk to a number of usb devices built around > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > Because this simply requires the small patch below to the > > > > > probe/attach routine, so if there are no objections I plan to add > > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > > few days. > > > > What about flow control? Is flow control required for these devices? > > the ones I am talking about don't implement any form of flow control. > I suppose they would otherwise match the previous check. > > luigi I mean, are you going to upload firmware through these interfaces? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:27:15 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 562911065672; Fri, 4 Jul 2008 22:27:15 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 8221A8FC18; Fri, 4 Jul 2008 22:27:14 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=KXcwBZ9UBvJSBEwOnWIA:9 a=JGbGACQMaNx_TWaKKlx5FTPUAzEA:4 a=lRjT1wxQ3FAA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 825515259; Sat, 05 Jul 2008 00:27:12 +0200 From: Hans Petter Selasky To: Luigi Rizzo Date: Sat, 5 Jul 2008 00:28:47 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807050028.48942.hselasky@c2i.net> Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:27:15 -0000 On Friday 04 July 2008, Luigi Rizzo wrote: > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > Luigi Rizzo wrote: > > > > > There was a discussion back in september about adding > > > > > support for basic CDC tty devices in umodem.c. > > > > > This lets you talk to a number of usb devices built around > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > Because this simply requires the small patch below to the > > > > > probe/attach routine, so if there are no objections I plan to add > > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > > few days. > > > > What about flow control? Is flow control required for these devices? > > the ones I am talking about don't implement any form of flow control. > I suppose they would otherwise match the previous check. > > luigi I mean, are you going to upload firmware through these interfaces? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:31:47 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7156F1065674; Fri, 4 Jul 2008 22:31:47 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id C685C8FC15; Fri, 4 Jul 2008 22:31:46 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=c6BnHM9TFBspsvL6eGoA:9 a=ejmT3T01ZoOlCTrhhJEdPEFQvR4A:4 a=lRjT1wxQ3FAA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 824222574; Fri, 04 Jul 2008 23:31:42 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 4 Jul 2008 23:33:15 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> In-Reply-To: <20080703152551.GA73103@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807042333.17859.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:31:47 -0000 On Thursday 03 July 2008, Luigi Rizzo wrote: > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > Luigi Rizzo wrote: > > > There was a discussion back in september about adding > > > support for basic CDC tty devices in umodem.c. > > > This lets you talk to a number of usb devices built around > > > microcontrollers (e.g. Atmel), and puts us on par with > > > Linux and Windows in terms of supporting these devices. > > > > > > Because this simply requires the small patch below to the > > > probe/attach routine, so if there are no objections I plan to add > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > few days. What about flow control? Is flow control required for these devices? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:32:56 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C4A21065677 for ; Fri, 4 Jul 2008 22:32:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 05C2B8FC16 for ; Fri, 4 Jul 2008 22:32:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m64MWnIW069764; Fri, 4 Jul 2008 18:32:49 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Fri, 4 Jul 2008 18:32:39 -0400 User-Agent: KMail/1.9.7 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <200807041733.25301.jhb@freebsd.org> <70771DF0-71BB-453F-949E-6A50DD7D0D71@mac.com> In-Reply-To: <70771DF0-71BB-453F-949E-6A50DD7D0D71@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807041832.40605.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Fri, 04 Jul 2008 18:32:50 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7639/Fri Jul 4 14:44:12 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Alexey Shuvaev , freebsd-current@freebsd.org, Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:32:56 -0000 On Friday 04 July 2008 06:06:48 pm Marcel Moolenaar wrote: > > On Jul 4, 2008, at 2:33 PM, John Baldwin wrote: > > > On Friday 04 July 2008 03:31:41 pm Marcel Moolenaar wrote: > >> > >> On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: > >> > >>> doesn't splitting uart out of kernel broke serial console? Last time > >>> I checked > >>> it did. > >> > >> Yes, it does. The serial console is setup/initialized and > >> used before pre-loaded modules are linked and/or usable. > >> We don't have the support in place that allows you to boot > >> without console until pre-loaded modules are initialized, > >> at which time add a low-level console device is setup. > >> It's not that hard to do, I think. > >> > >> So, currently low-level console drivers, such as dcons(4), > >> sio(4) and uart(4) need to be compiled into the kernel. > >> Consequently any devices/busses to which any of these can > >> attach must be compiled into the kernel as well. Of these > >> acpi(4) and puc(4) are good examples. acpi(4) is a good > >> example because we use hints to work around the issue and > >> have sio(4) attach to isa(4) instead... > > > > Actually, sio does attach to acpi0. What happens for sio is that the > > low-level console stuff is just doing bare-bones inb/outb anyway. > > sioX > > devices do attach to acpi0 though just fine. > > That's because sio(4) compiles-in the acpi bus attachment > even if acpi is not compiled-in. That's cheating :-) No, that's how new-bus works. :) It's perfectly fine to do that. The attachments get bound at runtime. This is actually an important feature. It's part of why you can have multiple drivers with the same name (e.g. the "generic", "ACPI", and "OpenFirmware" PCI bus drivers). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 23:11:22 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7E841065686; Fri, 4 Jul 2008 23:11:22 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.67]) by mx1.freebsd.org (Postfix) with ESMTP id B5A468FC0A; Fri, 4 Jul 2008 23:11:22 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp021-bge351000.mac.com (asmtp021-bge351000 [10.150.69.84]) by smtpoutm.mac.com (Xserve/smtpout004/MantshX 4.0) with ESMTP id m64NBMv1027595; Fri, 4 Jul 2008 16:11:22 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp021.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3I005GH8EW6S60@asmtp021.mac.com>; Fri, 04 Jul 2008 16:11:22 -0700 (PDT) Message-id: <0D68D063-6654-4E55-ACA9-A0B58C7AA45C@mac.com> From: Marcel Moolenaar To: John Baldwin In-reply-to: <200807041832.40605.jhb@freebsd.org> Date: Fri, 04 Jul 2008 16:11:20 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <200807041733.25301.jhb@freebsd.org> <70771DF0-71BB-453F-949E-6A50DD7D0D71@mac.com> <200807041832.40605.jhb@freebsd.org> X-Mailer: Apple Mail (2.926) Cc: Alexey Shuvaev , freebsd-current@freebsd.org, Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 23:11:23 -0000 On Jul 4, 2008, at 3:32 PM, John Baldwin wrote: > On Friday 04 July 2008 06:06:48 pm Marcel Moolenaar wrote: >> >> On Jul 4, 2008, at 2:33 PM, John Baldwin wrote: >> >>> On Friday 04 July 2008 03:31:41 pm Marcel Moolenaar wrote: >>>> >>>> On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: >>>> >>>>> doesn't splitting uart out of kernel broke serial console? Last >>>>> time >>>>> I checked >>>>> it did. >>>> >>>> Yes, it does. The serial console is setup/initialized and >>>> used before pre-loaded modules are linked and/or usable. >>>> We don't have the support in place that allows you to boot >>>> without console until pre-loaded modules are initialized, >>>> at which time add a low-level console device is setup. >>>> It's not that hard to do, I think. >>>> >>>> So, currently low-level console drivers, such as dcons(4), >>>> sio(4) and uart(4) need to be compiled into the kernel. >>>> Consequently any devices/busses to which any of these can >>>> attach must be compiled into the kernel as well. Of these >>>> acpi(4) and puc(4) are good examples. acpi(4) is a good >>>> example because we use hints to work around the issue and >>>> have sio(4) attach to isa(4) instead... >>> >>> Actually, sio does attach to acpi0. What happens for sio is that >>> the >>> low-level console stuff is just doing bare-bones inb/outb anyway. >>> sioX >>> devices do attach to acpi0 though just fine. >> >> That's because sio(4) compiles-in the acpi bus attachment >> even if acpi is not compiled-in. That's cheating :-) > > No, that's how new-bus works. :) It's perfectly fine to do that. In general, yes. How sio(4) does it, no. sio(4) tied acpi(4) with isa(4) so that if you get the acpi(4) bus attachment when you have isa(4) compiled-in. Consequently, you lose acpi(4) support if you build a kernel without isa(4) support. You also accidentally avoid the problems of having acpi(4) as module. It's a kluge. On ia64 we need acpi(4) but we can't have isa(4), so it's not a generic solution at all. > The > attachments get bound at runtime. This is actually an important > feature. It's an important feature of KOBJ, yes. The point of compiling drivers into the kernel is to get just what you need. Not a bunch of bus attachments you don't want. Modules have pretty much all bus attachments because they need to work with whatever kernel they're loaded in. So, sio(4) is not following the rules in the strictest sense. That's why sio(4) is a bad example, why the problem is not adequately acknowledged and people keep running into the same old problems of things not working "as expected". -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 00:09:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCB701065675; Sat, 5 Jul 2008 00:09:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.freebsd.org (Postfix) with ESMTP id 56B7A8FC1E; Sat, 5 Jul 2008 00:09:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m65098Sd024080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 10:09:08 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m65097FL052692; Sat, 5 Jul 2008 10:09:07 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m65097cw052691; Sat, 5 Jul 2008 10:09:07 +1000 (EST) (envelope-from peter) Date: Sat, 5 Jul 2008 10:09:07 +1000 From: Peter Jeremy To: Rob Lytle Message-ID: <20080705000907.GG29380@server.vk2pj.dyndns.org> References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> <784966050807032258n230bc0bx461b652c8ae6da71@mail.gmail.com> <784966050807032304x48b575d3jddfe3844d7196b38@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L/bWm/e7/ricERqM" Content-Disposition: inline In-Reply-To: <784966050807032304x48b575d3jddfe3844d7196b38@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 00:09:10 -0000 --L/bWm/e7/ricERqM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jul-03 23:04:10 -0700, Rob Lytle wrote: >FreeBSD partition, and install OpenBSD which has impeccable documentation. Having tried to make sense of the OpenBSD carp documentation, I can only assume that is meant as a joke. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --L/bWm/e7/ricERqM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhuu6MACgkQ/opHv/APuIellQCglC0MeOGfpzegnIwXJD8yuqJI aF0Anigv7XNQ0hfbgSmTXTHa0USvfWW2 =QQmr -----END PGP SIGNATURE----- --L/bWm/e7/ricERqM-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:47:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A34A41065677; Fri, 4 Jul 2008 22:47:33 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 604918FC0C; Fri, 4 Jul 2008 22:47:33 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 5B4247308E; Sat, 5 Jul 2008 00:49:18 +0200 (CEST) Date: Sat, 5 Jul 2008 00:49:18 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080704224918.GA2145@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050028.48942.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Sat, 05 Jul 2008 00:19:27 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:47:33 -0000 On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > On Friday 04 July 2008, Luigi Rizzo wrote: > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > Luigi Rizzo wrote: > > > > > > There was a discussion back in september about adding > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > This lets you talk to a number of usb devices built around > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > probe/attach routine, so if there are no objections I plan to add > > > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > > > few days. > > > > > > What about flow control? Is flow control required for these devices? > > > > the ones I am talking about don't implement any form of flow control. > > I suppose they would otherwise match the previous check. > > > > luigi > > I mean, are you going to upload firmware through these interfaces? the OS only know about bytes. are firmware, software, data or random noise. if you want to know whether the sam7 uploader works, yes it does. From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 22:47:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A34A41065677; Fri, 4 Jul 2008 22:47:33 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 604918FC0C; Fri, 4 Jul 2008 22:47:33 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 5B4247308E; Sat, 5 Jul 2008 00:49:18 +0200 (CEST) Date: Sat, 5 Jul 2008 00:49:18 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080704224918.GA2145@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050028.48942.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Sat, 05 Jul 2008 00:19:47 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 22:47:33 -0000 On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > On Friday 04 July 2008, Luigi Rizzo wrote: > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > Luigi Rizzo wrote: > > > > > > There was a discussion back in september about adding > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > This lets you talk to a number of usb devices built around > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > probe/attach routine, so if there are no objections I plan to add > > > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next > > > > > > few days. > > > > > > What about flow control? Is flow control required for these devices? > > > > the ones I am talking about don't implement any form of flow control. > > I suppose they would otherwise match the previous check. > > > > luigi > > I mean, are you going to upload firmware through these interfaces? the OS only know about bytes. are firmware, software, data or random noise. if you want to know whether the sam7 uploader works, yes it does. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 01:50:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8124E1065833 for ; Sat, 5 Jul 2008 01:50:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 230CD8FC0C for ; Sat, 5 Jul 2008 01:50:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m651oM54070905; Fri, 4 Jul 2008 21:50:23 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Fri, 4 Jul 2008 21:08:25 -0400 User-Agent: KMail/1.9.7 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <200807041832.40605.jhb@freebsd.org> <0D68D063-6654-4E55-ACA9-A0B58C7AA45C@mac.com> In-Reply-To: <0D68D063-6654-4E55-ACA9-A0B58C7AA45C@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807042108.25355.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Fri, 04 Jul 2008 21:50:23 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7639/Fri Jul 4 14:44:12 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Alexey Shuvaev , freebsd-current@freebsd.org, Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 01:50:30 -0000 On Friday 04 July 2008 07:11:20 pm Marcel Moolenaar wrote: > > On Jul 4, 2008, at 3:32 PM, John Baldwin wrote: > > > On Friday 04 July 2008 06:06:48 pm Marcel Moolenaar wrote: > >> > >> On Jul 4, 2008, at 2:33 PM, John Baldwin wrote: > >> > >>> On Friday 04 July 2008 03:31:41 pm Marcel Moolenaar wrote: > >>>> > >>>> On Jul 4, 2008, at 2:59 AM, Dmitry Morozovsky wrote: > >>>> > >>>>> doesn't splitting uart out of kernel broke serial console? Last > >>>>> time > >>>>> I checked > >>>>> it did. > >>>> > >>>> Yes, it does. The serial console is setup/initialized and > >>>> used before pre-loaded modules are linked and/or usable. > >>>> We don't have the support in place that allows you to boot > >>>> without console until pre-loaded modules are initialized, > >>>> at which time add a low-level console device is setup. > >>>> It's not that hard to do, I think. > >>>> > >>>> So, currently low-level console drivers, such as dcons(4), > >>>> sio(4) and uart(4) need to be compiled into the kernel. > >>>> Consequently any devices/busses to which any of these can > >>>> attach must be compiled into the kernel as well. Of these > >>>> acpi(4) and puc(4) are good examples. acpi(4) is a good > >>>> example because we use hints to work around the issue and > >>>> have sio(4) attach to isa(4) instead... > >>> > >>> Actually, sio does attach to acpi0. What happens for sio is that > >>> the > >>> low-level console stuff is just doing bare-bones inb/outb anyway. > >>> sioX > >>> devices do attach to acpi0 though just fine. > >> > >> That's because sio(4) compiles-in the acpi bus attachment > >> even if acpi is not compiled-in. That's cheating :-) > > > > No, that's how new-bus works. :) It's perfectly fine to do that. > > In general, yes. How sio(4) does it, no. sio(4) tied acpi(4) > with isa(4) so that if you get the acpi(4) bus attachment > when you have isa(4) compiled-in. Consequently, you lose > acpi(4) support if you build a kernel without isa(4) support. > You also accidentally avoid the problems of having acpi(4) > as module. > > It's a kluge. On ia64 we need acpi(4) but we can't have isa(4), > so it's not a generic solution at all. This is rather minor and easily fixable (< 5 minutes). You could just copy sio_isa.c to sio_acpi.c. > > The > > attachments get bound at runtime. This is actually an important > > feature. > > It's an important feature of KOBJ, yes. The point of compiling > drivers into the kernel is to get just what you need. Not a > bunch of bus attachments you don't want. Modules have pretty > much all bus attachments because they need to work with > whatever kernel they're loaded in. > > So, sio(4) is not following the rules in the strictest sense. > That's why sio(4) is a bad example, why the problem is not > adequately acknowledged and people keep running into the same > old problems of things not working "as expected". This is because acpi is a module. One way this could be fixed is to not put ISA devices enumerated by ACPI on acpi0, but instead of an ACPI-aware ISA bus driver for devices on ISA/LPC that ACPI enumerates. You don't like that idea even though it is probably the cleanest solution. Also, none of that will fix any of the actual problems people have (i.e. COM1 being sio1 and COM2 being sio0 because the BIOS lists them backwards. This happens to work in the non-ACPI case with PNPBIOS due to far grosser hacks that cause PNPBIOS devices to not even be used if hints are present.) -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 01:16:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5604F1065687 for ; Sat, 5 Jul 2008 01:16:34 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 2231F8FC2D for ; Sat, 5 Jul 2008 01:16:33 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1902435rvf.43 for ; Fri, 04 Jul 2008 18:16:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=j9WOPTo5HnH25s+14mqhIgJ0fMY8WzZQvpw9HN5XI5U=; b=m0KOav8eKXgprJB/Z2ANxuQM3iA3vJjsOxQGVeBWxvD8JoByQQEaF7izTIkSs2HxK/ jL3LpdcOtpUO9jowmgHxAt1zikrvpp7ErvLeLIeKqoCKuLiMzL+220a0hAI6/H9kOgJn UcyyTZElRcsSaXFhxVU2g3bwtwQZfBcfWHUCg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pgbqyH+hYKAqRlKUP4oJ2UEW0utKElU860HPswM6SK4P8vk4/0C5NaSqUWw2z1WnTC nB9wG8DlktKtKzfQ40ODD+obSeiNoFFYJxfzPr4cBhyin60RUa9IC33pSswHBdVJRouT eUZnp1mpHRVtruOX/N4XjikYNfdzWmGo/84c0= Received: by 10.141.153.16 with SMTP id f16mr701412rvo.252.1215219032057; Fri, 04 Jul 2008 17:50:32 -0700 (PDT) Received: by 10.141.113.12 with HTTP; Fri, 4 Jul 2008 17:50:32 -0700 (PDT) Message-ID: Date: Sat, 5 Jul 2008 08:50:32 +0800 From: "Xiaofan Chen" To: "Luigi Rizzo" In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> X-Mailman-Approved-At: Sat, 05 Jul 2008 02:46:23 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org, Hans Petter Selasky Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 01:16:34 -0000 On Sat, Jul 5, 2008 at 5:39 AM, Luigi Rizzo wrote: >> What about flow control? Is flow control required for these devices? > > the ones I am talking about don't implement any form of flow control. > I suppose they would otherwise match the previous check. > They are many of this device and they do not have flow control. I got two of them right here. One is for NXP LPC-P2148 and the other is using Microchip PIC18F USB PICs. Last time it was discussed here. http://lists.freebsd.org/pipermail/freebsd-usb/2008-April/004907.html I've tried the lpcusb based generic CDC-ACM device under Linux/Windows/NetBSD successfully but not FreeBSD. Xiaofan From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 01:19:04 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B18D6106567B for ; Sat, 5 Jul 2008 01:19:04 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 7E3EE8FC2A for ; Sat, 5 Jul 2008 01:19:04 +0000 (UTC) (envelope-from xiaofanc@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1902876rvf.43 for ; Fri, 04 Jul 2008 18:19:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=j9WOPTo5HnH25s+14mqhIgJ0fMY8WzZQvpw9HN5XI5U=; b=m0KOav8eKXgprJB/Z2ANxuQM3iA3vJjsOxQGVeBWxvD8JoByQQEaF7izTIkSs2HxK/ jL3LpdcOtpUO9jowmgHxAt1zikrvpp7ErvLeLIeKqoCKuLiMzL+220a0hAI6/H9kOgJn UcyyTZElRcsSaXFhxVU2g3bwtwQZfBcfWHUCg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pgbqyH+hYKAqRlKUP4oJ2UEW0utKElU860HPswM6SK4P8vk4/0C5NaSqUWw2z1WnTC nB9wG8DlktKtKzfQ40ODD+obSeiNoFFYJxfzPr4cBhyin60RUa9IC33pSswHBdVJRouT eUZnp1mpHRVtruOX/N4XjikYNfdzWmGo/84c0= Received: by 10.141.153.16 with SMTP id f16mr701412rvo.252.1215219032057; Fri, 04 Jul 2008 17:50:32 -0700 (PDT) Received: by 10.141.113.12 with HTTP; Fri, 4 Jul 2008 17:50:32 -0700 (PDT) Message-ID: Date: Sat, 5 Jul 2008 08:50:32 +0800 From: "Xiaofan Chen" To: "Luigi Rizzo" In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> X-Mailman-Approved-At: Sat, 05 Jul 2008 02:46:31 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org, Hans Petter Selasky Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 01:19:04 -0000 On Sat, Jul 5, 2008 at 5:39 AM, Luigi Rizzo wrote: >> What about flow control? Is flow control required for these devices? > > the ones I am talking about don't implement any form of flow control. > I suppose they would otherwise match the previous check. > They are many of this device and they do not have flow control. I got two of them right here. One is for NXP LPC-P2148 and the other is using Microchip PIC18F USB PICs. Last time it was discussed here. http://lists.freebsd.org/pipermail/freebsd-usb/2008-April/004907.html I've tried the lpcusb based generic CDC-ACM device under Linux/Windows/NetBSD successfully but not FreeBSD. Xiaofan From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 07:55:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB234106568A; Sat, 5 Jul 2008 07:55:33 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id F401D8FC2B; Sat, 5 Jul 2008 07:55:32 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=6I5d2MoRAAAA:8 a=V26Gi-mhlS2Ubpsm_kIA:9 a=yUohyMil2aWTgK4hbGIA:7 a=AIFCxzttIdze7HAiOTLRrlaUpBUA:4 a=lRjT1wxQ3FAA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 975623465; Sat, 05 Jul 2008 09:55:30 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 5 Jul 2008 09:57:06 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> In-Reply-To: <20080704224918.GA2145@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807050957.07900.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 07:55:33 -0000 On Saturday 05 July 2008, Luigi Rizzo wrote: > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > There was a discussion back in september about adding > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > the next few days. > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > the ones I am talking about don't implement any form of flow control. > > > I suppose they would otherwise match the previous check. > > > > > > luigi > > > > I mean, are you going to upload firmware through these interfaces? > > the OS only know about bytes. > > are firmware, software, data or random noise. > if you want to know whether the sam7 uploader works, yes it does. > _______________________________________________ > 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" Yes, but you know that umodem can drop data, if the buffers overflow ? --HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 07:59:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07E2C106566C for ; Sat, 5 Jul 2008 07:59:19 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8FA8FC1D for ; Sat, 5 Jul 2008 07:59:18 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m657xGoI056874; Sat, 5 Jul 2008 11:59:16 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 5 Jul 2008 11:59:16 +0400 (MSD) From: Dmitry Morozovsky To: Marcel Moolenaar In-Reply-To: <3F7F280F-C3ED-4E2E-9865-66A11FC3F03F@mac.com> Message-ID: <20080705115201.L97379@woozle.rinet.ru> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> <20080705011154.G97379@woozle.rinet.ru> <3F7F280F-C3ED-4E2E-9865-66A11FC3F03F@mac.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sat, 05 Jul 2008 11:59:17 +0400 (MSD) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 07:59:19 -0000 On Fri, 4 Jul 2008, Marcel Moolenaar wrote: MM> > Well, than, what is the reason to keep puc(4) out of GENERIC then? ;-P MM> MM> It's in GENERIC on ia64 :-) MM> MM> If no one has any strong objections, I'll add puc(4) to GENERIC MM> for all platforms. Well, it is actually there, but commented out: marck@woozle:/lh/src.current/sys> grep 'device.*puc' */conf/GENERIC amd64/conf/GENERIC:#device puc i386/conf/GENERIC:#device puc ia64/conf/GENERIC:device puc # Multi I/O cards and multi-channel UARTs sparc64/conf/GENERIC:device puc # Multi-channel uarts sun4v/conf/GENERIC:#device puc # Multi-channel uarts It seems it's in that state from the very beginning (cvs ann/log survery on sys/i386/conf/GENERIC): description: ---------------------------- revision 1.392 date: 2003/09/19 20:04:55; author: joerg; state: Exp; lines: +4 -0 Mention the puc(4) glue driver in a commented-out example so the user of "dumb" PCI-based serial/parallel boards get a hint how to enable them. I wasn't sure about the ia64, pc98, powerpc, and sparc64 archs whether they'd support puc(4) or not. ============================================================================= Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 08:29:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03A7B106564A for ; Sat, 5 Jul 2008 08:29:24 +0000 (UTC) (envelope-from ss.alert@online.no) Received: from mail46.e.nsc.no (mail46.e.nsc.no [193.213.115.46]) by mx1.freebsd.org (Postfix) with ESMTP id 80DFC8FC0A for ; Sat, 5 Jul 2008 08:29:23 +0000 (UTC) (envelope-from ss.alert@online.no) Received: from [192.168.1.115] (ti0034a380-0411.bb.online.no [88.88.10.157]) by mail46.nsc.no (8.13.8/8.13.5) with ESMTP id m657OFn7004528 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Sat, 5 Jul 2008 09:24:16 +0200 (MEST) Message-Id: From: Sverre Svenningsen To: freebsd-current In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Date: Sat, 5 Jul 2008 09:24:15 +0200 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> X-Mailer: Apple Mail (2.926) Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 08:29:24 -0000 On Jul 5, 2008, at 02:50 , Xiaofan Chen wrote: > On Sat, Jul 5, 2008 at 5:39 AM, Luigi Rizzo wrote: >>> What about flow control? Is flow control required for these devices? >> >> the ones I am talking about don't implement any form of flow control. >> I suppose they would otherwise match the previous check. >> > > They are many of this device and they do not have flow control. > I got two of them right here. One is for NXP LPC-P2148 and the other > is using Microchip PIC18F USB PICs. > > Last time it was discussed here. > http://lists.freebsd.org/pipermail/freebsd-usb/2008-April/004907.html > > I've tried the lpcusb based generic CDC-ACM device under > Linux/Windows/NetBSD successfully but not FreeBSD. > > Xiaofan > _______________________________________________ > 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 > " > > Is current@freebsd.org just an alias to freebsd-current@freebsd.org ? I keep getting duplicates of every message belongin to this discussion... Just thought i'd ask so the next guy replying can remove the dupe address from the CC field :) -Sverre From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 08:55:37 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B25310656C3 for ; Sat, 5 Jul 2008 08:55:37 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id B61028FC1D for ; Sat, 5 Jul 2008 08:55:36 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=6I5d2MoRAAAA:8 a=V26Gi-mhlS2Ubpsm_kIA:9 a=yUohyMil2aWTgK4hbGIA:7 a=AIFCxzttIdze7HAiOTLRrlaUpBUA:4 a=lRjT1wxQ3FAA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 975623465; Sat, 05 Jul 2008 09:55:30 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 5 Jul 2008 09:57:06 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> In-Reply-To: <20080704224918.GA2145@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807050957.07900.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 08:55:37 -0000 On Saturday 05 July 2008, Luigi Rizzo wrote: > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > There was a discussion back in september about adding > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > the next few days. > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > the ones I am talking about don't implement any form of flow control. > > > I suppose they would otherwise match the previous check. > > > > > > luigi > > > > I mean, are you going to upload firmware through these interfaces? > > the OS only know about bytes. > > are firmware, software, data or random noise. > if you want to know whether the sam7 uploader works, yes it does. > _______________________________________________ > 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" Yes, but you know that umodem can drop data, if the buffers overflow ? --HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 09:04:47 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 367F51065672 for ; Sat, 5 Jul 2008 09:04:47 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 0C15C8FC0C for ; Sat, 5 Jul 2008 09:04:46 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1987072rvf.43 for ; Sat, 05 Jul 2008 02:04:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=w+bL1XxRLBZxNVcnkJJLAM55IXMy1GE/IYyzb/y5wNE=; b=KekQ/n0WqezPyNsA5GSmoDcAOl+dpWQlynYta8QS82PHKuGGKCd/rtY2NDwAhWGGaw +TKmgMy/myWtBnZtzZa2GOCAWDngqjnwUPLJEdyxQkA0T3G8tJC2dS4YXc6wMg0bkCyw mmeTsglzj3or6jxwFogt3QbmwZhfMc9GG6wr8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=WzEBttBz6B9t/Lb95UBfS6ffyVyEmRtJ/wjWRVV7RqNKM1s/WoE0vB69idbqHcAGUg Ty9OP/mlzww33aFLTA4rzIKxedHdOVSUyOWdpFFVLqgQKYfJaD/NnCo2aOdX1bpL1REF sndG+pIa5VaCA3oWpH7pjWsPcXcDRjNWiPR+0= Received: by 10.114.46.11 with SMTP id t11mr4196782wat.211.1215248686621; Sat, 05 Jul 2008 02:04:46 -0700 (PDT) Received: by 10.115.78.5 with HTTP; Sat, 5 Jul 2008 02:04:46 -0700 (PDT) Message-ID: Date: Sat, 5 Jul 2008 13:04:46 +0400 From: "Vladimir Ermakov" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: wireless access point is don`t scaning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 09:04:47 -0000 Hello after creation access point, she is don`t scaning outputs: ============================================================= # ifconfig -a re0: flags=8843 metric 0 mtu 1500 options=399b ether 00:1e:90:88:92:85 inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active ath0: flags=8843 metric 0 mtu 2290 ether 00:11:6b:63:47:12 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running lo0: flags=8049 metric 0 mtu 16384 inet 127.0.0.1 netmask 0xff000000 wlan0: flags=8843 metric 0 mtu 2290 ether 00:11:6b:63:47:12 inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid ora channel 6 (2437 Mhz 11g) bssid 00:11:6b:63:47:12 country US ecm authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit txpower 18.5 scanvalid 60 protmode CTS wme burst ff dturbo dtimperiod 1 -dfs # ifconfig wlan0 up scan # # uname -a FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Fri Jul 4 20:01:51 MSD 2008 root@:/usr/obj/usr/src/sys/GRAVICAPA i386 ============================================================= messages output: ============================================================= Jul 5 13:02:05 kernel: wlan0: ieee80211_ioctl_scanreq: flags 0x13 duration 0x7fffffff mindwell 0 maxdwell 0 nssid 0 Jul 5 13:02:05 kernel: wlan0: start_scan_locked: active scan, duration 2147483647 mindwell 0 maxdwell 0, desired mode auto, append, nopick, once Jul 5 13:02:05 kernel: wlan0: scan set 6g dwell min 200 max 200 Jul 5 13:02:05 kernel: wlan0: scan_next: chan 6g -> 6g [active, dwell min 200 max 200] Jul 5 13:02:05 kernel: wlan0: send probe req on channel 6 bssid ff:ff:ff:ff:ff:ff ssid "" Jul 5 13:02:05 kernel: wlan0: scan_next: done, [ticks 5242290, dwell min 200 scanend 2152725736] Jul 5 13:02:05 kernel: wlan0: notify scan done ============================================================= please, any solution? /Vladimir Ermakov From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 10:08:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E673D1065677 for ; Sat, 5 Jul 2008 10:08:04 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id B8AF58FC1E for ; Sat, 5 Jul 2008 10:08:04 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1361829wfg.7 for ; Sat, 05 Jul 2008 03:08:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=SGaY2IsikegguKlPw1ppHrtYO95PU0DAOl4s7RpydjI=; b=FKs2JTfF68/0rRTn3za4Qd6DKSPBg6hWRSB70hldQxBn8CIzlz/HyR5gJDB4A5UqjG OWQJhUJBq+pTMZCM+R+37XyDohcUmpwDte1tuPItgKJ0ALwQTYnOd7XiBN4xeq+YWjX1 IbZAG2DnFQJAE86Z5M7nohENYJhtA4ewUAha0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=VJ2wECmJZqGqZ2NuzVBrw5FhJGU4SOsOiTeJsXV3LeNbmRx04ob2oRy5KAaDin/WDd qFKKRBHDamj7SX93XvsuUqX4/WNR7B03KE9An/nOT64ADqAuNPY3x7AplhAfUUHXjYh7 RnNsTpviGKXp8UknMF14ybK7ezWdD/kcVyPYU= Received: by 10.142.212.19 with SMTP id k19mr556244wfg.13.1215252484186; Sat, 05 Jul 2008 03:08:04 -0700 (PDT) Received: by 10.142.231.8 with HTTP; Sat, 5 Jul 2008 03:08:04 -0700 (PDT) Message-ID: <3a142e750807050308s41a6a012sad25eb1e596b6628@mail.gmail.com> Date: Sat, 5 Jul 2008 12:08:04 +0200 From: "Paul B. Mahol" To: "Vladimir Ermakov" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: wireless access point is don`t scaning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 10:08:05 -0000 Correct command is: ifconfig wlan0 list sta everything is clearly explained in ifconfig manual page. On 7/5/08, Vladimir Ermakov wrote: > Hello > > after creation access point, she is don`t scaning > > outputs: > ============================================================= > # ifconfig -a > re0: flags=8843 metric 0 mtu 1500 > > options=399b > ether 00:1e:90:88:92:85 > inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > ath0: flags=8843 metric 0 mtu 2290 > ether 00:11:6b:63:47:12 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > lo0: flags=8049 metric 0 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > wlan0: flags=8843 metric 0 mtu 2290 > ether 00:11:6b:63:47:12 > inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid ora channel 6 (2437 Mhz 11g) bssid 00:11:6b:63:47:12 > country US ecm authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit > TKIP 3:128-bit txpower 18.5 scanvalid 60 protmode CTS wme burst ff > dturbo dtimperiod 1 -dfs > > # ifconfig wlan0 up scan > # > # uname -a > FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Fri Jul 4 20:01:51 MSD > 2008 root@:/usr/obj/usr/src/sys/GRAVICAPA i386 > ============================================================= > > messages output: > ============================================================= > Jul 5 13:02:05 kernel: wlan0: ieee80211_ioctl_scanreq: flags 0x13 > duration 0x7fffffff mindwell 0 maxdwell 0 nssid 0 > Jul 5 13:02:05 kernel: wlan0: start_scan_locked: active scan, > duration 2147483647 mindwell 0 maxdwell 0, desired mode auto, append, > nopick, once > Jul 5 13:02:05 kernel: wlan0: scan set 6g dwell min 200 max 200 > Jul 5 13:02:05 kernel: wlan0: scan_next: chan 6g -> 6g [active, > dwell min 200 max 200] > Jul 5 13:02:05 kernel: wlan0: send probe req on channel 6 bssid > ff:ff:ff:ff:ff:ff ssid "" > Jul 5 13:02:05 kernel: wlan0: scan_next: done, [ticks 5242290, dwell > min 200 scanend 2152725736] > Jul 5 13:02:05 kernel: wlan0: notify scan done > ============================================================= > > please, any solution? > > /Vladimir Ermakov > _______________________________________________ > 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" > From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 12:25:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9C311065678; Sat, 5 Jul 2008 12:25:42 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from watery.cc.kogakuin.ac.jp (watery.cc.kogakuin.ac.jp [133.80.152.80]) by mx1.freebsd.org (Postfix) with ESMTP id 8083D8FC14; Sat, 5 Jul 2008 12:25:42 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) by watery.cc.kogakuin.ac.jp (unknown) with ESMTP id m65CPKSe053473; Sat, 5 Jul 2008 21:25:20 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Sat, 05 Jul 2008 21:24:22 +0900 (JST) Message-Id: <20080705.212422.226755141.nyan@jp.FreeBSD.org> To: xcllnt@mac.com From: Takahashi Yoshihiro In-Reply-To: <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> References: <20080704.063540.1210476607.imp@bsdimp.com> <20080704.221043.226715262.nyan@jp.FreeBSD.org> <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ed@80386.nl, sam@freebsd.org, imp@freebsd.org, freebsd-current@freebsd.org, arch@freebsd.org Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 12:25:42 -0000 In article <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> Marcel Moolenaar writes: > > The uart probably works for some 16550 based devices but does not work > > for other one like multi-port devices. > > The design principle of uart(4) is that it does not know > about multi-port hardware. It controls a single serial > port only. For multi-port hardware you must have multiple > nodes on a bus or use an umbrella driver, such as puc(4), > quicc(4) or scc(4). Those drivers provide attachments for > every port. > > I suspect that support for multi-port devices is not to > hard to do on pc98... Many serial devices on pc98 use indirect I/O space, so resource management is quite complex. Therefore, it may need more work you think. At the starting point, I have added CBus frontend and fixed console support for pc98. http://home.jp.freebsd.org/~nyan/patches/uart_pc98.diff.bz2 --- TAKAHASHI Yoshihiro From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 08:05:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1785106567B; Sat, 5 Jul 2008 08:05:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id A00728FC29; Sat, 5 Jul 2008 08:05:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 61A4073087; Sat, 5 Jul 2008 10:06:49 +0200 (CEST) Date: Sat, 5 Jul 2008 10:06:49 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080705080649.GA7043@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050957.07900.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Sat, 05 Jul 2008 12:34:04 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 08:05:05 -0000 On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Luigi Rizzo wrote: > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > There was a discussion back in september about adding > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > > the next few days. > > > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > > > the ones I am talking about don't implement any form of flow control. > > > > I suppose they would otherwise match the previous check. > > > > > > > > luigi > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > the OS only know about bytes. > > > > are firmware, software, data or random noise. > > if you want to know whether the sam7 uploader works, yes it does. > > _______________________________________________ > > 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" > > Yes, but you know that umodem can drop data, if the buffers overflow ? yes i know. and there is another million things that can go wrong. bye luigi From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 08:05:04 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1785106567B; Sat, 5 Jul 2008 08:05:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id A00728FC29; Sat, 5 Jul 2008 08:05:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 61A4073087; Sat, 5 Jul 2008 10:06:49 +0200 (CEST) Date: Sat, 5 Jul 2008 10:06:49 +0200 From: Luigi Rizzo To: Hans Petter Selasky Message-ID: <20080705080649.GA7043@onelab2.iet.unipi.it> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050957.07900.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Sat, 05 Jul 2008 12:34:12 +0000 Cc: usb@freebsd.org, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 08:05:05 -0000 On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Luigi Rizzo wrote: > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > There was a discussion back in september about adding > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > > the next few days. > > > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > > > the ones I am talking about don't implement any form of flow control. > > > > I suppose they would otherwise match the previous check. > > > > > > > > luigi > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > the OS only know about bytes. > > > > are firmware, software, data or random noise. > > if you want to know whether the sam7 uploader works, yes it does. > > _______________________________________________ > > 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" > > Yes, but you know that umodem can drop data, if the buffers overflow ? yes i know. and there is another million things that can go wrong. bye luigi From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 14:54:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBFC1106567A for ; Sat, 5 Jul 2008 14:54:04 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from dire.wubethiopia.com (j071.v.rootbsd.net [208.79.82.223]) by mx1.freebsd.org (Postfix) with ESMTP id 717548FC16 for ; Sat, 5 Jul 2008 14:54:04 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from rogue.mike.lan (unknown [213.55.67.249]) by dire.wubethiopia.com (Postfix) with ESMTPSA id 787B64FD97AF; Sat, 5 Jul 2008 14:53:55 +0000 (UTC) Message-ID: <486F8C57.9050908@wubethiopia.com> Date: Sat, 05 Jul 2008 17:59:35 +0300 From: Mike Makonnen User-Agent: Thunderbird 2.0.0.12 (X11/20080323) MIME-Version: 1.0 To: Robert Watson References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> In-Reply-To: <20080703092511.T69986@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Lothar Braun , freebsd-current@freebsd.org Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 14:54:05 -0000 Robert Watson wrote: > > For me, it's really about minimizing the time to get to a generic > install from a CD or DVD. Most of the time, I don't do a lot of > customization during the install -- I configure machines using DHCP, I > add most packages later, and I tend to use default disk layouts since my > servers don't multi-boot and the defaults currently seem "reasonable". > > I don't like being asked many more questions than whether or not to > enable sshd, and what to set the root password to. This means that I > find our current distributions menu a bit inefficient (I don't want > sub-menus, I just want checkboxes), and that the inconsistency in the > handling of the space/enter/tab/cursor keys across different libdialog > interfaces in the install is awkward. The current generic and express > installs seem to capture a lot of my desire, in that I can get a box > installed in <5m including actual time to write out the file systems, > which is great. I really don't want to lose this with a new installer :-). That's the route I'm trying to go with the Sysinstall-BSD Installer "mashup." No "submenu hell", no "XYZ distribution" choices, and no extraneous configuration choices. My basic philosophy is that there should be no "Basic", "Expert", or "Custom" modes. There should only be one mode with sensible default choices so that the novice user can simply just click "Next" and the more expert user can modify the default choices and get exactly what he/she wants. Also, the installer's job should only be to install a useable system. Post-installation chores like configuration, adding/removing users, etc should be done by another application. You shouldn't need the installer once you've installed the OS. And oh yeah-- if you can't reliably upgrade from a previous version of the OS, you shouldn't offer the user the option of doing so. Essentially the user only needs to supply 6 things: 1) Where to install to. 2) Where to get installation files from. 3) Network card configuration. 4) Date and Time zone. 5) Hostname. 6)root's password. I'm leaning towards adding a 7th question on whether to enable sshd(8) simply because it's so useful and one of the first things I do after installing a server. Although I didn't want to have the installer setup additional users at first I'm also leaning towards implementing it since enabling sshd(8) without having a non-root user to login as is kinda pointless. Other than that: 1. The stock installation disk should allow the user to easily automate installation (through a configuration file on a flash disk or something). 2. You shouldn't have to edit the source code to make changes to release name, ftp installation sites, etc... 3. Completely divorce the UI from the backend installation logic. So, that all that you need to implement a new UI is boiler plate code to display items sent by the backend and return responses/choices made by the user. Although it needs a few improvements, the BSD Installer pretty much already does this. Status update on the installer I'm woring on: The installer can already install a basic FreeBSD system (including the ports collection) from CD, UFS, or DOS partition. I'm currently working on getting FTP/HTTP/NFS installation to work. Next on my list after that is setting Date and Time Zone. At that stage the installer will be more or less feature-complete, and I can start code cleanup, getting it to work on additional architectures, etc. I had initially intended to include package installation as one of the criteria for feature-completeness, but after reading through this thread I've decided not to use sysinstall's package installation code and instead write one from scratch once I'm happy with the rest of the installer. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 15:22:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 150671065676; Sat, 5 Jul 2008 15:22:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id E09FD8FC20; Sat, 5 Jul 2008 15:22:09 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3587746C50; Sat, 5 Jul 2008 11:22:09 -0400 (EDT) Date: Sat, 5 Jul 2008 16:22:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mike Makonnen In-Reply-To: <486F8C57.9050908@wubethiopia.com> Message-ID: <20080705161614.O19209@fledge.watson.org> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Lothar Braun , freebsd-current@freebsd.org Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 15:22:10 -0000 On Sat, 5 Jul 2008, Mike Makonnen wrote: > The installer can already install a basic FreeBSD system (including the > ports collection) from CD, UFS, or DOS partition. I'm currently working on > getting FTP/HTTP/NFS installation to work. Next on my list after that is > setting Date and Time Zone. At that stage the installer will be more or less > feature-complete, and I can start code cleanup, getting it to work on > additional architectures, etc. I had initially intended to include package > installation as one of the criteria for feature-completeness, but after > reading through this thread I've decided not to use sysinstall's package > installation code and instead write one from scratch once I'm happy with the > rest of the installer. Sounds pretty much in line with what I was looking for. However, I think I would like to see it be a bit more complete than sysinstall in the area of geom partition labeling (concat/strip/raid/encryption), and perhaps also ZFS support. I realize that adds complexity a fair amount, but one of the biggest areas of feature lack in sysinstall today is that you are basically stuck with the original BSD partition structure and UFS, whereas we expect increasing numbers of users to deploy ZFS. We don't have boot support currently, but being able to set up /data as a ZFS file system would be great. Today, people have to do an initial install on, say, a small boot partition and then relabel/deal with the rest of the disk, boot a live CD, or worse, discover they have to repartition, which really fails to expose some of the excellent ease-of-use, auto-configuration, etc, features that we otherwise have in this area. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 15:22:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4214A106564A for ; Sat, 5 Jul 2008 15:22:53 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id EEDA18FC12 for ; Sat, 5 Jul 2008 15:22:52 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from Macintosh-4.local ([10.0.0.194]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m65FMqhp094995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 08:22:52 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <486F91CC.60009@freebsd.org> Date: Sat, 05 Jul 2008 08:22:52 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Vladimir Ermakov References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: wireless access point is don`t scaning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 15:22:53 -0000 Vladimir Ermakov wrote: > Hello > > after creation access point, she is don`t scaning > > outputs: > ============================================================= > # ifconfig -a > re0: flags=8843 metric 0 mtu 1500 > options=399b > ether 00:1e:90:88:92:85 > inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > ath0: flags=8843 metric 0 mtu 2290 > ether 00:11:6b:63:47:12 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > lo0: flags=8049 metric 0 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > wlan0: flags=8843 metric 0 mtu 2290 > ether 00:11:6b:63:47:12 > inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid ora channel 6 (2437 Mhz 11g) bssid 00:11:6b:63:47:12 > country US ecm authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit > TKIP 3:128-bit txpower 18.5 scanvalid 60 protmode CTS wme burst ff > dturbo dtimperiod 1 -dfs > > # ifconfig wlan0 up scan > # > # uname -a > FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Fri Jul 4 20:01:51 MSD > 2008 root@:/usr/obj/usr/src/sys/GRAVICAPA i386 > ============================================================= > > messages output: > ============================================================= > Jul 5 13:02:05 kernel: wlan0: ieee80211_ioctl_scanreq: flags 0x13 > duration 0x7fffffff mindwell 0 maxdwell 0 nssid 0 > Jul 5 13:02:05 kernel: wlan0: start_scan_locked: active scan, > duration 2147483647 mindwell 0 maxdwell 0, desired mode auto, append, > nopick, once > Jul 5 13:02:05 kernel: wlan0: scan set 6g dwell min 200 max 200 > Jul 5 13:02:05 kernel: wlan0: scan_next: chan 6g -> 6g [active, > dwell min 200 max 200] > Jul 5 13:02:05 kernel: wlan0: send probe req on channel 6 bssid > ff:ff:ff:ff:ff:ff ssid "" > Jul 5 13:02:05 kernel: wlan0: scan_next: done, [ticks 5242290, dwell > min 200 scanend 2152725736] > Jul 5 13:02:05 kernel: wlan0: notify scan done > ============================================================= > > please, any solution? The "scan set" lists only channel 6. Looks like you locked down the channel. Sam From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 15:44:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9676F106566C; Sat, 5 Jul 2008 15:44:58 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.79]) by mx1.freebsd.org (Postfix) with ESMTP id 7EFD48FC0C; Sat, 5 Jul 2008 15:44:58 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp016-bge351000.mac.com (asmtp016-bge351000 [10.150.69.79]) by smtpoutm.mac.com (Xserve/smtpout016/MantshX 4.0) with ESMTP id m65Fiw5H002452; Sat, 5 Jul 2008 08:44:58 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3J00NQOIEW4340@asmtp016.mac.com>; Sat, 05 Jul 2008 08:44:58 -0700 (PDT) Message-id: <13CE46CD-EF60-448D-BDC7-CBE274D22FE3@mac.com> From: Marcel Moolenaar To: John Baldwin In-reply-to: <200807042108.25355.jhb@freebsd.org> Date: Sat, 05 Jul 2008 08:44:56 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <200807041832.40605.jhb@freebsd.org> <0D68D063-6654-4E55-ACA9-A0B58C7AA45C@mac.com> <200807042108.25355.jhb@freebsd.org> X-Mailer: Apple Mail (2.926) Cc: Alexey Shuvaev , freebsd-current@freebsd.org, Dmitry Morozovsky Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 15:44:58 -0000 On Jul 4, 2008, at 6:08 PM, John Baldwin wrote: >>> The >>> attachments get bound at runtime. This is actually an important >>> feature. >> >> It's an important feature of KOBJ, yes. The point of compiling >> drivers into the kernel is to get just what you need. Not a >> bunch of bus attachments you don't want. Modules have pretty >> much all bus attachments because they need to work with >> whatever kernel they're loaded in. >> >> So, sio(4) is not following the rules in the strictest sense. >> That's why sio(4) is a bad example, why the problem is not >> adequately acknowledged and people keep running into the same >> old problems of things not working "as expected". > > This is because acpi is a module. One way this could be fixed is to > not put > ISA devices enumerated by ACPI on acpi0, but instead of an ACPI- > aware ISA bus > driver for devices on ISA/LPC that ACPI enumerates. Agreed. For this to work on ia64, we also have to clean up the ISA related code and some drivers. We have to remove the assumption of having (legacy) PC hardware from it. The legacy PC code must be moved under a different option. Think about syscons, PnP, ISA DMA and option ROM. Those options could be put under an option LPC or something. For example: we could have an option LPC that is what option ISA is now, but excludes the isa(4) bus driver. The ISA option would change to mean the isa(4) bus driver only. In a way acpi(4) is that new isa(4) bus driver, but we didn't change option ISA to exclude the current isa bus. In other words, we didn't add support for hints to acpi(4). The amount of work is to eliminate the isa bus. That gives exactly what you suggest, modulo naming. > Also, none of that will > fix any of the actual problems people have (i.e. COM1 being sio1 and > COM2 > being sio0 because the BIOS lists them backwards. This happens to > work in > the non-ACPI case with PNPBIOS due to far grosser hacks that cause > PNPBIOS > devices to not even be used if hints are present.) That's still a different issue and unrelated. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 15:59:47 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 766821065673 for ; Sat, 5 Jul 2008 15:59:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 595E58FC25 for ; Sat, 5 Jul 2008 15:59:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m65Fxk6C017667; Sat, 5 Jul 2008 08:59:46 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m65FxZwC054791; Sat, 5 Jul 2008 08:59:35 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pool-96-232-19-75.nycmny.east.verizon.net [96.232.19.75] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m65FxY13024808; Sat, 5 Jul 2008 08:59:35 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Sat, 05 Jul 2008 11:59:34 -0400 Message-ID: From: gnn@freebsd.org To: Bakul Shah In-Reply-To: <20080704191043.87CFE5B4B@mail.bitblocks.com> References: <20080704191043.87CFE5B4B@mail.bitblocks.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 868068 - 1b4be2eb1021 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 15:59:47 -0000 At Fri, 04 Jul 2008 12:10:43 -0700, Bakul Shah wrote: > > On Fri, 04 Jul 2008 12:58:07 EDT gnn@freebsd.org wrote: > > I have hundreds of these files to run this over, and a full check > > takes about 3 hours, but I usually see some form of corruption within > > the first 20 minutes. > > ... > > 4) Corruption is seen only after a reboot, if the machines continue to > > run corruption is never seen again, until another reboot. > > This sounds like a hardware problem.... May be heat related or due > to a marginal power supply? Try using a beefier supply on one of > the systems or removing something to reduce load. Or increase the > load by making disks do lots of seeking while you are running unzip > and running other things at the same time. To isolate heat related > problems we used to blow cold air (or hot air) on suspected > components and see if the problem goes away or gets worse. These machines are in a brand new data center with more than adequate cooling and have very beefy power. Best, George From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 16:04:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C54BE1065671; Sat, 5 Jul 2008 16:04:59 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.81]) by mx1.freebsd.org (Postfix) with ESMTP id 93CB98FC18; Sat, 5 Jul 2008 16:04:59 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp020-bge351000.mac.com (asmtp020-bge351000 [10.150.69.83]) by smtpoutm.mac.com (Xserve/smtpout018/MantshX 4.0) with ESMTP id m65G4xAl026393; Sat, 5 Jul 2008 09:04:59 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp020.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3J00A33JCAVLA0@asmtp020.mac.com>; Sat, 05 Jul 2008 09:04:59 -0700 (PDT) Message-id: <254B5D19-E08A-43A0-AB76-43299C4AD77C@mac.com> From: Marcel Moolenaar To: Takahashi Yoshihiro In-reply-to: <20080705.212422.226755141.nyan@jp.FreeBSD.org> Date: Sat, 05 Jul 2008 09:04:58 -0700 References: <20080704.063540.1210476607.imp@bsdimp.com> <20080704.221043.226715262.nyan@jp.FreeBSD.org> <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> <20080705.212422.226755141.nyan@jp.FreeBSD.org> X-Mailer: Apple Mail (2.926) Cc: ed@80386.nl, sam@freebsd.org, imp@freebsd.org, freebsd-current@freebsd.org, arch@freebsd.org Subject: Re: MPSAFE TTY schedule [uart vs sio] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 16:04:59 -0000 On Jul 5, 2008, at 5:24 AM, Takahashi Yoshihiro wrote: > In article <29489C48-93A2-41D9-9EF1-5395A673A9B3@mac.com> > Marcel Moolenaar writes: > >>> The uart probably works for some 16550 based devices but does not >>> work >>> for other one like multi-port devices. >> >> The design principle of uart(4) is that it does not know >> about multi-port hardware. It controls a single serial >> port only. For multi-port hardware you must have multiple >> nodes on a bus or use an umbrella driver, such as puc(4), >> quicc(4) or scc(4). Those drivers provide attachments for >> every port. >> >> I suspect that support for multi-port devices is not to >> hard to do on pc98... > > Many serial devices on pc98 use indirect I/O space, so resource > management is quite complex. Therefore, it may need more work you > think. I'm not sure I understand exactly what that means. Can you elaborate? > At the starting point, I have added CBus frontend and fixed console > support for pc98. Great, thanks! Could you commit sys/pc98/include/bus.h and sys/pc98/pc98/busiosubr.c at your earliest convenience. That code has to be in the kernel if I were to work on the uart module. Thanks, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 16:24:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6A86106568A for ; Sat, 5 Jul 2008 16:24:35 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5A4CE8FC12 for ; Sat, 5 Jul 2008 16:24:34 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65GOV5t082834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 5 Jul 2008 18:24:32 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65GOSrK024819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 18:24:28 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65GOSBR042024; Sat, 5 Jul 2008 18:24:28 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65GOR6a042023; Sat, 5 Jul 2008 18:24:27 +0200 (CEST) (envelope-from ticso) Date: Sat, 5 Jul 2008 18:24:27 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705162426.GD41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050957.07900.hselasky@c2i.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.109, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 16:24:35 -0000 On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Luigi Rizzo wrote: > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > There was a discussion back in september about adding > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > > the next few days. > > > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > > > the ones I am talking about don't implement any form of flow control. > > > > I suppose they would otherwise match the previous check. > > > > > > > > luigi > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > the OS only know about bytes. > > > > are firmware, software, data or random noise. > > if you want to know whether the sam7 uploader works, yes it does. > > _______________________________________________ > > 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" > > Yes, but you know that umodem can drop data, if the buffers overflow ? Do you mean the driver can loose data? It would be good if this is avoidable somehow. In fact those beasts have some kind of pseudo flow control in that they don't ack further packets. Basicly this is nothing more than using a pair of bulk pipes for raw data, but under the hood of CDC identification. I personally only use them for uploading firmware to AT91SAM7* controllers, as luigi does, but since Windows and Linux have generic drivers this is quite popular. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 16:54:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5AAE1065681 for ; Sat, 5 Jul 2008 16:54:30 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 87C108FC1C for ; Sat, 5 Jul 2008 16:54:30 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m65GFaan018297; Sat, 5 Jul 2008 09:15:36 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m65GFNFC059458; Sat, 5 Jul 2008 09:15:23 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pool-96-224-5-178.nycmny.east.verizon.net [96.224.5.178]) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m65GFHT7027740; Sat, 5 Jul 2008 09:15:22 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Sat, 05 Jul 2008 12:15:16 -0400 Message-ID: From: gnn@freebsd.org To: John Baldwin In-Reply-To: <200807041521.25711.jhb@freebsd.org> References: <200807041521.25711.jhb@freebsd.org> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 868141 - da1bf8f9d251 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: freebsd-current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 16:54:30 -0000 At Fri, 4 Jul 2008 15:21:25 -0400, John Baldwin wrote: > > If this is one of the ATA controllers where it tries to use 63k > transfers (126 * DEV_BSIZE) instead of 64k, then change it to 32k > (64 * DEV_BSIZE). W/o this fix I see massive data corruption > (couldn't even build a kernel with the fix, had to reinstall the > box) on HT1000 ATA chipsets. Crashdumps also don't seem to work > reliably w/o changing that. > Hmm, I don't see quite that much corruption. Reading over ata-chipset.c I see that there are 4 controllers which may have this issue: Cyrix Marvell National Serverworks This has been happening on AMCC cards and very occasionally Supermicro motherboards. Is there an easy way to determine if either of those are using these chips? Best, George From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 17:01:01 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBD7B1065672; Sat, 5 Jul 2008 17:01:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8628FC0C; Sat, 5 Jul 2008 17:01:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65GOV5t082834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 5 Jul 2008 18:24:32 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65GOSrK024819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 18:24:28 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65GOSBR042024; Sat, 5 Jul 2008 18:24:28 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65GOR6a042023; Sat, 5 Jul 2008 18:24:27 +0200 (CEST) (envelope-from ticso) Date: Sat, 5 Jul 2008 18:24:27 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705162426.GD41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050028.48942.hselasky@c2i.net> <20080704224918.GA2145@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807050957.07900.hselasky@c2i.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.109, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 17:01:01 -0000 On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Luigi Rizzo wrote: > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote: > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote: > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > There was a discussion back in september about adding > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > probe/attach routine, so if there are no objections I plan to > > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in > > > > > > > > the next few days. > > > > > > > > > > What about flow control? Is flow control required for these devices? > > > > > > > > the ones I am talking about don't implement any form of flow control. > > > > I suppose they would otherwise match the previous check. > > > > > > > > luigi > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > the OS only know about bytes. > > > > are firmware, software, data or random noise. > > if you want to know whether the sam7 uploader works, yes it does. > > _______________________________________________ > > 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" > > Yes, but you know that umodem can drop data, if the buffers overflow ? Do you mean the driver can loose data? It would be good if this is avoidable somehow. In fact those beasts have some kind of pseudo flow control in that they don't ack further packets. Basicly this is nothing more than using a pair of bulk pipes for raw data, but under the hood of CDC identification. I personally only use them for uploading firmware to AT91SAM7* controllers, as luigi does, but since Windows and Linux have generic drivers this is quite popular. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 17:18:37 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C71021065672; Sat, 5 Jul 2008 17:18:37 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id AD8EA8FC19; Sat, 5 Jul 2008 17:18:37 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 0379B5B4C; Sat, 5 Jul 2008 10:18:36 -0700 (PDT) To: gnn@freebsd.org In-reply-to: Your message of "Sat, 05 Jul 2008 11:59:34 EDT." Date: Sat, 05 Jul 2008 10:18:36 -0700 From: Bakul Shah Message-Id: <20080705171837.0379B5B4C@mail.bitblocks.com> Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 17:18:37 -0000 On Sat, 05 Jul 2008 11:59:34 EDT gnn@freebsd.org wrote: > At Fri, 04 Jul 2008 12:10:43 -0700, > Bakul Shah wrote: > > > > On Fri, 04 Jul 2008 12:58:07 EDT gnn@freebsd.org wrote: > > > I have hundreds of these files to run this over, and a full check > > > takes about 3 hours, but I usually see some form of corruption within > > > the first 20 minutes. > > > ... > > > 4) Corruption is seen only after a reboot, if the machines continue to > > > run corruption is never seen again, until another reboot. > > > > This sounds like a hardware problem.... May be heat related or due > > to a marginal power supply? Try using a beefier supply on one of > > the systems or removing something to reduce load. Or increase the > > load by making disks do lots of seeking while you are running unzip > > and running other things at the same time. To isolate heat related > > problems we used to blow cold air (or hot air) on suspected > > components and see if the problem goes away or gets worse. > > These machines are in a brand new data center with more than adequate > cooling and have very beefy power. The fact you see corruption during just the first 20 minutes and that you have this problem with a bunch of machines with the same kind of mobo made me think of a h/w problem. A marginal design may work fine within some temperature range but not the one of interest to you (when the scratches on your head get really deep this is something to look into). From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 20:11:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C984B10656A1 for ; Sat, 5 Jul 2008 20:11:40 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id AD9518FC13 for ; Sat, 5 Jul 2008 20:11:40 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 28340 invoked from network); 5 Jul 2008 20:11:39 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Jul 2008 20:11:39 -0000 Message-ID: <486FD2BA.8050505@telenix.org> Date: Sat, 05 Jul 2008 15:59:54 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: kernel modules wont load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 20:11:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can't get my oss sound to load, and the first error I get is this: osscore.ko: depends on kernel - not available That came from both the oss logging file and dmesg. I don't understand what "depends on kernel" means, could I get a hint on that? I think it's the reason that later oss modules don't load correctly. Thanks for any help on this, I'd like to get my sound working again. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhv0rkACgkQz62J6PPcoOl71ACgiGfUYQvVoRh+D2yt7neztzp7 eboAn0kzZiIA1643EXklGO793XZYzvwd =r1ZM -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 20:18:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BB1D1065670 for ; Sat, 5 Jul 2008 20:18:08 +0000 (UTC) (envelope-from guguibin@cn.ibm.com) Received: from e23smtp02.au.ibm.com (E23SMTP02.au.ibm.com [202.81.18.163]) by mx1.freebsd.org (Postfix) with ESMTP id 892498FC14 for ; Sat, 5 Jul 2008 20:18:07 +0000 (UTC) (envelope-from guguibin@cn.ibm.com) Received: from sd0109e.au.ibm.com (d23rh905.au.ibm.com [202.81.18.225]) by e23smtp02.au.ibm.com (8.13.1/8.13.1) with ESMTP id m65K3oD2015770 for ; Sun, 6 Jul 2008 06:03:50 +1000 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by sd0109e.au.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m65K45fI282212 for ; Sun, 6 Jul 2008 06:04:05 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m65K44eg009205 for ; Sun, 6 Jul 2008 06:04:05 +1000 Received: from d23m0014.cn.ibm.com (D23M0014.cn.ibm.com [9.181.41.11]) by d23av04.au.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m65K440m009202 for ; Sun, 6 Jul 2008 06:04:04 +1000 In-Reply-To: <20080705024636.45FDF106571D@hub.freebsd.org> To: freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: Gui Bin Gu Message-ID: Date: Sun, 6 Jul 2008 04:04:50 +0800 X-MIMETrack: Serialize by Router on d23m0014/23/M/IBM(Release 7.0.2FP2HF178 | August 10, 2007) at 06/07/2008 04:04:51, Serialize complete at 06/07/2008 04:04:52, Serialize by Router on d23m0014/23/M/IBM(Release 7.0.2FP2HF178 | August 10, 2007) at 06/07/2008 04:04:52 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: freebsd-current Digest, Vol 249, Issue 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 20:18:10 -0000 From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 20:47:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22AAE106564A; Sat, 5 Jul 2008 20:47:43 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id 008208FC1A; Sat, 5 Jul 2008 20:47:42 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KFEfW-0008Cl-CH; Sat, 05 Jul 2008 20:47:42 +0000 Message-ID: <486FDDED.20403@psg.com> Date: Sun, 06 Jul 2008 05:47:41 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Robert Watson References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <20080705161614.O19209@fledge.watson.org> In-Reply-To: <20080705161614.O19209@fledge.watson.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 20:47:43 -0000 > Sounds pretty much in line with what I was looking for. However, I > think I would like to see it be a bit more complete than sysinstall in > the area of geom partition labeling (concat/strip/raid/encryption), and > perhaps also ZFS support. I realize that adds complexity a fair amount, > but one of the biggest areas of feature lack in sysinstall today is that > you are basically stuck with the original BSD partition structure and > UFS, whereas we expect increasing numbers of users to deploy ZFS. We > don't have boot support currently, but being able to set up /data as a > ZFS file system would be great. Today, people have to do an initial > install on, say, a small boot partition and then relabel/deal with the > rest of the disk, boot a live CD, or worse, discover they have to > repartition, which really fails to expose some of the excellent > ease-of-use, auto-configuration, etc, features that we otherwise have in > this area. i suspect many folk installing zfs want a gmirrored boot partition, as i do. and setting zfs up is trivial next to doing a gmirrored boot on two small partitions on the two drives. but with the varied file system options and strategies we have, ufs, zfs, gmirror, crypted, ... i suspect that trying to get sysinstall to support us all is a path to having sysinstall need a dvd as opposed to a cd-rom. randy From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 20:54:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C6881065677 for ; Sat, 5 Jul 2008 20:54:41 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swipnet.se [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7038FC13 for ; Sat, 5 Jul 2008 20:54:40 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=6I5d2MoRAAAA:8 a=vPI1Uvfh2tOLLZd5LvAA:9 a=3B-JzkFH_HoxxIMzs3gA:7 a=u3MJIqfA3LGkk_pR_JBcSmJQSosA:4 a=lRjT1wxQ3FAA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 256148758; Sat, 05 Jul 2008 22:54:38 +0200 From: Hans Petter Selasky To: ticso@cicely.de Date: Sat, 5 Jul 2008 22:56:14 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> In-Reply-To: <20080705162426.GD41487@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200807052256.15792.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 20:54:41 -0000 On Saturday 05 July 2008, Bernd Walter wrote: > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > On Saturday 05 July 2008, Luigi Rizzo wrote: > > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wro= te: > > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrot= e: > > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > > There was a discussion back in september about adding > > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > > probe/attach routine, so if there are no objections I plan > > > > > > > > > to add this to the system (CURRENT then RELENG_7 and > > > > > > > > > RELENG_6) in the next few days. > > > > > > > > > > > > What about flow control? Is flow control required for these > > > > > > devices? > > > > > > > > > > the ones I am talking about don't implement any form of flow > > > > > control. I suppose they would otherwise match the previous check. > > > > > > > > > > luigi > > > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > > > the OS only know about bytes. > > > > > > are firmware, software, data or random noise. > > > if you want to know whether the sam7 uploader works, yes it does. > > > _______________________________________________ > > > 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" > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > Do you mean the driver can loose data? > It would be good if this is avoidable somehow. > In fact those beasts have some kind of pseudo flow control in that they > don't ack further packets. > Basicly this is nothing more than using a pair of bulk pipes for raw > data, but under the hood of CDC identification. > I personally only use them for uploading firmware to AT91SAM7* > controllers, as luigi does, but since Windows and Linux have generic > drivers this is quite popular. =46rom what I know the TTY layer which umodem uses will dump data when the= =20 buffers are full. But it there is some kind of framing in the protocol used= ,=20 then this is no problem. =2D-HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:04:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58F7A1065679 for ; Sat, 5 Jul 2008 21:04:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 310AE8FC0C for ; Sat, 5 Jul 2008 21:04:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A61B346C48; Sat, 5 Jul 2008 17:04:47 -0400 (EDT) Date: Sat, 5 Jul 2008 22:04:47 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chuck Robey In-Reply-To: <486FD2BA.8050505@telenix.org> Message-ID: <20080705220254.I51796@fledge.watson.org> References: <486FD2BA.8050505@telenix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: kernel modules wont load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 21:04:48 -0000 On Sat, 5 Jul 2008, Chuck Robey wrote: > I can't get my oss sound to load, and the first error I get is this: > > osscore.ko: depends on kernel - not available > > That came from both the oss logging file and dmesg. I don't understand what > "depends on kernel" means, could I get a hint on that? I think it's the > reason that later oss modules don't load correctly. > > Thanks for any help on this, I'd like to get my sound working again. In HEAD, we're currently building all modules with an automatic version dependency on the version of the kernel they are intended to run in. The error message should be telling you need version X but it found version Y, but doesn't, unfortunately. Rebuilding the module should get it working. I seem to recall printing the error better is awkward because the dependency failure is generated somewhere deep in the linker, and the error is printed on the surface, but should be fixable. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:35:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 612531065672 for ; Sat, 5 Jul 2008 21:35:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by mx1.freebsd.org (Postfix) with ESMTP id E29808FC1B for ; Sat, 5 Jul 2008 21:35:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m65LZ1Dl015832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jul 2008 07:35:02 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m65LZ1tt064421; Sun, 6 Jul 2008 07:35:01 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m65LZ1Sb064420; Sun, 6 Jul 2008 07:35:01 +1000 (EST) (envelope-from peter) Date: Sun, 6 Jul 2008 07:35:01 +1000 From: Peter Jeremy To: Sverre Svenningsen Message-ID: <20080705213500.GC29380@server.vk2pj.dyndns.org> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <20080703170700.3b91b8c6@peedub.jennejohn.org> <20080703152551.GA73103@onelab2.iet.unipi.it> <200807042333.17859.hselasky@c2i.net> <20080704213959.GA1706@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rQ7Ovc9/RBrrr0/1" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 21:35:04 -0000 --rQ7Ovc9/RBrrr0/1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jul-05 09:24:15 +0200, Sverre Svenningsen wrot= e: >Is current@freebsd.org just an alias to freebsd-current@freebsd.org ? Yes. There are some MUAs that have broken list-handling functionality and cannot be configured to recognize list aliases. Unless the sender manually strips out the redundant address, it will wind up duplicated. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --rQ7Ovc9/RBrrr0/1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhv6QQACgkQ/opHv/APuIe32QCfafPlba5fkYbrci+tIAAiMld/ NGAAn1SmUkwKsOe9LfLrmXp+i59SrY6Q =KTMH -----END PGP SIGNATURE----- --rQ7Ovc9/RBrrr0/1-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:50:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B72A01065672; Sat, 5 Jul 2008 21:50:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA688FC12; Sat, 5 Jul 2008 21:50:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65LosZR096345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 5 Jul 2008 23:50:54 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65LoXNJ032132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 23:50:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65LoXGK042724; Sat, 5 Jul 2008 23:50:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65LoWHC042723; Sat, 5 Jul 2008 23:50:32 +0200 (CEST) (envelope-from ticso) Date: Sat, 5 Jul 2008 23:50:32 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705215032.GG41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> <200807052256.15792.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807052256.15792.hselasky@c2i.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.104, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, ticso@cicely.de, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 21:50:57 -0000 On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Bernd Walter wrote: > > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > > > Do you mean the driver can loose data? > > It would be good if this is avoidable somehow. > > In fact those beasts have some kind of pseudo flow control in that they > > don't ack further packets. > > Basicly this is nothing more than using a pair of bulk pipes for raw > > data, but under the hood of CDC identification. > > I personally only use them for uploading firmware to AT91SAM7* > > controllers, as luigi does, but since Windows and Linux have generic > > drivers this is quite popular. > > From what I know the TTY layer which umodem uses will dump data when the > buffers are full. But it there is some kind of framing in the protocol used, > then this is no problem. Well - the problem is that there is not special protocol. This technology is used as a general purpose interface for almost every kind of application that. Most protocols are using smal transactions, but this is general purpos after all. This is quite similar as devices using embedded uart or something like the FT245 pseudo uart chips from FTDI. I asume even most modern cell phones don't use real uarts. I wonder what happens with real USB RS232 with activated RTS/CTS. The handshake is handled in the USB device and not under FreeBSD, because the USB devices have too large buffers for the OS to react fast enough. Can we loose data as well? If yes we have a problem there as well. If not, then there must be some kind of mechanism to sync TTY layer with the USB transport speed and we can use the same for pseudo uart. I don't think we should drop data ourself, since we have USB handshake for speed syncronisation. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:50:57 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B72A01065672; Sat, 5 Jul 2008 21:50:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA688FC12; Sat, 5 Jul 2008 21:50:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65LosZR096345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 5 Jul 2008 23:50:54 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65LoXNJ032132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 23:50:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65LoXGK042724; Sat, 5 Jul 2008 23:50:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65LoWHC042723; Sat, 5 Jul 2008 23:50:32 +0200 (CEST) (envelope-from ticso) Date: Sat, 5 Jul 2008 23:50:32 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705215032.GG41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> <200807052256.15792.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807052256.15792.hselasky@c2i.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.104, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, ticso@cicely.de, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 21:50:57 -0000 On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote: > On Saturday 05 July 2008, Bernd Walter wrote: > > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > > > Do you mean the driver can loose data? > > It would be good if this is avoidable somehow. > > In fact those beasts have some kind of pseudo flow control in that they > > don't ack further packets. > > Basicly this is nothing more than using a pair of bulk pipes for raw > > data, but under the hood of CDC identification. > > I personally only use them for uploading firmware to AT91SAM7* > > controllers, as luigi does, but since Windows and Linux have generic > > drivers this is quite popular. > > From what I know the TTY layer which umodem uses will dump data when the > buffers are full. But it there is some kind of framing in the protocol used, > then this is no problem. Well - the problem is that there is not special protocol. This technology is used as a general purpose interface for almost every kind of application that. Most protocols are using smal transactions, but this is general purpos after all. This is quite similar as devices using embedded uart or something like the FT245 pseudo uart chips from FTDI. I asume even most modern cell phones don't use real uarts. I wonder what happens with real USB RS232 with activated RTS/CTS. The handshake is handled in the USB device and not under FreeBSD, because the USB devices have too large buffers for the OS to react fast enough. Can we loose data as well? If yes we have a problem there as well. If not, then there must be some kind of mechanism to sync TTY layer with the USB transport speed and we can use the same for pseudo uart. I don't think we should drop data ourself, since we have USB handshake for speed syncronisation. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:54:46 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83B761065676; Sat, 5 Jul 2008 21:54:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swipnet.se [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id B0ED08FC0A; Sat, 5 Jul 2008 21:54:45 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pW5Z-H8n_VoA:10 a=_6_vb1nlnQcA:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=6I5d2MoRAAAA:8 a=vPI1Uvfh2tOLLZd5LvAA:9 a=3B-JzkFH_HoxxIMzs3gA:7 a=u3MJIqfA3LGkk_pR_JBcSmJQSosA:4 a=lRjT1wxQ3FAA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 256148758; Sat, 05 Jul 2008 22:54:38 +0200 From: Hans Petter Selasky To: ticso@cicely.de Date: Sat, 5 Jul 2008 22:56:14 +0200 User-Agent: KMail/1.9.7 References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> In-Reply-To: <20080705162426.GD41487@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200807052256.15792.hselasky@c2i.net> Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 21:54:46 -0000 On Saturday 05 July 2008, Bernd Walter wrote: > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > On Saturday 05 July 2008, Luigi Rizzo wrote: > > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote: > > > > On Friday 04 July 2008, Luigi Rizzo wrote: > > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wro= te: > > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote: > > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrot= e: > > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200 > > > > > > > > > > > > > > > > Luigi Rizzo wrote: > > > > > > > > > There was a discussion back in september about adding > > > > > > > > > support for basic CDC tty devices in umodem.c. > > > > > > > > > This lets you talk to a number of usb devices built around > > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with > > > > > > > > > Linux and Windows in terms of supporting these devices. > > > > > > > > > > > > > > > > > > Because this simply requires the small patch below to the > > > > > > > > > probe/attach routine, so if there are no objections I plan > > > > > > > > > to add this to the system (CURRENT then RELENG_7 and > > > > > > > > > RELENG_6) in the next few days. > > > > > > > > > > > > What about flow control? Is flow control required for these > > > > > > devices? > > > > > > > > > > the ones I am talking about don't implement any form of flow > > > > > control. I suppose they would otherwise match the previous check. > > > > > > > > > > luigi > > > > > > > > I mean, are you going to upload firmware through these interfaces? > > > > > > the OS only know about bytes. > > > > > > are firmware, software, data or random noise. > > > if you want to know whether the sam7 uploader works, yes it does. > > > _______________________________________________ > > > 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" > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > Do you mean the driver can loose data? > It would be good if this is avoidable somehow. > In fact those beasts have some kind of pseudo flow control in that they > don't ack further packets. > Basicly this is nothing more than using a pair of bulk pipes for raw > data, but under the hood of CDC identification. > I personally only use them for uploading firmware to AT91SAM7* > controllers, as luigi does, but since Windows and Linux have generic > drivers this is quite popular. =46rom what I know the TTY layer which umodem uses will dump data when the= =20 buffers are full. But it there is some kind of framing in the protocol used= ,=20 then this is no problem. =2D-HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 22:13:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A43821065676; Sat, 5 Jul 2008 22:13:20 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 27CD38FC12; Sat, 5 Jul 2008 22:13:19 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65MDHNX096881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 6 Jul 2008 00:13:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65MCmXP032732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jul 2008 00:12:48 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65MCljC042790; Sun, 6 Jul 2008 00:12:47 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65MClfW042789; Sun, 6 Jul 2008 00:12:47 +0200 (CEST) (envelope-from ticso) Date: Sun, 6 Jul 2008 00:12:47 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705221247.GH41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> <200807052256.15792.hselasky@c2i.net> <20080705215032.GG41487@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080705215032.GG41487@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.103, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, ticso@cicely.de, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 22:13:20 -0000 On Sat, Jul 05, 2008 at 11:50:32PM +0200, Bernd Walter wrote: > On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote: > > On Saturday 05 July 2008, Bernd Walter wrote: > > > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > > > > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > > > > > Do you mean the driver can loose data? > > > It would be good if this is avoidable somehow. > > > In fact those beasts have some kind of pseudo flow control in that they > > > don't ack further packets. > > > Basicly this is nothing more than using a pair of bulk pipes for raw > > > data, but under the hood of CDC identification. > > > I personally only use them for uploading firmware to AT91SAM7* > > > controllers, as luigi does, but since Windows and Linux have generic > > > drivers this is quite popular. > > > > From what I know the TTY layer which umodem uses will dump data when the > > buffers are full. But it there is some kind of framing in the protocol used, > > then this is no problem. > > Well - the problem is that there is not special protocol. > This technology is used as a general purpose interface for almost every > kind of application that. > Most protocols are using smal transactions, but this is general purpos > after all. > This is quite similar as devices using embedded uart or something like > the FT245 pseudo uart chips from FTDI. > I asume even most modern cell phones don't use real uarts. > > I wonder what happens with real USB RS232 with activated RTS/CTS. > The handshake is handled in the USB device and not under FreeBSD, > because the USB devices have too large buffers for the OS to react fast > enough. > Can we loose data as well? > If yes we have a problem there as well. > If not, then there must be some kind of mechanism to sync TTY layer > with the USB transport speed and we can use the same for pseudo uart. > > I don't think we should drop data ourself, since we have USB handshake > for speed syncronisation. After rethinking: I only remember having seen TTY layer dropped data in the receive path and I can't think that it was every reasonable to do for sending, since the local application can be throttled. However - we should not receive from USB if our tty buffer can't hold further data. It is up to the USB device to drop data if unavoidable, since only the device itsel can judge. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 22:13:20 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A43821065676; Sat, 5 Jul 2008 22:13:20 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 27CD38FC12; Sat, 5 Jul 2008 22:13:19 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m65MDHNX096881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 6 Jul 2008 00:13:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m65MCmXP032732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jul 2008 00:12:48 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m65MCljC042790; Sun, 6 Jul 2008 00:12:47 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m65MClfW042789; Sun, 6 Jul 2008 00:12:47 +0200 (CEST) (envelope-from ticso) Date: Sun, 6 Jul 2008 00:12:47 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20080705221247.GH41487@cicely7.cicely.de> References: <20080703140719.GA72315@onelab2.iet.unipi.it> <200807050957.07900.hselasky@c2i.net> <20080705162426.GD41487@cicely7.cicely.de> <200807052256.15792.hselasky@c2i.net> <20080705215032.GG41487@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080705215032.GG41487@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.103, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: usb@freebsd.org, Luigi Rizzo , freebsd-current@freebsd.org, ticso@cicely.de, current@freebsd.org Subject: Re: may I commit this small umodem patch ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 22:13:20 -0000 On Sat, Jul 05, 2008 at 11:50:32PM +0200, Bernd Walter wrote: > On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote: > > On Saturday 05 July 2008, Bernd Walter wrote: > > > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote: > > > > > > > > Yes, but you know that umodem can drop data, if the buffers overflow ? > > > > > > Do you mean the driver can loose data? > > > It would be good if this is avoidable somehow. > > > In fact those beasts have some kind of pseudo flow control in that they > > > don't ack further packets. > > > Basicly this is nothing more than using a pair of bulk pipes for raw > > > data, but under the hood of CDC identification. > > > I personally only use them for uploading firmware to AT91SAM7* > > > controllers, as luigi does, but since Windows and Linux have generic > > > drivers this is quite popular. > > > > From what I know the TTY layer which umodem uses will dump data when the > > buffers are full. But it there is some kind of framing in the protocol used, > > then this is no problem. > > Well - the problem is that there is not special protocol. > This technology is used as a general purpose interface for almost every > kind of application that. > Most protocols are using smal transactions, but this is general purpos > after all. > This is quite similar as devices using embedded uart or something like > the FT245 pseudo uart chips from FTDI. > I asume even most modern cell phones don't use real uarts. > > I wonder what happens with real USB RS232 with activated RTS/CTS. > The handshake is handled in the USB device and not under FreeBSD, > because the USB devices have too large buffers for the OS to react fast > enough. > Can we loose data as well? > If yes we have a problem there as well. > If not, then there must be some kind of mechanism to sync TTY layer > with the USB transport speed and we can use the same for pseudo uart. > > I don't think we should drop data ourself, since we have USB handshake > for speed syncronisation. After rethinking: I only remember having seen TTY layer dropped data in the receive path and I can't think that it was every reasonable to do for sending, since the local application can be throttled. However - we should not receive from USB if our tty buffer can't hold further data. It is up to the USB device to drop data if unavoidable, since only the device itsel can judge. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.