request for your comments on release documentation
Hi, I would like your comments on release notes for each release. Although I have been working on editing them for years, the workflow is still not optimal and sometimes delay of the preparation became an obstacle for release process. I would like to improve it, but before that I would like to know what are desired of the contents which people think. Release Notes is just listing the changes between the two releases. It includes user-visible change (bugfix and/or UI change), new functionality, and performance improvement. Minor changes such as one in kernel internal structure are omitted. I always try to keep these series of relnotes items are correct and reasonably comprehensive, but this lengthy list may be boring and technically-correct descriptions can be cryptic for average users. So, my questions are: 1. What do you think about current granularity of the relnotes items? Too detailed, good, or too rough? Currently, judgment of what is included or not is based on user-visible, new functionality, or performance improvement. Applicable changes are included as relnotes items even if the changes are small, 2. Do you want technical details? For example, just "disk access performance was improved by 50%" or "Feature A has been added. This changes the old behavior because ..., and as a result, it improves disk access performance by 50%". 3. Is there missing information which should be in the relnotes? Probably there are some missing items for each release, but this question is one at some abstraction level. Link to commit log and diff, detailed description of major incompatible changes, and so on. Although the other release documentations---Errata, Installation Notes, ReadMe, and Hardware Notes---also need some improvements, please focus on Release Notes only. And you might think quality of English writing are not good, please leave that alone for now. -- Hiroki pgp8TpJHirj07.pgp Description: PGP signature
copyin()/copyout() constraints ?
hi, is it possible to run copyin() or copyout() in one of these cases: 1. while holding a spinlock 2. while holding a regular mutex/lock 3. while holding a read lock (on an RWLOCK or RMLOCK) 4. while holding a write lock (on an RWLOCK or RMLOCK) I suspect #1 is forbidden, but am a bit unclear for the other cases. thanks luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on arm/arm
TB --- 2013-06-12 15:30:19 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 15:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 15:30:19 - starting HEAD tinderbox run for arm/arm TB --- 2013-06-12 15:30:19 - cleaning the object tree TB --- 2013-06-12 15:30:19 - /usr/local/bin/svn stat /src TB --- 2013-06-12 15:30:24 - At svn revision 251658 TB --- 2013-06-12 15:30:25 - building world TB --- 2013-06-12 15:30:25 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 15:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 15:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 15:30:25 - SRCCONF=/dev/null TB --- 2013-06-12 15:30:25 - TARGET=arm TB --- 2013-06-12 15:30:25 - TARGET_ARCH=arm TB --- 2013-06-12 15:30:25 - TZ=UTC TB --- 2013-06-12 15:30:25 - __MAKE_CONF=/dev/null TB --- 2013-06-12 15:30:25 - cd /src TB --- 2013-06-12 15:30:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 15:30:32 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 18:10:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 18:10:31 - ERROR: failed to build world TB --- 2013-06-12 18:10:31 - 7894.74 user 1260.23 system 9611.82 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-arm-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on armv6/arm
TB --- 2013-06-12 15:30:19 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 15:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 15:30:19 - starting HEAD tinderbox run for armv6/arm TB --- 2013-06-12 15:30:19 - cleaning the object tree TB --- 2013-06-12 15:30:19 - /usr/local/bin/svn stat /src TB --- 2013-06-12 15:30:24 - At svn revision 251658 TB --- 2013-06-12 15:30:25 - building world TB --- 2013-06-12 15:30:25 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 15:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 15:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 15:30:25 - SRCCONF=/dev/null TB --- 2013-06-12 15:30:25 - TARGET=arm TB --- 2013-06-12 15:30:25 - TARGET_ARCH=armv6 TB --- 2013-06-12 15:30:25 - TZ=UTC TB --- 2013-06-12 15:30:25 - __MAKE_CONF=/dev/null TB --- 2013-06-12 15:30:25 - cd /src TB --- 2013-06-12 15:30:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 15:30:32 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 18:10:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 18:10:39 - ERROR: failed to build world TB --- 2013-06-12 18:10:39 - 7901.94 user 1259.37 system 9620.22 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-armv6-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on i386/i386
TB --- 2013-06-12 15:30:19 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 15:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 15:30:19 - starting HEAD tinderbox run for i386/i386 TB --- 2013-06-12 15:30:19 - cleaning the object tree TB --- 2013-06-12 15:30:19 - /usr/local/bin/svn stat /src TB --- 2013-06-12 15:30:24 - At svn revision 251658 TB --- 2013-06-12 15:30:25 - building world TB --- 2013-06-12 15:30:25 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 15:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 15:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 15:30:25 - SRCCONF=/dev/null TB --- 2013-06-12 15:30:25 - TARGET=i386 TB --- 2013-06-12 15:30:25 - TARGET_ARCH=i386 TB --- 2013-06-12 15:30:25 - TZ=UTC TB --- 2013-06-12 15:30:25 - __MAKE_CONF=/dev/null TB --- 2013-06-12 15:30:25 - cd /src TB --- 2013-06-12 15:30:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 15:30:32 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 18:20:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 18:20:01 - ERROR: failed to build world TB --- 2013-06-12 18:20:01 - 8521.66 user 1266.73 system 10182.12 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-i386.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on amd64/amd64
TB --- 2013-06-12 15:30:19 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 15:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 15:30:19 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-06-12 15:30:19 - cleaning the object tree TB --- 2013-06-12 15:30:19 - /usr/local/bin/svn stat /src TB --- 2013-06-12 15:30:24 - At svn revision 251658 TB --- 2013-06-12 15:30:25 - building world TB --- 2013-06-12 15:30:25 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 15:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 15:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 15:30:25 - SRCCONF=/dev/null TB --- 2013-06-12 15:30:25 - TARGET=amd64 TB --- 2013-06-12 15:30:25 - TARGET_ARCH=amd64 TB --- 2013-06-12 15:30:25 - TZ=UTC TB --- 2013-06-12 15:30:25 - __MAKE_CONF=/dev/null TB --- 2013-06-12 15:30:25 - cd /src TB --- 2013-06-12 15:30:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 15:30:32 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 18:20:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 18:20:01 - ERROR: failed to build world TB --- 2013-06-12 18:20:01 - 8510.71 user 1257.52 system 10181.88 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: request for your comments on release documentation
On Wed, 12 Jun 2013 12:49:21 -0500, Hiroki Sato wrote: So, my questions are: 1. What do you think about current granularity of the relnotes items? Too detailed, good, or too rough? Currently, judgment of what is included or not is based on user-visible, new functionality, or performance improvement. Applicable changes are included as relnotes items even if the changes are small, As a sysadmin I live and die by the granularity of release notes. If they weren't granular I'd end up having to read the commit logs and try to parse out changes myself. Sometimes changes aren't going to be obvious if you weren't aware of discussions on the -hackers, -current, or -stable lists. 2. Do you want technical details? For example, just "disk access performance was improved by 50%" or "Feature A has been added. This changes the old behavior because ..., and as a result, it improves disk access performance by 50%". I'm sure if you're too terse like in your first example people will jump to conclusions and be angry when disk performance isn't improved 50% in every possible situation, as well as the project receiving bad press for being too deceiving. If you want to be terse perhaps "Disk access improvements" is sufficient, and use the second example if you want to be more explicit. 3. Is there missing information which should be in the relnotes? Probably there are some missing items for each release, but this question is one at some abstraction level. Link to commit log and diff, detailed description of major incompatible changes, and so on. I try to keep up with the development and changes in releases as best I can and I haven't noticed any glaring omissions over the last several releases. I think you're doing a fine job. Also, is there a reason this isn't a "living" document that can be updated as things get MFC'd to STABLE? It would help take load off your end and maybe speed up release once the freeze has happened and we begin the final grind through release candidates. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: copyin()/copyout() constraints ?
On 6/12/13 11:01 AM, Luigi Rizzo wrote: hi, is it possible to run copyin() or copyout() in one of these cases: 1. while holding a spinlock 2. while holding a regular mutex/lock 3. while holding a read lock (on an RWLOCK or RMLOCK) 4. while holding a write lock (on an RWLOCK or RMLOCK) I suspect #1 is forbidden, but am a bit unclear for the other cases. No on all of the above unless the memory is wired. You need a sx or semaphore. -Alfred thanks luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Alfred Perlstein VP Software Engineering, iXsystems ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: copyin()/copyout() constraints ?
On Wed, Jun 12, 2013 at 08:01:15PM +0200, Luigi Rizzo wrote: > hi, > is it possible to run copyin() or copyout() in one of these cases: > 1. while holding a spinlock > 2. while holding a regular mutex/lock > 3. while holding a read lock (on an RWLOCK or RMLOCK) > 4. while holding a write lock (on an RWLOCK or RMLOCK) > > I suspect #1 is forbidden, but am a bit unclear for the > other cases. The rules for copyin/copyout/uiomove come from the fact that usermode access might require VM handling the page fault, which might further require VM access to the VFS/filesystem and device. If the filesystem is NFS, then there is a network access down the stack. As result, you cannot hold any lock which may be recursed, or any non-sleepable lock. In other word, answer to all your four questions is no, since kernel cannot sleep while owning spinlock, mutex, rmlock or rwlock. In practical terms, you could only own some private sleepable lock which is before any other kernel lock. pgpVanTBDjg_o.pgp Description: PGP signature
[head tinderbox] failure on mips/mips
TB --- 2013-06-12 18:20:01 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 18:20:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 18:20:01 - starting HEAD tinderbox run for mips/mips TB --- 2013-06-12 18:20:01 - cleaning the object tree TB --- 2013-06-12 18:20:01 - /usr/local/bin/svn stat /src TB --- 2013-06-12 18:20:14 - At svn revision 251658 TB --- 2013-06-12 18:20:15 - building world TB --- 2013-06-12 18:20:15 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 18:20:15 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 18:20:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 18:20:15 - SRCCONF=/dev/null TB --- 2013-06-12 18:20:15 - TARGET=mips TB --- 2013-06-12 18:20:15 - TARGET_ARCH=mips TB --- 2013-06-12 18:20:15 - TZ=UTC TB --- 2013-06-12 18:20:15 - __MAKE_CONF=/dev/null TB --- 2013-06-12 18:20:15 - cd /src TB --- 2013-06-12 18:20:15 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 18:20:22 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 19:08:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 19:08:31 - ERROR: failed to build world TB --- 2013-06-12 19:08:31 - 2096.70 user 473.88 system 2909.31 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on mips64/mips
TB --- 2013-06-12 18:20:02 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 18:20:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 18:20:02 - starting HEAD tinderbox run for mips64/mips TB --- 2013-06-12 18:20:02 - cleaning the object tree TB --- 2013-06-12 18:20:02 - /usr/local/bin/svn stat /src TB --- 2013-06-12 18:20:14 - At svn revision 251658 TB --- 2013-06-12 18:20:15 - building world TB --- 2013-06-12 18:20:15 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 18:20:15 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 18:20:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 18:20:15 - SRCCONF=/dev/null TB --- 2013-06-12 18:20:15 - TARGET=mips TB --- 2013-06-12 18:20:15 - TARGET_ARCH=mips64 TB --- 2013-06-12 18:20:15 - TZ=UTC TB --- 2013-06-12 18:20:15 - __MAKE_CONF=/dev/null TB --- 2013-06-12 18:20:15 - cd /src TB --- 2013-06-12 18:20:15 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 18:20:22 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 19:08:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 19:08:36 - ERROR: failed to build world TB --- 2013-06-12 19:08:36 - 2102.77 user 475.45 system 2913.71 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips64-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on ia64/ia64
TB --- 2013-06-12 18:10:40 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 18:10:40 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 18:10:40 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-06-12 18:10:40 - cleaning the object tree TB --- 2013-06-12 18:10:40 - /usr/local/bin/svn stat /src TB --- 2013-06-12 18:10:43 - At svn revision 251658 TB --- 2013-06-12 18:10:44 - building world TB --- 2013-06-12 18:10:44 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 18:10:44 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 18:10:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 18:10:44 - SRCCONF=/dev/null TB --- 2013-06-12 18:10:44 - TARGET=ia64 TB --- 2013-06-12 18:10:44 - TARGET_ARCH=ia64 TB --- 2013-06-12 18:10:44 - TZ=UTC TB --- 2013-06-12 18:10:44 - __MAKE_CONF=/dev/null TB --- 2013-06-12 18:10:44 - cd /src TB --- 2013-06-12 18:10:44 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 18:10:51 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 19:17:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 19:17:27 - ERROR: failed to build world TB --- 2013-06-12 19:17:27 - 3173.88 user 539.47 system 4007.52 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on sparc64/sparc64
TB --- 2013-06-12 19:17:28 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 19:17:28 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 19:17:28 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2013-06-12 19:17:28 - cleaning the object tree TB --- 2013-06-12 19:17:28 - /usr/local/bin/svn stat /src TB --- 2013-06-12 19:17:31 - At svn revision 251658 TB --- 2013-06-12 19:17:32 - building world TB --- 2013-06-12 19:17:32 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 19:17:32 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 19:17:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 19:17:32 - SRCCONF=/dev/null TB --- 2013-06-12 19:17:32 - TARGET=sparc64 TB --- 2013-06-12 19:17:32 - TARGET_ARCH=sparc64 TB --- 2013-06-12 19:17:32 - TZ=UTC TB --- 2013-06-12 19:17:32 - __MAKE_CONF=/dev/null TB --- 2013-06-12 19:17:32 - cd /src TB --- 2013-06-12 19:17:32 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 19:17:39 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 20:11:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 20:11:22 - ERROR: failed to build world TB --- 2013-06-12 20:11:22 - 2406.41 user 493.29 system 3234.23 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS?
Hi, I try to update from a pre-clang world (r242511M) to "now" (r251618M). The resulting kernel boots, but while starting some jails (with ezjail from ports, so fairly late in the boot process) I get a kernel panic (IIRC zfs trying to access page 0). Before I try to get some time to debug this, I would like to know if there are some known incompatibilities with my make.conf settings. With gcc I used successfully this: ---snip--- COPTFLAGS= -O2 -pipe CPUTYPE?=core2 ---snip--- With those settings I first did a buildworld, then a buildkernel with the r251618 sources. Are there some known issues with those settings? If yes, any suggestions what I should use instead? If not, would it be beneficial to try with different settings (which ones)? Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS?
On Jun 12, 2013, at 22:30, Alexander Leidinger wrote: > I try to update from a pre-clang world (r242511M) to "now" (r251618M). > The resulting kernel boots, but while starting some jails (with ezjail > from ports, so fairly late in the boot process) I get a kernel panic > (IIRC zfs trying to access page 0). If you are running on i386, it might be a stack overflow? Try increasing the stack a little, it might help in that case. In any case, please try to get a backtrace. > Before I try to get some time to debug this, I would like to know if > there are some known incompatibilities with my make.conf settings. With > gcc I used successfully this: > ---snip--- > COPTFLAGS= -O2 -pipe > CPUTYPE?=core2 > ---snip--- > > With those settings I first did a buildworld, then a buildkernel with > the r251618 sources. > > Are there some known issues with those settings? If yes, any suggestions > what I should use instead? If not, would it be beneficial to try with > different settings (which ones)? "-O2 -pipe" is the default setting, so it should work. I personally also always use CPUTYPE core2, and I have never seen any panics. Then again, I do not usually use jails intensively... -Dimitry ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on i386/pc98
TB --- 2013-06-12 18:10:31 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 18:10:31 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 18:10:31 - starting HEAD tinderbox run for i386/pc98 TB --- 2013-06-12 18:10:31 - cleaning the object tree TB --- 2013-06-12 18:10:31 - /usr/local/bin/svn stat /src TB --- 2013-06-12 18:10:35 - At svn revision 251658 TB --- 2013-06-12 18:10:36 - building world TB --- 2013-06-12 18:10:36 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 18:10:36 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 18:10:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 18:10:36 - SRCCONF=/dev/null TB --- 2013-06-12 18:10:36 - TARGET=pc98 TB --- 2013-06-12 18:10:36 - TARGET_ARCH=i386 TB --- 2013-06-12 18:10:36 - TZ=UTC TB --- 2013-06-12 18:10:36 - __MAKE_CONF=/dev/null TB --- 2013-06-12 18:10:36 - cd /src TB --- 2013-06-12 18:10:36 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 18:10:43 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 21:01:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 21:01:03 - ERROR: failed to build world TB --- 2013-06-12 21:01:03 - 8749.38 user 1041.43 system 10231.15 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on powerpc/powerpc
TB --- 2013-06-12 19:08:31 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 19:08:31 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 19:08:31 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2013-06-12 19:08:31 - cleaning the object tree TB --- 2013-06-12 19:08:31 - /usr/local/bin/svn stat /src TB --- 2013-06-12 19:08:35 - At svn revision 251658 TB --- 2013-06-12 19:08:36 - building world TB --- 2013-06-12 19:08:36 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 19:08:36 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 19:08:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 19:08:36 - SRCCONF=/dev/null TB --- 2013-06-12 19:08:36 - TARGET=powerpc TB --- 2013-06-12 19:08:36 - TARGET_ARCH=powerpc TB --- 2013-06-12 19:08:36 - TZ=UTC TB --- 2013-06-12 19:08:36 - __MAKE_CONF=/dev/null TB --- 2013-06-12 19:08:36 - cd /src TB --- 2013-06-12 19:08:36 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 19:08:43 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 21:24:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 21:24:23 - ERROR: failed to build world TB --- 2013-06-12 21:24:23 - 7038.75 user 905.14 system 8152.06 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on powerpc64/powerpc
TB --- 2013-06-12 19:08:36 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-12 19:08:36 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-12 19:08:36 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2013-06-12 19:08:36 - cleaning the object tree TB --- 2013-06-12 19:08:36 - /usr/local/bin/svn stat /src TB --- 2013-06-12 19:08:39 - At svn revision 251658 TB --- 2013-06-12 19:08:40 - building world TB --- 2013-06-12 19:08:40 - CROSS_BUILD_TESTING=YES TB --- 2013-06-12 19:08:40 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-12 19:08:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-12 19:08:40 - SRCCONF=/dev/null TB --- 2013-06-12 19:08:40 - TARGET=powerpc TB --- 2013-06-12 19:08:40 - TARGET_ARCH=powerpc64 TB --- 2013-06-12 19:08:40 - TZ=UTC TB --- 2013-06-12 19:08:40 - __MAKE_CONF=/dev/null TB --- 2013-06-12 19:08:40 - cd /src TB --- 2013-06-12 19:08:40 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Wed Jun 12 19:08:47 UTC 2013 >>> 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 [...] *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-12 21:25:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-12 21:25:01 - ERROR: failed to build world TB --- 2013-06-12 21:25:01 - 7096.42 user 912.99 system 8185.57 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc64-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS?
On Wed, Jun 12, 2013 at 1:39 PM, Dimitry Andric wrote: > On Jun 12, 2013, at 22:30, Alexander Leidinger > wrote: >> I try to update from a pre-clang world (r242511M) to "now" (r251618M). >> The resulting kernel boots, but while starting some jails (with ezjail >> from ports, so fairly late in the boot process) I get a kernel panic >> (IIRC zfs trying to access page 0). > > If you are running on i386, it might be a stack overflow? Try > increasing the stack a little, it might help in that case. > For i386 I'd be more inclined to suspect KVA exhaustion. For non-PAE, as a shot in the dark, increase options KVA_PAGES=384 .. the default is 256 for PAE. that increases kernel KVA from 1GB to 1.5GB. For a PAE system, this number is multipled by 2, so a corresponding change is 512 -> 768. This is just a shot in the dark. If this is amd64, then never mind, KVA_PAGES is meaningless there. -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV On IRC, talking about C++: I think that it is a good thing I will never meet Bjarne on a street cause really, I don't want to end up in prison or anything ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS?
On 6/12/13 3:10 PM, Peter Wemm wrote: On Wed, Jun 12, 2013 at 1:39 PM, Dimitry Andric wrote: On Jun 12, 2013, at 22:30, Alexander Leidinger wrote: I try to update from a pre-clang world (r242511M) to "now" (r251618M). The resulting kernel boots, but while starting some jails (with ezjail from ports, so fairly late in the boot process) I get a kernel panic (IIRC zfs trying to access page 0). If you are running on i386, it might be a stack overflow? Try increasing the stack a little, it might help in that case. For i386 I'd be more inclined to suspect KVA exhaustion. For non-PAE, as a shot in the dark, increase options KVA_PAGES=384 .. the default is 256 for PAE. that increases kernel KVA from 1GB to 1.5GB. For a PAE system, this number is multipled by 2, so a corresponding change is 512 -> 768. This is just a shot in the dark. If this is amd64, then never mind, KVA_PAGES is meaningless there. Is there some way we can get a pps ratelimited (or even one-time) message when the kva is almost exhausted? Could that help people? -- Alfred Perlstein VP Software Engineering, iXsystems ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
