TB --- 2013-09-22 04:12:07 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 04:12:07 - 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 ---
I'm seeing this panic pretty consistently when I try to do a buildworld on
r255764 (i386):
http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.09%20PM.png
I'm not seeing it on r255602, so I suspect it's a recent problem.
Running on VMWare Fusion 6. This was about as
TB --- 2013-09-22 06:03:29 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 06:03:29 - 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 ---
TB --- 2013-09-22 05:46:15 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 05:46:15 - 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 ---
On Sat, 21 Sep 2013 09:34:59 -0700
Davide Italiano dav...@freebsd.org wrote:
On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@freebsd.org
wrote:
On 9/21/2013 11:18 AM, Adam McDougall wrote:
On 09/21/13 09:41, Davide Italiano wrote:
On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
TB --- 2013-09-22 07:16:19 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 07:16: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 ---
TB --- 2013-09-22 06:10:04 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 06:10:04 - 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 ---
On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
I'm seeing this panic pretty consistently when I try to do a buildworld on
r255764 (i386):
http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.09%20PM.png
I'm not seeing it on r255602, so I suspect it's
TB --- 2013-09-22 06:29:31 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-22 06:29: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 ---
Hello, Freebsd-current.
I have fresh and clean 10.0-ALPHA2 (r255763) i386 build. Only changed files in
/etc is rc.conf, master.passwd, group and fstab. It was installed from build
system with make TARGET=i386 TARGET_ARCH=i386 DESTDIR=/mnt installworld
installkernel on newely-created FS, so it
On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels lars.eng...@0x20.net wrote:
On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
I'm seeing this panic pretty consistently when I try to do a buildworld on
r255764 (i386):
On Sun, Sep 22, 2013 at 05:11:30AM -0700, Davide Italiano wrote:
On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels lars.eng...@0x20.net wrote:
On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
I'm seeing this panic pretty consistently when I try to do a buildworld on
r255764 (i386):
On Sun, Sep 22, 2013 at 2:28 PM, Lars Engels lars.eng...@0x20.net wrote:
On Sun, Sep 22, 2013 at 05:11:30AM -0700, Davide Italiano wrote:
On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels lars.eng...@0x20.net wrote:
On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
I'm seeing this
Is it intended that we need to set exec=on for /usr/src after the
include/mk-osreldate.sh addition?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688
On Sun, 2013-09-22 at 09:37 -0500, Larry Rosenman wrote:
Is it intended that we need to set exec=on for /usr/src after the
include/mk-osreldate.sh addition?
Are you saying you have /usr/src mounted with the noexec option and
that's preventing the script from running? The mount manpage
On 2013-09-22 10:41, Ian Lepore wrote:
On Sun, 2013-09-22 at 09:37 -0500, Larry Rosenman wrote:
Is it intended that we need to set exec=on for /usr/src after the
include/mk-osreldate.sh addition?
Are you saying you have /usr/src mounted with the noexec option and
that's preventing the
Got a panic this morning after updating to 10.0-ALPHA-2 today while
installing ports to a clean system.
I can hold the box at the db prompt for a bit if someone wants me to
look at things
Sean
signature.asc
Description: This is a digitally signed message part
I'm trying to build kdelibs on 10.0 Alpha 2, however after 3 triesI get
a panic while building gcc, but I'm not sure if its related or just
coincidence!
---
Kernel 12 trap 12 with interrupts disable
Fatal trap 12: page fault in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x30
On Sun, Sep 22, 2013 at 10:10:42AM -0700, Sean Bruno wrote:
Got a panic this morning after updating to 10.0-ALPHA-2 today while
installing ports to a clean system.
I can hold the box at the db prompt for a bit if someone wants me to
look at things
I think this is fixed with r255788
I noticed on freebsdnews that UEFI support could make it into release.
https://wiki.freebsd.org/UEFI
http://svnweb.freebsd.org/base/projects/uefi/
I've tested it as shown in the wiki link and it only reboots the vm.
I'm just wondering if that news was accurate or if it's still going to be a
long
On Sun, 2013-09-22 at 11:02 -0500, Larry Rosenman wrote:
On 2013-09-22 10:41, Ian Lepore wrote:
On Sun, 2013-09-22 at 09:37 -0500, Larry Rosenman wrote:
Is it intended that we need to set exec=on for /usr/src after the
include/mk-osreldate.sh addition?
Are you saying you have
On Sun, Sep 22, 2013 at 09:41:55AM -0600, Ian Lepore wrote:
On Sun, 2013-09-22 at 09:37 -0500, Larry Rosenman wrote:
Is it intended that we need to set exec=on for /usr/src after the
include/mk-osreldate.sh addition?
Are you saying you have /usr/src mounted with the noexec option
On 20 Sep 2013, at 15:42, Neel Chauhan n...@neelc.org wrote:
This patch is untested
I doubt this will be integrated without any testing. If you can't test, we
should try to find someone that can.
--
Rui Paulo
___
freebsd-current@freebsd.org
Its definatly not related to GCC, I'm getting the same while trying to
buildkernel, I'm trying to upgrade to a more recent current version! Same
kernel panic is showing...
No one else had this problem yet?
Thanks
On Sun, Sep 22, 2013 at 6:12 PM, Miguel Clara miguelmcl...@gmail.comwrote:
I'm
On Sun, Sep 22, 2013 at 1:40 PM, Miguel Clara miguelmcl...@gmail.com wrote:
Its definatly not related to GCC, I'm getting the same while trying to
buildkernel, I'm trying to upgrade to a more recent current version! Same
kernel panic is showing...
No one else had this problem yet?
Thanks
On Sun, Sep 22, 2013 at 1:47 PM, Miguel C. miguelmcl...@gmail.com wrote:
Hum, its probably best to take a scrennshot since I can't copy this from
the console!
attaching the file
That was a regression I introduced, but I'm confident r255788 fixed
the issue. Please update your sources and
On Tue, Sep 10, 2013 at 08:00:02AM +0200, Matthias Andree wrote:
Am 10.09.2013 01:51, schrieb Christos Zoulas:
On Sep 10, 1:21am, d...@des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
wrote:
-- Subject: Re: [PATCH] mtree should not output size if the file is not a
reg
| Roll a large
http://img833.imageshack.us/img833/259/1dpu.jpg
On Sun, Sep 22, 2013 at 9:43 PM, Davide Italiano dav...@freebsd.org wrote:
On Sun, Sep 22, 2013 at 1:40 PM, Miguel Clara miguelmcl...@gmail.com
wrote:
Its definatly not related to GCC, I'm getting the same while trying to
buildkernel, I'm
Hi,
I can test it. I've also a patch for Haswell, which required patching
agp as well in order to get it work, so I guess this patch alone won't
do the trick.
I'll try to test it sometime at the end of next week.
Greetings
Michael
On Sun, 22 Sep 2013, Rui Paulo wrote:
On 20 Sep 2013, at
On Sun, Sep 22, 2013 at 2:06 PM, Miguel Clara miguelmcl...@gmail.comwrote:
I sent the mail again to the list in a smaller size, the first one was
huge ...
Anyway that's the revision I'm trying to build -- r255788 ... but the
problem is, I can't buildkernel, I get a panic while doing it... so
Thanks for the suggestion but I would have tried it If r255788 or newer was
there but its not the case!
I also checked
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/10.0-CURRENT/ but
kernel.txz seems to be outdated too!
I guess the best thing for me at the moment is to wait for a
On Sat, Sep 21, 2013 at 03:42:16PM +0400, Lev Serebryakov wrote:
Hello, Sean.
You wrote 20 2013 ??., 22:39:30:
SB wow, that didn't work at all. :-)
SB I set these in make.conf:
SB CC=/usr/local/bin/clang
SB C++=/usr/local/bin/clang++
SB CPP=/usr/local/bin/clang++
I sent the mail again to the list in a smaller size, the first one was huge
...
Anyway that's the revision I'm trying to build -- r255788 ... but the
problem is, I can't buildkernel, I get a panic while doing it... so unless
there's some kernel.txz available already compile, I'm out of luck!
On Sun, Sep 22, 2013 at 2:47 PM, Miguel Clara miguelmcl...@gmail.com wrote:
Thanks for the suggestion but I would have tried it If r255788 or newer was
there but its not the case!
I also checked
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/10.0-CURRENT/ but
kernel.txz seems
On Sun, Sep 22, 2013 at 03:12:06PM -0700, Davide Italiano wrote:
On Sun, Sep 22, 2013 at 2:47 PM, Miguel Clara miguelmcl...@gmail.com wrote:
Thanks for the suggestion but I would have tried it If r255788 or newer was
there but its not the case!
I also checked
Interesting Idea... I wasn't aware the snapshots were from previous
versions before the regressions, thanks for the heads up!
Time to put this to the test, I'll report back after compiling r255788
thanks!
The link I gave to you contains a snapshot as per r255342 (which is
way before the
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the case, and ${SHELL} is whatever comes from
the environment, which
On 9/22/2013 6:18 PM, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the case, and ${SHELL} is
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set
On Sun, 2013-09-22 at 19:45 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a
On Sun, Sep 22, 2013 at 05:56:07PM -0600, Ian Lepore wrote:
You can hard-code /bin/sh directly, but what I was getting at with the
'#!/usr/bin/env sh' is that the 'sh' interpreter of the build
environment could be used (instead of /bin/sh directly). Then you don't
need to worry about the
43 matches
Mail list logo
