On 09/02/2010 04:55, Rob Farmer wrote:
>
> I tried applying the patch to r212087 to rule out recent changes to
> dtrace, but it made no difference. I used patch -E -p0 < patch.
>
Hi Rob,
I see that in your build error are a bunch of things to do with atomic.h
and I recalled a patch from pjd@ on
on 02/09/2010 23:23 Randy Stewart said the following:
> Hi all:
>
> So I finally upgraded my 7.3stable main server to 8.1stable...
>
> And now my backup to atapi-cam is failing.. I get:
>
> r...@lakerest /usr/tmp]# /usr/local/bin/growisofs -Z /dev/cd0 -R -J
> backup_init.08-31-2010.gz
> :-( unab
On Friday, September 03, 2010 01:34:54 Davide Italiano wrote:
> Hi. I've been recently upgraded to -CURRENT (9.0).
> After
> # make buildworld
> # make buildkernel KERNCONF=MYKERNEL
> # make install kernel KERNCONF=MYKERNEL
>
> I have rebooted to single-user mode, as suggested in the documentation
On Thu, Sep 2, 2010 at 11:10 PM, Adam Vande More wrote:
> Wouldn't it be a lot easier to have a nice article on installing
> /usr/ports/misc/freebsd-doc-* from the date of the release of the installed
> system? Or maybe offer archive web access to a handbook snapshot from that
> date(Django does
On Thu, Sep 2, 2010 at 5:54 PM, Daniel Gerzo wrote:
> I actually think there is some point in this idea. The problem is that many
> times we just leave notes or warnings specific for given releases, which can
> many times lead to confusion (or people just don't notice) and as time goes
> and we c
I actually think there is some point in this idea. The problem is that many
times we just leave notes or warnings specific for given releases, which can
many times lead to confusion (or people just don't notice) and as time goes and
we cut the support for given releases they get stale (e.g. We h
Hi. I've been recently upgraded to -CURRENT (9.0).
After
# make buildworld
# make buildkernel KERNCONF=MYKERNEL
# make install kernel KERNCONF=MYKERNEL
I have rebooted to single-user mode, as suggested in the documentation.
No more wireless connection. I've a intel 2200 bg wireless card,
running u
Hi all:
So I finally upgraded my 7.3stable main server to 8.1stable...
And now my backup to atapi-cam is failing.. I get:
r...@lakerest /usr/tmp]# /usr/local/bin/growisofs -Z /dev/cd0 -R -J
backup_init.08-31-2010.gz
:-( unable to CAMGETPASSTHRU for /dev/cd0: Inappropriate ioctl for
device
On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote:
[...]
> Ok, now that I know you read everything carefully, here is the patch:
>
> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
Now it is even easier to test new ZFS! :)
Here you can find VirtualBox Applia
TB --- 2010-09-02 17:57:06 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:57:06 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-09-02 17:57:06 - cleaning the object tree
TB --- 2010-09-02 17:57:23 - cvsupping the source tree
TB --- 2010-09-02 17:57:23 - /usr
TB --- 2010-09-02 17:58:41 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:58:41 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2010-09-02 17:58:41 - cleaning the object tree
TB --- 2010-09-02 17:58:59 - cvsupping the source tree
TB --- 2010-09-02 17:58:59 - /u
Hi Guys,
How well does ZFS on FreeBSD handle a dying/wedged log and/or cache
device? OpenSolaris handles this pretty well in my experience and will
fail through relatively quickly. But this tends to rely on FMA. Thank
you in advance.
-J
___
freebsd-curr
On Thu, Sep 02, 2010 at 06:03:16PM +0100, Anton Shterenlikht wrote:
> On Thu, Sep 02, 2010 at 11:00:14AM +0100, Anton Shterenlikht wrote:
> > I just updated world and kernel from r204991M to r212097 on sparc64.
> >
> > Now I can't ping my gateway. If I boot kernel.old, then
> > the network works f
TB --- 2010-09-02 17:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:20:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-09-02 17:20:00 - cleaning the object tree
TB --- 2010-09-02 17:20:34 - cvsupping the source tree
TB --- 2010-09-02 17:20:34 - /usr/bin/c
TB --- 2010-09-02 17:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:20:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-09-02 17:20:00 - cleaning the object tree
TB --- 2010-09-02 17:20:38 - cvsupping the source tree
TB --- 2010-09-02 17:20:38 - /usr/bin
TB --- 2010-09-02 17:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:20:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-09-02 17:20:00 - cleaning the object tree
TB --- 2010-09-02 17:20:35 - cvsupping the source tree
TB --- 2010-09-02 17:20:35 - /usr/bin/c
TB --- 2010-09-02 17:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-02 17:20:00 - starting HEAD tinderbox run for arm/arm
TB --- 2010-09-02 17:20:00 - cleaning the object tree
TB --- 2010-09-02 17:20:24 - cvsupping the source tree
TB --- 2010-09-02 17:20:24 - /usr/bin/csu
On Thu, Sep 02, 2010 at 11:00:14AM +0100, Anton Shterenlikht wrote:
> I just updated world and kernel from r204991M to r212097 on sparc64.
>
> Now I can't ping my gateway. If I boot kernel.old, then
> the network works fine. As far as I could see mergemaster
> didn't update any network files.
>
>
b. f. wrote:
> In:
> http://people.freebsd.org/~mav/timers_oneshot7.patch
>
> you need to offset the declaration of 'cpu' in getnextevent() on line
> 256 of src/sys/kern/kern_clocksource.c by #ifdef SMP, because it is
> not used otherwise, and will break UP kernel builds with our default
> warning
on 02/09/2010 13:10 Andriy Gapon said the following:
>
> Not sure if this is some local issue or a problem in FreeBSD code.
> I remember minidumps working perfectly well for me, but now I can not get data
> from them.
> Example:
> dmesg -M /var/crash/vmcore.4
> dmesg: _kvm_vatop: direct map addres
In:
http://people.freebsd.org/~mav/timers_oneshot7.patch
you need to offset the declaration of 'cpu' in getnextevent() on line
256 of src/sys/kern/kern_clocksource.c by #ifdef SMP, because it is
not used otherwise, and will break UP kernel builds with our default
warnings and -Werror.
Incidental
Hello,
On Thu, Sep 2, 2010 at 11:45 AM, Niclas Zeising
wrote:
> would it be possible to move that site to the wiki, where
> most other stuff related to FreeBSD development is?
Almost all parts are on the FreeBSD wiki already. Only the main
coordination page (which is only a single HTML page),
Alexander Motin wrote:
> Ian FREISLICH wrote:
> > On Wed, Sep 1, 2010 at 2:16 PM, Alexander Motin wrote:
> >> Brandon Gooch wrote:
> >>> This latest patch causes an interrupt storm with the HPET timer on my
> >>> system. The machine took about 8 minutes to boot and bring me to a
> >>> login prompt
Ian FREISLICH wrote:
> On Wed, Sep 1, 2010 at 2:16 PM, Alexander Motin wrote:
>> Brandon Gooch wrote:
>>> This latest patch causes an interrupt storm with the HPET timer on my
>>> system. The machine took about 8 minutes to boot and bring me to a
>>> login prompt. System interactivity (i.e. input
On 2010-09-02 00:46, Gabor PALI wrote:
Hello there,
I am looking for volunteers who are interested in writing
documentation, i.e. working with the FreeBSD Handbook and the
documentation set. Many of our great documentation writers have
decided to retire from their work over the last years, whic
on 02/09/2010 13:01 Andriy Gapon said the following:
>
> Brian,
>
> after I upgraded my kernel from beginning of July version to end of August
> version I started to get panics in get_next_dirent under parallel FS load,
> like
> e.g. during buildworld with -jN.
>
> Is this something that might
Not sure if this is some local issue or a problem in FreeBSD code.
I remember minidumps working perfectly well for me, but now I can not get data
from them.
Example:
dmesg -M /var/crash/vmcore.4
dmesg: _kvm_vatop: direct map address 0xff012fe0 not in minidump
dmesg: kvm_read: invalid addre
Brian,
after I upgraded my kernel from beginning of July version to end of August
version I started to get panics in get_next_dirent under parallel FS load, like
e.g. during buildworld with -jN.
Is this something that might have been broken by accident and then fixed later?
I've seen that you we
I just updated world and kernel from r204991M to r212097 on sparc64.
Now I can't ping my gateway. If I boot kernel.old, then
the network works fine. As far as I could see mergemaster
didn't update any network files.
Please advise
In the meantime I'll try intermediate revisions.
many thanks
anto
Brian,
after I upgrade from beginning-of-June kernel to end-of-August one (r211758) I
get a panic in get_next_dirent which happens during parallel access to FS like
during buildworld with -jN.
I am upgrading kernel to the latest revision as of today.
Could this be something that you accidentally
On Wed, Sep 1, 2010 at 2:16 PM, Alexander Motin wrote:
> Brandon Gooch wrote:
>> This latest patch causes an interrupt storm with the HPET timer on my
>> system. The machine took about 8 minutes to boot and bring me to a
>> login prompt. System interactivity (i.e. input from keyboard, output
>> on
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrote:
>
> Ok, now that I know you read everything carefully, here is the patch:
>
> http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
>
buildworld on i386 (yes I know ZFS isn't ideal there):
===> cddl/lib/libdtrace (all)
cc
On Thu, Sep 02, 2010 at 01:55:51AM -0700, Rob Farmer wrote:
> On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrote:
> >
> > Ok, now that I know you read everything carefully, here is the patch:
> >
> > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
> >
>
> buildworld o
on 01/09/2010 21:21 Garrett Wollman said the following:
> < said:
>
>> Just want to draw attention of those who use ahci, have hald running and burn
>> optical media to couple of known issues:
>
> What about those of us who use ahci, don't have hald running, and just
> want to read their DVDs?
I
* Mehmet Erol Sanliturk wrote:
> Please separate Handbook with respect to distributions , i.e. , maintain a
> different Handbook for each distribution .
The problem with that is that it will cause documentation for older, but
still supported releases, to become stale. Most doc changes apply to
fu
35 matches
Mail list logo
