On Thu, Oct 23, 2014 at 10:03:29PM +0300, Konstantin Belousov wrote:
> On Wed, Oct 22, 2014 at 03:59:23PM -0400, Adam McDougall wrote:
> > On 10/22/2014 08:26, Konstantin Belousov wrote:
>
> Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one
> private report of the patch worked
I was able to complete a ZFS replication by manually intervening each
time "zfs recv" blocked on "kmem arena": running the program at the end
was sufficient to unblock zfs each of the 17 times it stalled.
The program is intended to consume about 24GB RAM out of 32GB physical
RAM, thereby pressurin
Kostik wrote:
> On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote:
> > Beeblebrox wrote:
> > > Sorry guys, we have a considerable time-zone difference.
> > >
> > > >> It appears that the sysctl must be set before mountd, nfsd are
> > > >> started to take effect. (Or they must be restart
I would be using such a patch as soon as it was available. On a friend's
advice, I upgraded a ZFS server here at home with an AMD 9590 and 32Gig of
RAM. I'd dearly like to use it to track down the netgraph bug (see my
other recent posts), but it doesn't currently qualify.
On Sat, Oct 25, 2014 at
Beeblebrox wrote:
Dan:
>> to get pxeboot to do v3, add to /boot/loader.conf
>> boot-nfsroot-options="nfsv3"
>Thanks. I'm using grub for the bootloader and menu, and comparable entry
>should be:
>set kfreebsd.boot.nfsroot.options=3D"nfsv3"
>It does not work however. mount_root hangs for a while the
Beeblebrox wrote:
> Dan:
> >> to get pxeboot to do v3, add to /boot/loader.conf
> >> boot-nfsroot-options=“nfsv3”
> Thanks. I'm using grub for the bootloader and menu, and comparable
> entry should be:
> set kfreebsd.boot.nfsroot.options="nfsv3"
> It does not work however. mount_root hangs for a wh
Dan:
>> to get pxeboot to do v3, add to /boot/loader.conf
>> boot-nfsroot-options=“nfsv3”
Thanks. I'm using grub for the bootloader and menu, and comparable entry should
be:
set kfreebsd.boot.nfsroot.options="nfsv3"
It does not work however. mount_root hangs for a while then reverts to V2. I've
a
On Sunday 26 October 2014 14:18:47 Dimitry Andric wrote:
>
> Your config executable is too old. Most likely, you need to run "make
> kernel-toolchain" first.
>
Thank you very much, that helped.
--
wbr, Maxim Filimonov
c...@bein.link
___
freebsd-curre
On Sat, Oct 25, 2014 at 1:45 PM, Mateusz Guzik wrote:
> Hello,
>
> In short, nice kernel tasks people with C language skills can do in few
> evenings.
>
> https://wiki.freebsd.org/JuniorJobs
>
>
Thanks for making that list. I was looking at some other projects,
and noticed that on the front page
Nice info...
On Sat, Oct 25, 2014 at 11:45 PM, Mateusz Guzik wrote:
> Hello,
>
> In short, nice kernel tasks people with C language skills can do in few
> evenings.
>
> https://wiki.freebsd.org/JuniorJobs
>
> It is assumed you know how to obtain sources and build the kernel.
>
> What you can get
On 25 Oct 2014, at 23:39, Maxim V FIlimonov wrote:
>
> I'm trying to build the current FreeBSD kernel, and that's what I get:
>
> % sudo make buildkernel
>
> --
Kernel build for GENERIC started on Sun Oct 26 01:39:13 MSK 2014
> --
On Mon, 20 Oct 2014 18:21:58 -0400
Allan Jude wrote:
> On 2014-10-20 17:15, Chris H wrote:
> > On Mon, 20 Oct 2014 14:32:53 -0400 Mason Loring Bliss
> > wrote
> >
> >> On Sat, Oct 18, 2014 at 02:58:57PM +0900, Tomoaki AOKI wrote:
> >>
> >>> I think the advantages of the forum are...
> >>>
> >>
On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote:
> Beeblebrox wrote:
> > Sorry guys, we have a considerable time-zone difference.
> >
> > >> It appears that the sysctl must be set before mountd, nfsd are
> > >> started to take effect. (Or they must be restarted after it is
> > >> set.
Beeblebrox wrote:
> Sorry guys, we have a considerable time-zone difference.
>
> >> It appears that the sysctl must be set before mountd, nfsd are
> >> started to take effect. (Or they must be restarted after it is
> >> set.)
> I had apparently re-started nfsd but not mountd. This time
> re-starti
Beeblebrox wrote:
> Sorry guys, we have a considerable time-zone difference.
>
> >> It appears that the sysctl must be set before mountd, nfsd are
> >> started to take effect. (Or they must be restarted after it is
> >> set.)
> I had apparently re-started nfsd but not mountd. This time
> re-starti
Hans Petter Selasky wrote:
> On 10/23/14 16:28, Fabian Keil wrote:
> > kldunload umass.ko lead to a panic, dumping didn't work.
> >
> > Screenshots are available at:
> > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r273434-usb/
> >
> > I've seen locked-up usbconfig processes in the past,
> On Oct 26, 2014, at 10:48 AM, Beeblebrox wrote:
>
> Sorry guys, we have a considerable time-zone difference.
>
>>> It appears that the sysctl must be set before mountd, nfsd are
>>> started to take effect. (Or they must be restarted after it is set.)
> I had apparently re-started nfsd but not
Sorry guys, we have a considerable time-zone difference.
>> It appears that the sysctl must be set before mountd, nfsd are
>> started to take effect. (Or they must be restarted after it is set.)
I had apparently re-started nfsd but not mountd. This time re-starting both and
launching the PXE clie
18 matches
Mail list logo
