[head tinderbox] failure on i386/i386

TB --- 2010-08-26 08:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-08-26 08:30:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-08-26 08:30:00 - cleaning the object tree TB --- 2010-08-26 08:30:56 - cvsupping the source tree TB --- 2010-08-26 08:30:56 -

[head tinderbox] failure on mips/mips

TB --- 2010-08-26 10:40:55 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-08-26 10:40:55 - starting HEAD tinderbox run for mips/mips TB --- 2010-08-26 10:40:55 - cleaning the object tree TB --- 2010-08-26 10:41:16 - cvsupping the source tree TB --- 2010-08-26 10:41:16 -

[head tinderbox] failure on powerpc64/powerpc

TB --- 2010-08-26 11:11:39 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-08-26 11:11:39 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2010-08-26 11:11:39 - cleaning the object tree TB --- 2010-08-26 11:11:51 - cvsupping the source tree TB --- 2010-08-26 11:11:51 -

concerning GCC GPLv2 vs. GPLv3

hi there, the FreeBSD base GCC version is dated 20070719 which is the release date of GCC 4.2.1. after this release the 4.2 branch got GPLv3'ed which is the reason anything after 20070719 in the 4.2 branch cannot be imported into the FreeBSD. Also all the other branches 4.2 are GPLv3'ed too.

[RFC] ifconfig description support in rc.d

[cc'ing current@ as rc@ looks too quite] Hi. Since ifconfig has grown to label interfaces with ifconfig $ifname description foobar, what about to give it more life and store i/face descriptions semi-permanently, so they will survive between reboots? This patch adds a functionality to rc.d to

sched_pin() bug in SCHED_ULE

Back at the beginning of August I posted about issues with sched_pin() and witness_warn(): http://lists.freebsd.org/pipermail/freebsd-hackers/2010-August/032553.html After a lot of debugging I think I've basically found the issue. I found this bug on stable/7, but looking at the commit log for

Re: [RFC] ifconfig description support in rc.d

On 08/26/2010 12:53 PM, pluknet wrote: [cc'ing current@ as rc@ looks too quite] Hi. Since ifconfig has grown to label interfaces with ifconfig $ifname description foobar, what about to give it more life and store i/face descriptions semi-permanently, so they will survive between reboots? This

Re: sched_pin() bug in SCHED_ULE

On Thursday, August 26, 2010 4:03:38 pm m...@freebsd.org wrote: Back at the beginning of August I posted about issues with sched_pin() and witness_warn(): http://lists.freebsd.org/pipermail/freebsd-hackers/2010-August/032553.html After a lot of debugging I think I've basically found the

Re: [RFC] ifconfig description support in rc.d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010/08/26 13:09, Doug Barton wrote: On 08/26/2010 12:53 PM, pluknet wrote: [cc'ing current@ as rc@ looks too quite] Hi. Since ifconfig has grown to label interfaces with ifconfig $ifname description foobar, what about to give it more

Re: sched_pin() bug in SCHED_ULE

On Thu, Aug 26, 2010 at 1:49 PM, John Baldwin j...@freebsd.org wrote: On Thursday, August 26, 2010 4:03:38 pm m...@freebsd.org wrote: Back at the beginning of August I posted about issues with sched_pin() and witness_warn():

Re: sched_pin() bug in SCHED_ULE

on 27/08/2010 00:20 m...@freebsd.org said the following: I tried making sched_pin() a real function which used intr_disable/intr_restore around saving off td-td_oncpu, td-td_lastcpu and ts-ts_cpu, and the stack at the time of call. In sched_switch when I saw an unexpected migration I

Re: sched_pin() bug in SCHED_ULE

On Thu, Aug 26, 2010 at 3:10 PM, Andriy Gapon a...@icyb.net.ua wrote: on 27/08/2010 00:20 m...@freebsd.org said the following: I tried making sched_pin() a real function which used intr_disable/intr_restore around saving off td-td_oncpu, td-td_lastcpu and ts-ts_cpu, and the stack at the time

Apparent regression in extended/logical partition handling

Howdy, Summary: FreeBSD 9-current can't see logical drives inside an extended partition unless all space is assigned to a logical volume, and all logical volumes are formatted with a file system. 7.3-RELEASE does not have this problem. Background: So I got a new HD, and wanted to put

[PATCH] Use MACHINE_ARCH for boot loader

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The attached patch changes FreeBSD/x86 back to FreeBSD/i386 on i386 and FreeBSD/amd64 on amd64. Comments welcome! I'll commit it in by the weekend if there is no objection on this. Cheers, - -- Xin LI delp...@delphij.net

Re: Apparent regression in extended/logical partition handling

On Fri, Aug 27, 2010 at 5:35 AM, Doug Barton do...@freebsd.org wrote: Specifically what I did was to boot Windows XP, delete all the partitions other than the XP partition (first primary dos-style partition) and then create a dos-style extended partition, and a logical drive inside of it,

[head tinderbox] failure on powerpc64/powerpc

TB --- 2010-08-27 03:49:08 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-08-27 03:49:08 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2010-08-27 03:49:08 - cleaning the object tree TB --- 2010-08-27 03:49:22 - cvsupping the source tree TB --- 2010-08-27 03:49:22 -

a question about FreeBSD

Dear all: A quick question about the FreeBSD. In my lab, there is a multicore machine and i install a FreeBSD system on it. I wonder to know how to see the utilization for each core? are there such tools? Thanks! -- Think big; Dream impossible; Make it happen.

Re: a question about FreeBSD

On Fri, Aug 27, 2010 at 12:07:11PM +0800, ccuiy...@gmail.com wrote: Dear all: A quick question about the FreeBSD. In my lab, there is a multicore machine and i install a FreeBSD system on it. I wonder to know how to see the utilization for each core? are there such tools?