When I started with FreeBSD on a G3 B&W, I noticed that the performance
improved with a higher kern.hz rating. Unless the future holds an emu20k2,
there will be RAM used from the motherboard.
1. I will need a real-time or a faster kernel- hence the high rate wanted-
because the devices to be built
Well, why is it reducing latency? That's the thing you should investigate.
Is it because processes aren't getting enough time? or too much time?
Or the audio device isn't getting enough time to run? etc.
-adrian
On 24 July 2013 15:35, Super Bisquit wrote:
> http://lists.freebsd.org/pipermail/
http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html
This is the thread that I was referring to earlier. Since the patch is for
2009, what are the chances it would work with 10.x or 9.x?
On PowerPC machines with a low MHz rate- or any machine with a CPU rate of
800 MHz or
On Wed, Jul 24, 2013 at 03:27:07PM -0500, Pedro Giffuni wrote:
> On 24.07.2013 13:49, Baptiste Daroussin wrote:
> > ...
> >> Yes fuse in base is broken since r248084 downgrade sys/fs/fuse to that
> >> version
> >> and it will work, I'm investigating.
> >>
> >> What I fix is the umount umounting al
On 24.07.2013 13:49, Baptiste Daroussin wrote:
...
Yes fuse in base is broken since r248084 downgrade sys/fs/fuse to that version
and it will work, I'm investigating.
What I fix is the umount umounting all the FS.
regards,
Bapt
Forgot to say r248084 is the last working revision.
Sorry for t
On 24.07.2013 14:07, Baptiste Daroussin wrote:
On Wed, Jul 24, 2013 at 01:55:21PM -0500, Pedro Giffuni wrote:
On 24.07.2013 13:34, Baptiste Daroussin wrote:
On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote:
Hi Pedro,
Bapt tells me that there are FUSE issues in the most recent -HEA
On Wed, Jul 24, 2013 at 01:55:21PM -0500, Pedro Giffuni wrote:
> On 24.07.2013 13:34, Baptiste Daroussin wrote:
> > On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote:
> >> Hi Pedro,
> >>
> >> Bapt tells me that there are FUSE issues in the most recent -HEAD and
> >> it's stopping poudrie
On 24.07.2013 13:34, Baptiste Daroussin wrote:
On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote:
Hi Pedro,
Bapt tells me that there are FUSE issues in the most recent -HEAD and
it's stopping poudriere from running.
Nah poudriere does not use yet fuse :)
What's the story here?
I
On Wed, Jul 24, 2013 at 08:36:10PM +0200, Baptiste Daroussin wrote:
> On Wed, Jul 24, 2013 at 09:16:44PM +0300, Alexander Panyushkin wrote:
> > 24.07.2013 18:22, Baptiste Daroussin пишет:
> > > On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote:
> > >> On Fri, Jul 19, 2013 at 6:22 PM, Pe
On Wed, Jul 24, 2013 at 09:16:44PM +0300, Alexander Panyushkin wrote:
> 24.07.2013 18:22, Baptiste Daroussin пишет:
> > On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote:
> >> On Fri, Jul 19, 2013 at 6:22 PM, Pedro Giffuni wrote:
> >>
> >>> On 19.07.2013 12:07, Alexander Panyushkin wro
Hi;
El 24/07/2013 1:22 p. m., Adrian Chadd escribió:
Hi Pedro,
Bapt tells me that there are FUSE issues in the most recent -HEAD and
it's stopping poudriere from running.
What's the story here?
I reverted all my birthtime changes, the remaining change is only a
header update from upstream
On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote:
> Hi Pedro,
>
> Bapt tells me that there are FUSE issues in the most recent -HEAD and
> it's stopping poudriere from running.
Nah poudriere does not use yet fuse :)
>
> What's the story here?
>
I was about to mail you :)
It is broke
Hi Pedro,
Bapt tells me that there are FUSE issues in the most recent -HEAD and
it's stopping poudriere from running.
What's the story here?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
24.07.2013 18:22, Baptiste Daroussin пишет:
On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote:
On Fri, Jul 19, 2013 at 6:22 PM, Pedro Giffuni wrote:
On 19.07.2013 12:07, Alexander Panyushkin wrote:
19.07.2013 19:42, Pedro Giffuni пишет:
(re-posting since the original response
On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote:
> On Fri, Jul 19, 2013 at 6:22 PM, Pedro Giffuni wrote:
>
> > On 19.07.2013 12:07, Alexander Panyushkin wrote:
> >
> >> 19.07.2013 19:42, Pedro Giffuni пишет:
> >>
> >>> (re-posting since the original response didn't make it through)
20.07.2013 18:02, Pedro Giffuni пишет:
On 19.07.2013 23:42, Kevin Oberman wrote:
...
fuse is at least partly broken in -current. I discovered that if you
mount two devices that use fuse, when you umount any of them, ll are
marked as not mounted and disappear from df(1) or mount(8) output,
b
On Wed, Jul 24, 2013 at 4:02 AM, Alexander Motin wrote:
> cam.k kernel module includes all existing periph drivers in one bundle.
> Loading cam.ko you are probably getting sg driver also, that triggers
> reported issue. You may try to rip out sg with single line hack to module's
> Makefile. The re
on 22/07/2013 23:38 Pawel Jakub Dawidek said the following:
> On Mon, Jul 22, 2013 at 10:29:40AM +0300, Andriy Gapon wrote:
>> I think that this setup (on ZFS level) is quite untypical, although not
>> impossible on FreeBSD (and perhaps only FreeBSD).
>> It's untypical because you have separate boo
What does zdb on each device report?
Regards
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, co
19 matches
Mail list logo
