On Monday, February 21, 2011 08:38:03 pm Devin Teske wrote:
>
> Really, the crux of the issue is that our organization is **just now**
> migrating off of FreeBSD-4 (yes, it's true... there are over 1,000
> FreeBSD-4.11 machines running in production at this very moment spanning
> the entire Unite
TB --- 2011-02-22 05:21:04 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-02-22 05:21:04 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2011-02-22 05:21:04 - cleaning the object tree
TB --- 2011-02-22 05:21:20 - cvsupping the source tree
TB --- 2011-02-22 05:21:20 - /u
On Feb 21, 2011, at 2:12 PM, Josh Paetzel wrote:
> On Saturday, February 19, 2011 02:44:42 am Bruce Cran wrote:
>> On Saturday 19 February 2011 03:04:39 Devin Teske wrote:
>>> There are many reasons for this, and none of them are selfish (although
>>> it remains possible to drum-up some selfish r
On Mon, 2011-02-21 at 16:12 -0600, Josh Paetzel wrote:
> pc-sysinstall has been used as the PC-BSD installer for quite a while now,
> and
> has done a lot of installs on a lot of different hardware platforms. I'll
> wager that the compatibility of the shell command gpart is a better bet than
On Mon, 2011-02-21 at 16:12 -0600, Josh Paetzel wrote:
> pc-sysinstall has been used as the PC-BSD installer for quite a while now,
> and
> has done a lot of installs on a lot of different hardware platforms. I'll
> wager that the compatibility of the shell command gpart is a better bet than
Hi,
Any ideas why the bootloader prints a 'error: stack overflow' message
and request
user confirmation to load the kernel manually?
$ uname -a
FreeBSD marina.localdomain 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Wed
Feb 16 03:38:23 EST 2011
root@:/usr/local/freebsd8/src/sys/amd64/compil
On Saturday, February 19, 2011 02:44:42 am Bruce Cran wrote:
> On Saturday 19 February 2011 03:04:39 Devin Teske wrote:
> > There are many reasons for this, and none of them are selfish (although
> > it remains possible to drum-up some selfish reason, all of the reasons
> > behind our motivation ar
On 2/21/2011 4:10 PM, Kostik Belousov wrote:
> Is this reproducable ?
The box seems to have a number of bugs it has been triggering.
g...@freebsd.org's netgraph patch, seems to have fixed one of them. Max seems
to have fixed two others. This one, I am not sure. I can re-enable memguard to
ran
Hello,
> On a Dell E6400 the bluetooth wireless minicard (Dell 370 => BCM2046B1
> if i am right) does not attach to any driver.
> Is this ship supported by the btbcmfw driver?
> Any comment would be helpfull.
did you try to load ng_ubt(4) driver? also freebsd-bluetooth@ is
probably more appropria
On Sun, Feb 20, 2011 at 10:30:52AM -0500, Mike Tancsa wrote:
> On 2/20/2011 9:33 AM, Andrey Smagin wrote:
> > On week -current I have same problem, my box paniced every 2-15 min. I
> > resolve problem by next steps - unplug network connectors from 2 intel em
> > (82574L) cards. I think last time
On Feb 21, 2011, at 8:24 AM, Jerome Flesch wrote:
> While investigating a timing issue with one of our program, we found out
> something weird: We've written a small test program that just calls
> clock_gettime() a lot of times and checks that the time difference between
> calls makes sense. In
On Wed, Nov 3, 2010 at 1:05 PM, Renato Botelho wrote:
> On Wed, Nov 3, 2010 at 12:44 PM, Ed Schouten wrote:
>> * Renato Botelho , 20101103 15:36:
>>> On Wed, Nov 3, 2010 at 11:44 AM, Ed Schouten wrote:
>>> > Garga!
>>> >
>>> > * Renato Botelho , 20101103 13:36:
>>> >> For now i solve my problem
Hi,
> On Tue, 22 Feb 2011 01:50:17 +0900
> Hajimu UMEMOTO said:
bz> Do you have an updated patch for 3.4.1 or 3.3.6? I'd like to help to
bz> you get it in for 9.0-R. I wouldn't even mind if some ports would
bz> conflict with it for a while not making the situation any worse than
bz> it
Hi,
> On Sun, 20 Feb 2011 18:21:18 + (UTC)
> "Bjoern A. Zeeb" said:
bz> Do you have an updated patch for 3.4.1 or 3.3.6? I'd like to help to
bz> you get it in for 9.0-R. I wouldn't even mind if some ports would
bz> conflict with it for a while not making the situation any worse tha
Hello,
While investigating a timing issue with one of our program, we found out
something weird: We've written a small test program that just calls
clock_gettime() a lot of times and checks that the time difference
between calls makes sense. In the end, it seems it doesn't always do.
Calling
I was trying to upgrade my 9.0-CURRENT amd64 after clang
was updated, but i got following error:
===> sys/boot/i386/cdboot (all)
===> sys/boot/i386/gptboot (all)
===> sys/boot/i386/kgzldr (all)
===> sys/boot/i386/libi386 (all)
clang -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600
-
On Mon, Feb 21, 2011 at 12:34 PM, Renato Botelho wrote:
> I was trying to upgrade my 9.0-CURRENT amd64 after clang
> was updated, but i got following error:
>
> ===> sys/boot/i386/cdboot (all)
> ===> sys/boot/i386/gptboot (all)
> ===> sys/boot/i386/kgzldr (all)
> ===> sys/boot/i386/libi386 (all)
>
On 2011-02-21 11:33, Olivier Smedts wrote:
I can't buildworld with Clang since the last update.
...
%cat /etc/src.conf
.if !defined(CC) || ${CC} == "cc"
CC=clang
.endif
.if !defined(CXX) || ${CXX} == "c++"
CXX=clang++
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
Try putting these lines i
Hello,
I can't buildworld with Clang since the last update.
%uname -a
FreeBSD zozo.afpicl.lan 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r218908M:
Mon Feb 21 09:56:35 CET 2011
r...@zozo.afpicl.lan:/usr/obj/usr/src/sys/CORE amd64
%clang -v
FreeBSD clang version 2.9 (trunk 126079) 20110220
Target: x86_64-
today current
crash with loaded mpd5
1st place:
ipwf_chk
ipfw_check_hook
pfil_run_hooks
ip_output
tcp_output repeated
tcp_mtudisc~20 times
tcp_ctlinput
icmp_input
ip_input
swi_net
intr_event_execute_handlers
2nd place
flowtable_lookup
flowteble_lookup_mbuf
ip_output
tcp_output
20 matches
Mail list logo
