For the last week or so, I've been unable to run chrome. Any attempt
to start it up will cause the system either to freeze up or reboot.
To make matters worse, no trace of what's happening is anywhere to be
found. Nothing in any log files. The system doesn't drop into the
kernel debugger, eithe
> I recently ran "make delete-old" on a -current box and felt it was
> rather slow. That prompted me to do some more careful experiments.
>
> On one box where I have both 8-stable and 9-stable available, there
> was a ~30x slowdown (based on 5 runs, ignoring the first). I don't
> have a -current
On 5/16/2012 6:02 PM, Outback Dingo wrote:
Guess his next claim will be that the kernel was forked from minix,
and userland came from QNX... some people are just plain
(biting my tongue)
You guys DO realize that's a troll website, right? And you're being
seriously trolled.. right
On 2012-May-16 18:11:32 -0700, Devin Teske wrote:
>Right now, I believe the most useful comparison between systems is
>(assuming UFS is in play) the output of "tunefs -p" for the
>filesystem that the slowness is appearing on.
These systems all run ZFS and apart from the first run, there doesn't
s
On May 16, 2012, at 4:06 PM, Peter Jeremy wrote:
> I recently ran "make delete-old" on a -current box and felt it was
> rather slow. That prompted me to do some more careful experiments.
>
> On one box where I have both 8-stable and 9-stable available, there
> was a ~30x slowdown (based on 5 ru
I recently ran "make delete-old" on a -current box and felt it was
rather slow. That prompted me to do some more careful experiments.
On one box where I have both 8-stable and 9-stable available, there
was a ~30x slowdown (based on 5 runs, ignoring the first). I don't
have a -current world on th
On Wed, May 16, 2012 at 5:44 PM, Thomas Mueller wrote:
> Umm, it's about as factual as The Onion, except not as funny. FreeBSD
> never had to "jettison two thirds of its code base and start from
> scratch". Apple is not involved in FreeBSD development. No Mac OS X or
> Darwin version "includes"
On 2012-05-16 20:48, O. Hartmann wrote:> When compiling world (make buildworld)
I receive the bewlo error, which
> seems very strange!
> The error occured out of the blue on a FreeBSD 10.0-CURRENT/amd64 box.
...
> /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol
> `_ZNSi6ignoreEv@GLIBCXX_3
Umm, it's about as factual as The Onion, except not as funny. FreeBSD
never had to "jettison two thirds of its code base and start from
scratch". Apple is not involved in FreeBSD development. No Mac OS X or
Darwin version "includes" FreeBSD. FreeBSD and Mac OS X will never
merge. FreeBSD was n
On 2012-05-16 23:18, Joel Dahl wrote:> Hi,
> I did a buildworld+buildkernel on my workstation today and buildkernel fails
> with:
>
> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> -Wpoint
On Wed, May 16, 2012 at 11:18:26PM +0200, Joel Dahl wrote:
> Hi,
>
> I did a buildworld+buildkernel on my workstation today and buildkernel fails
> with:
>
> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmis
Hi,
I did a buildworld+buildkernel on my workstation today and buildkernel fails
with:
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointe
On Wednesday, May 16, 2012 12:18:25 pm Andriy Gapon wrote:
> on 16/05/2012 17:50 John Baldwin said the following:
> > On Tuesday, May 15, 2012 12:35:12 pm Andriy Gapon wrote:
> >> Not sure what you disagree with...
> >> First, the wildcard device is added to the child list during the walk.
> >> The
Hi All,
When ifp->if_ioctl() is invoked for the ioctl cmd SIOCADDMULTI,
IN_MULTI_LOCK() is called in one of the functions in_joingroup() in the caller
stack.
>From netinet/in_var.h, line 357 : #define IN_MULTI_LOCK()
>mtx_lock(&in_multi_mtx)
>From netinet/in_mcast.c
1098 in_joi
When compiling world (make buildworld) I receive the bewlo error, which
seems very strange!
The error occured out of the blue on a FreeBSD 10.0-CURRENT/amd64 box.
The line
/usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol
`_ZNSi6ignoreEv@GLIBCXX_3.4' changed from 243 in
/usr/obj/usr/src/tm
TB --- 2012-05-16 17:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-05-16 17:10:00 - 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 --- 2012-
on 16/05/2012 17:50 John Baldwin said the following:
> On Tuesday, May 15, 2012 12:35:12 pm Andriy Gapon wrote:
>> Not sure what you disagree with...
>> First, the wildcard device is added to the child list during the walk.
>> Then, the unit 0 device is added to the list when acpi_timer identify is
Hello;
On 05/12/12 17:49, Mateusz Guzik wrote:
Gave this a spin and found what looks like a deadlock:
http://people.freebsd.org/~pho/stress/log/ext2fs.txt
Not a new problem, it would seem. Same issue with 8.3-PRERELEASE r232656M.
pid 2680 (fts) holds lock for vnode cb4be414 and tries to loc
On Wed, May 16, 2012 at 11:08:05AM -0400, John Baldwin wrote:
> On Wednesday, May 16, 2012 4:45:51 am Anton Shterenlikht wrote:
> > On Tue, May 15, 2012 at 12:11:09PM -0400, John Baldwin wrote:
> > > On Monday, May 07, 2012 5:25:02 pm Anton Shterenlikht wrote:
> > > > On Mon, May 07, 2012 at 10:39:
On Mon, 9 Apr 2012, O. Hartmann wrote:
Am 04/08/12 17:29, schrieb David Wolfskill:
*snip*
* I don't know that this is different, but it may well be: my
xorg.conf
includes a stanza:
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
I should go with this
On Wednesday, May 16, 2012 4:45:51 am Anton Shterenlikht wrote:
> On Tue, May 15, 2012 at 12:11:09PM -0400, John Baldwin wrote:
> > On Monday, May 07, 2012 5:25:02 pm Anton Shterenlikht wrote:
> > > On Mon, May 07, 2012 at 10:39:51AM -0400, John Baldwin wrote:
> > > > On Friday, May 04, 2012 4:07:2
On Tuesday, May 15, 2012 12:35:12 pm Andriy Gapon wrote:
> on 15/05/2012 17:34 John Baldwin said the following:
> > On Monday, May 14, 2012 12:41:37 pm Andriy Gapon wrote:
> >> on 14/05/2012 01:43 Bruce Cran said the following:
> >>> On 13/05/2012 21:06, Andriy Gapon wrote:
> Can you produce a
2012/5/16, Andriy Gapon :
> on 16/05/2012 15:37 Attilio Rao said the following:
>> 2012/5/16, Andriy Gapon :
>>>
>>> I would like to commit something like the following patch.
>>> I think that in-kernel watchdog patting during crash dump is useful with
>>> hardware watchdogs too. The code seems to
on 16/05/2012 15:37 Attilio Rao said the following:
> 2012/5/16, Andriy Gapon :
>>
>> I would like to commit something like the following patch.
>> I think that in-kernel watchdog patting during crash dump is useful with
>> hardware watchdogs too. The code seems to work fine here.
>> In fact, I am
2012/5/16, Andriy Gapon :
>
> I would like to commit something like the following patch.
> I think that in-kernel watchdog patting during crash dump is useful with
> hardware watchdogs too. The code seems to work fine here.
> In fact, I am not sure why wdog_kern_pat was originally tied to
> SW_WAT
- Hans Petter Selasky's Original Message -
> On Friday 11 May 2012 02:54:19 John wrote:
> > Hi Folks,
> >
> >We've been trying to bring freebsd up on a hp dl980g7 for awhile.
> > Due to usb issues, we finally installed onto a revo card and
> > installed it into the 980. The system cons
Vance Siemens writes:
> Can you share a brief overview of what's wrong with it?
Umm, it's about as factual as The Onion, except not as funny. FreeBSD
never had to "jettison two thirds of its code base and start from
scratch". Apple is not involved in FreeBSD development. No Mac OS X or
Darwin
On Wed, May 16, 2012 at 03:12:50PM +1200, Andrew Thompson wrote:
> Hi,
>
>
> Here is a quick patch to limit the sockstat output to a specific jail
> id, this is useful to verify which sockets a jail has open. A jid of 0
> will show the host system.
>
> This will result in an extra syscall per so
I would like to commit something like the following patch.
I think that in-kernel watchdog patting during crash dump is useful with
hardware watchdogs too. The code seems to work fine here.
In fact, I am not sure why wdog_kern_pat was originally tied to SW_WATCHDOG.
commit 59329ca52f5e25266772f1
29 matches
Mail list logo
