TB --- 2013-05-22 05:37:29 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 05:37: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 ---
For a short notice:
I have a box that is at the moment stuck with r250670 since this is
version doesn't crash.
Every version above also most recent sources, coredump after several
seconds after the console login shows up with a lot of chat on the
screen regarding CAM and SCSI-like output.
This
Switching off systems running FreeBSD 10.0-CURRENT #3 r250886: Tue May
21 23:12:29 CEST 2013 amd64 but pressing the power button doesn't switch
the box off anymore. The console is stuck with presenting last lines of
syncing disks and several numbers counting down the to-sync blocks.
This happens
TB --- 2013-05-22 06:22:03 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 06:22:03 - 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-05-22 05:46:12 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 05:46:12 - 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-05-22 05:51:51 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 05:51:51 - 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 ---
В Tue, 21 May 2013 12:00:54 -0500
Brooks Davis bro...@freebsd.org пишет:
I belive this is now fixed in r250859. Sorry about the breakage.
-- Brooks
Unfortunately it did not fix the error when building the world.
I still watch an error like this:
--- /usr/bin/ld: this linker was not
Hi,
my buildworlds using ccache have recently begun failing with the message below.
Buildworld without ccache works fine. Any ideas?
CC='/usr/local/libexec/ccache/world/clang
--sysroot=/home/elars/obj/usr/home/elars/src/tmp
-B/home/elars/obj/usr/home/elars/src/tmp/usr/bin' mkdep -f .depend -a
On 05/17/2013 09:45 PM, Florent Peterschmitt wrote:
Hi,
With the r250749 revision of head, rebuilt world with make -j4
buildworld, all was fine.
Then install new world, reboot and so:
$ cd /usr/src
$ make -j4 kernel
--- buildkernel ---
make: illegal option -- J
usage: make
On 2013-05-22 13:01, Eggert, Lars wrote:
my buildworlds using ccache have recently begun failing with the message below.
Buildworld without ccache works fine. Any ideas?
CC='/usr/local/libexec/ccache/world/clang --sysroot=/home/elars/obj/usr/home/elars/src/tmp
On 05/22/2013 01:05 PM, Julian Stecklina wrote:
This also affects building CURRENT from a 9.1 system. One workaround is
to build without -j, but this is quite painful on an 8-core box.
I tried using bmake from ports, but this fails, because the build system
seems to have PATH hardcoded and
TB --- 2013-05-22 13:12:26 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 13:12:26 - 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 Wed, May 22, 2013 at 11:08:56AM +0300, Ivan Klymenko wrote:
?? Tue, 21 May 2013 12:00:54 -0500
Brooks Davis bro...@freebsd.org ??:
I belive this is now fixed in r250859. Sorry about the breakage.
-- Brooks
Unfortunately it did not fix the error when building the world.
On Tue, 2013-05-21 at 04:10:30 +0200, Ulrich Spörlein wrote:
On Mon, 2013-05-20 at 23:06:40 +0200, Matthias Andree wrote:
Am 20.05.2013 15:49, schrieb Ulrich Spörlein:
Hey all,
I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d
ago, now it's kaput:
...
TB --- 2013-05-22 14:22:47 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 14:22:47 - 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 ---
В Wed, 22 May 2013 09:31:57 -0500
Brooks Davis bro...@freebsd.org пишет:
On Wed, May 22, 2013 at 11:08:56AM +0300, Ivan Klymenko wrote:
?? Tue, 21 May 2013 12:00:54 -0500
Brooks Davis bro...@freebsd.org ??:
I belive this is now fixed in r250859. Sorry about the breakage.
TB --- 2013-05-22 15:13:48 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 15:13:48 - 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 Wed, May 22, 2013 at 06:52:14PM +0300, Ivan Klymenko wrote:
?? Wed, 22 May 2013 09:31:57 -0500
Brooks Davis bro...@freebsd.org ??:
On Wed, May 22, 2013 at 11:08:56AM +0300, Ivan Klymenko wrote:
?? Tue, 21 May 2013 12:00:54 -0500
Brooks Davis bro...@freebsd.org ??:
On 22 May 2013 00:03, Jung-uk Kim j...@freebsd.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note flex/lex was updated to 2.5.37 from flex.sourceforge.net and
__FreeBSD_version was bumped to 133.
FYI, I added couple of compatibility shims (just enough to build the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-22 12:24:45 -0400, Sergey Kandaurov wrote:
On 22 May 2013 00:03, Jung-uk Kim j...@freebsd.org wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Please note flex/lex was updated to 2.5.37 from
flex.sourceforge.net and
TB --- 2013-05-22 15:55:29 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 15:55: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 ---
Hi YongHyeon,
Without natd this seems to work fine (both on RELEASE and CURRENT).
Both my Hong-Kong no-name and Edimax EU-4208 seem to behave the same.
This works with natd on RELEASE as well, but just for a limited time.
I've yet to establish if it's time or #packets that cause the
processing
TB --- 2013-05-22 15:19:29 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 15:19: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-05-22 15:25:12 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 15:25:12 - 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 5/21/2013 9:25 AM, Andreas Turriff wrote:
On 5/21/2013 5:33 AM, Konstantin Belousov wrote:
On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote:
On migrating one of my servers to -current, I discovered that the tws
driver panics on boot; I will follow up with a full backtrace
TB --- 2013-05-22 22:52:45 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-22 22:52:45 - 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-05-23 00:08:51 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-23 00:08:51 - 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 ---
When a process is exiting accounting code always allocates new rlimit,
copies old limits over and sets RLIMIT_FSIZE to RLIM_INFINITY.
Since I don't see any good for keeping old limits with exception of
RLIMIT_FSIZE, allocation each time looks unnecessary. Thus I propose the
following:
TB --- 2013-05-23 01:00:03 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-23 01:00:03 - 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-05-23 01:36:27 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-23 01:36:27 - 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 ---
Hi,
I updated my system over night. It suddenly reboots and I find some 20
entries like this in /var/log/message:
May 23 10:05:28 X220 kernel: Fatal trap 3: breakpoint instruction fault
while in kernel mode
May 23 10:05:28 X220 kernel: cpuid = 0; apic id = 00
May 23 10:05:28 X220 kernel:
TB --- 2013-05-23 01:04:02 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-23 01:04: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 ---
TB --- 2013-05-23 01:07:40 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-23 01:07: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 ---
On Thu, May 23, 2013 at 10:25:24AM +0700, Erich Dollansky wrote:
Hi,
I updated my system over night. It suddenly reboots and I find some 20
entries like this in /var/log/message:
May 23 10:05:28 X220 kernel: Fatal trap 3: breakpoint instruction fault
while in kernel mode
May 23 10:05:28
Hi,
On Thu, 23 May 2013 07:23:33 +0300
Konstantin Belousov kostik...@gmail.com wrote:
On Thu, May 23, 2013 at 10:25:24AM +0700, Erich Dollansky wrote:
Hi,
I updated my system over night. It suddenly reboots and I find some
20 entries like this in /var/log/message:
May 23 10:05:28
Hi,
On Thu, 23 May 2013 07:23:33 +0300
Konstantin Belousov kostik...@gmail.com wrote:
On Thu, May 23, 2013 at 10:25:24AM +0700, Erich Dollansky wrote:
uname -a says:
FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #24
r250918: Thu May 23 09:00:07 WIT 2013
36 matches
Mail list logo
