Re: Heads Up: default NFS server changing to the new one

> > Actually, I think we should switch GENERIC in HEAD to the new client > and > kernel very soon. The goal is to get current users testing the new > client and > server so they can uncover any bugs. If problems crop up during the > testing > that can't be resolved, we can always revert to the old

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

Hi, On Tue, Apr 26, 2011 at 5:19 PM, Matthias Apitz wrote: > El día Tuesday, April 26, 2011 a las 01:51:55PM -0400, Arnaud Lacombe > escribió: > >> >> Then you can go to gcc.gnu.org/bugzilla and file a PR. >> > >> > Thanks for your hints concerning the GCC problem; I will collect the >> > data a

[head tinderbox] failure on ia64/ia64

TB --- 2011-04-26 21:00:12 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 21:00:12 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-04-26 21:00:12 - cleaning the object tree TB --- 2011-04-26 21:00:17 - cvsupping the source tree TB --- 2011-04-26 21:00:17 - /usr/bin/c

Re: Old ATA disk names emulation [Was: Switch from legacy ata(4) to CAM-based ATA]

Arnaud Lacombe wrote: > Hi, > > 2011/4/25 Alexander Motin : >> Kostik Belousov wrote: >>> On Mon, Apr 25, 2011 at 03:26:02PM +0300, Alexander Motin wrote: Andrey V. Elsukov wrote: > On 25.04.2011 14:23, Alexander Motin wrote: >> What will not work: >> - old device names won't be

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

El día Tuesday, April 26, 2011 a las 01:51:55PM -0400, Arnaud Lacombe escribió: > >> Then you can go to gcc.gnu.org/bugzilla and file a PR. > > > > Thanks for your hints concerning the GCC problem; I will collect the > > data and file a bug report; > > > If it is the gcc in the FreeBSD tree, pleas

[head tinderbox] failure on arm/arm

TB --- 2011-04-26 20:10:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 20:10:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-04-26 20:10:00 - cleaning the object tree TB --- 2011-04-26 20:10:08 - cvsupping the source tree TB --- 2011-04-26 20:10:08 - /usr/bin/csu

Re: sched_4bsd startup crash trying to run a bound thread on an AP that hasn't started

On Tuesday, April 26, 2011 3:46:06 pm Ryan Stone wrote: > On Mon, Apr 25, 2011 at 2:58 PM, John Baldwin wrote: > > > > Yes, I would perhaps tweak the comment to reflect the full if statement > > though. Maybe something like: > > > > /* > > * If SMP is started and the thread is pinned or otherwis

Re: sched_4bsd startup crash trying to run a bound thread on an AP that hasn't started

On Mon, Apr 25, 2011 at 2:58 PM, John Baldwin wrote: > > Yes, I would perhaps tweak the comment to reflect the full if statement > though.  Maybe something like: > > /* >  * If SMP is started and the thread is pinned or otherwise limited to >  * a specific set of CPUs, queue the thread to a per-CP

Re: Old ATA disk names emulation [Was: Switch from legacy ata(4) to CAM-based ATA]

Hi, 2011/4/25 Alexander Motin : > Kostik Belousov wrote: >> On Mon, Apr 25, 2011 at 03:26:02PM +0300, Alexander Motin wrote: >>> Andrey V. Elsukov wrote: On 25.04.2011 14:23, Alexander Motin wrote: > What will not work: >  - old device names won't be seen inside GEOM, so users who har

Re: nspluginwrapper (was: Re: Wow... (<-- blown away at performance))

On Saturday 23 April 2011 04:11 pm, Benjamin Kaduk wrote: > On Thu, 31 Mar 2011, Benjamin Kaduk wrote: > > On Thu, 31 Mar 2011, Jung-uk Kim wrote: > >> On Thursday 31 March 2011 02:27 pm, Alexander Best wrote: > >>> i just noticed the WWW links in pkg-descr of boths > >>> nspluginwrapper and nsplug

[head tinderbox] failure on sparc64/sun4v

TB --- 2011-04-26 18:07:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 18:07:25 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2011-04-26 18:07:25 - cleaning the object tree TB --- 2011-04-26 18:07:38 - cvsupping the source tree TB --- 2011-04-26 18:07:38 - /usr/b

[head tinderbox] failure on sparc64/sparc64

TB --- 2011-04-26 18:07:22 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 18:07:22 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-04-26 18:07:22 - cleaning the object tree TB --- 2011-04-26 18:07:35 - cvsupping the source tree TB --- 2011-04-26 18:07:35 - /usr

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

Hi, On Tue, Apr 26, 2011 at 5:51 AM, Matthias Apitz wrote: > El día Tuesday, April 26, 2011 a las 10:22:21AM +0100, David Woodhouse > escribió: > >> >   crash, i.e. it is *not* the typical hardware related crash; >> > - the above mentioned version evolution-exchange-2.32.1_1 is a fake, in >> >  

[head tinderbox] failure on mips/mips

TB --- 2011-04-26 16:56:41 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 16:56:41 - starting HEAD tinderbox run for mips/mips TB --- 2011-04-26 16:56:41 - cleaning the object tree TB --- 2011-04-26 16:56:50 - cvsupping the source tree TB --- 2011-04-26 16:56:50 - /usr/bin/c

Re: prefer tsc timecounter when it's good

On Friday 08 April 2011 01:43 am, Andriy Gapon wrote: > on 07/04/2011 23:00 Jung-uk Kim said the following: > > Although it looks okay, please don't commit it just yet. I am > > working in this area actively. Also, if the Intel's claim is > > true, i.e., TSCs reset to zero when APs start, we cann

[head tinderbox] failure on ia64/ia64

TB --- 2011-04-26 15:39:39 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 15:39:39 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-04-26 15:39:39 - cleaning the object tree TB --- 2011-04-26 15:39:46 - cvsupping the source tree TB --- 2011-04-26 15:39:46 - /usr/bin/c

Re: Removal of ICC (intel compiler) bits from mk

On Wed, Aug 18, 2010, Rui Paulo wrote: > Hi, > I've been chatting with the ICC ex-users and they seem to be ok with the > removal of the ICC bits from share/mk and other places. > The reason is that it doesn't work and no one has volunteered to fix it for > many years. This seems to indicate tha

Re: Heads up: was Re: error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'

On 04/26/11 15:54, Rick Macklem wrote: Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: Revision: 221060) update I get the follwoing error while building the kernel (options NFSD/options NFSCL instead of options NFSSERVER/options NFSCLIENT): cc -c -O2 -frename-registers -pipe -fno-str

[head tinderbox] failure on arm/arm

TB --- 2011-04-26 14:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 14:50:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-04-26 14:50:00 - cleaning the object tree TB --- 2011-04-26 14:50:08 - cvsupping the source tree TB --- 2011-04-26 14:50:08 - /usr/bin/csu

Heads up: was Re: error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'

> > Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: > > Revision: > > 221060) update I get the follwoing error while building the kernel > > (options NFSD/options NFSCL instead of options NFSSERVER/options > > NFSCLIENT): > > > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing >

Re: bsd/linux ioctl.

Quoting Julian Elischer (from Fri, 22 Apr 2011 18:28:06 -0700): [linux ioctl compatibility] So my first question is "is this hack commonly known?" and secondly "should we clean it up and put it in an ioctl(9) man page?" We should probably have such a page. Do we have a driver porter's han

[head tinderbox] failure on sparc64/sun4v

TB --- 2011-04-26 12:43:40 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 12:43:40 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2011-04-26 12:43:40 - cleaning the object tree TB --- 2011-04-26 12:43:47 - cvsupping the source tree TB --- 2011-04-26 12:43:47 - /usr/b

[head tinderbox] failure on sparc64/sparc64

TB --- 2011-04-26 12:43:35 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 12:43:35 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-04-26 12:43:35 - cleaning the object tree TB --- 2011-04-26 12:43:45 - cvsupping the source tree TB --- 2011-04-26 12:43:45 - /usr

Re: Heads Up: default NFS server changing to the new one

On Sunday, April 24, 2011 3:12:13 pm Rick Macklem wrote: > > On 04/24/11 02:00, Rick Macklem wrote: > > > There will soon be a commit to head that will change the > > > default NFS server to the new one that was called the > > > experimental NFS server (but no longer experimental). After > > > this

Re: error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'

> Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: Revision: > 221060) update I get the follwoing error while building the kernel > (options NFSD/options NFSCL instead of options NFSSERVER/options > NFSCLIENT): > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native >

[head tinderbox] failure on mips/mips

TB --- 2011-04-26 11:34:53 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 11:34:53 - starting HEAD tinderbox run for mips/mips TB --- 2011-04-26 11:34:53 - cleaning the object tree TB --- 2011-04-26 11:35:01 - cvsupping the source tree TB --- 2011-04-26 11:35:01 - /usr/bin/c

error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'

Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: Revision: 221060) update I get the follwoing error while building the kernel (options NFSD/options NFSCL instead of options NFSSERVER/options NFSCLIENT): cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99

[head tinderbox] failure on ia64/ia64

TB --- 2011-04-26 10:18:57 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 10:18:57 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-04-26 10:18:57 - cleaning the object tree TB --- 2011-04-26 10:19:08 - cvsupping the source tree TB --- 2011-04-26 10:19:08 - /usr/bin/c

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

On Tue, 2011-04-26 at 11:51 +0200, Matthias Apitz wrote: > I need the evolution-exchange connector; That's for Exchange 2003, right? If you were on a newer version of Exchange perhaps you'd be able to use the new Evolution-EWS connector. > can I live with 2.32.1 while evolution and its dataserve

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

On Tue, 2011-04-26 at 10:04 +0200, Matthias Apitz wrote: > > Hello, > > I'm trying to compile /usr/ports/mail/evolution-exchange/ and the gcc > crashes with: > > [root@vm-9Current /usr/ports/mail/evolution-exchange]# LANG=C make > ===> Building for evolution-exchange-2.32.1_1 > gmake all-recu

Re: responsiveness during IO tasks

On Mon Apr 25 11, Steve Wills wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I've noticed lately that when doing heavy IO, my 9-CURRENT system (Fri > Apr 15 23:33:46 EDT 2011) is quite unresponsive. I have two ZFS mirrors > setup and run KDE4. The system has 12GB of RAM. >

[head tinderbox] failure on arm/arm

TB --- 2011-04-26 09:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 09:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-04-26 09:30:00 - cleaning the object tree TB --- 2011-04-26 09:30:09 - cvsupping the source tree TB --- 2011-04-26 09:30:09 - /usr/bin/csu

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

El día Tuesday, April 26, 2011 a las 10:22:21AM +0100, David Woodhouse escribió: > > crash, i.e. it is *not* the typical hardware related crash; > > - the above mentioned version evolution-exchange-2.32.1_1 is a fake, in > > real it is compiling the original evolution-exchange-2.32.3 sources;

Re: 9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

Hello. Don't know is this related. I've got rather fresh 9.0-CURRENT (checked out few days ago) built with clang. And I use clang as the system compiler, but ruby fails to build with clang. So I've tried gcc. But with gcc I've got this: .. configure:3211: checking whether the C compiler works

[head tinderbox] failure on sparc64/sun4v

TB --- 2011-04-26 07:25:05 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 07:25:05 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2011-04-26 07:25:05 - cleaning the object tree TB --- 2011-04-26 07:25:15 - cvsupping the source tree TB --- 2011-04-26 07:25:15 - /usr/b

[head tinderbox] failure on sparc64/sparc64

TB --- 2011-04-26 07:07:19 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 07:07:19 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-04-26 07:07:19 - cleaning the object tree TB --- 2011-04-26 07:07:36 - cvsupping the source tree TB --- 2011-04-26 07:07:36 - /usr

9.0-CURRENT r220692 && cc1: internal compiler error: Segmentation fault: 11

Hello, I'm trying to compile /usr/ports/mail/evolution-exchange/ and the gcc crashes with: [root@vm-9Current /usr/ports/mail/evolution-exchange]# LANG=C make ===> Building for evolution-exchange-2.32.1_1 gmake all-recursive gmake[1]: Entering directory `/usr/ports/mail/evolution-exchange/wor

[head tinderbox] failure on mips/mips

TB --- 2011-04-26 06:31:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-04-26 06:31:03 - starting HEAD tinderbox run for mips/mips TB --- 2011-04-26 06:31:03 - cleaning the object tree TB --- 2011-04-26 06:31:10 - cvsupping the source tree TB --- 2011-04-26 06:31:10 - /usr/bin/c