On 11/9/13, 1:24 PM, Erik Cederstrand wrote:
Hi Julian,
Den 08/11/2013 kl. 03.02 skrev Julian Elischer :
Some time ago someone showed some freebsd performance graphs graphed against
time.
He had them up on a website that was updated each day or so.
I think they were network perf tests but I'
On Sat, Nov 09, 2013 at 08:29:30PM -0600, Brandon Gooch wrote:
> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
> 5300 to hang after only a few moments of use.
>
> For now, I've just reverted only those aspects of r257133, enabling
> MRR and keeping the rate index lookup, whi
yup, same info as brandon. :)
-a
On 10 November 2013 04:17, Stefan Farfeleder wrote:
> On Sat, Nov 09, 2013 at 08:29:30PM -0600, Brandon Gooch wrote:
>> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
>> 5300 to hang after only a few moments of use.
>>
>> For now, I've just
On 11/09/13 21:23, Allan Jude wrote:
On 2013-11-09 21:13, Adrian Chadd wrote:
On 9 November 2013 17:58, Allan Jude wrote:
Well, if the rc.conf config is specific to the daemon being installed by
the package, then the existing /etc/rc.conf.d/ system works fine, it
just falls down a little on x
I've built the ports with the following lines in my /etc/make.conf:
WITH_NEW_XORG=1
WITH_KMS=1
WITH_GALLIUM=1
And I've attempted to run ``startx''.
The compiler was a very recent version of Clang.
When building the kernel (not the ports):
== /etc/make.conf snippet begins ==
On 2013-11-10 09:04, George Mitchell wrote:
> On 11/09/13 21:23, Allan Jude wrote:
>> On 2013-11-09 21:13, Adrian Chadd wrote:
>>> On 9 November 2013 17:58, Allan Jude wrote:
>>>
Well, if the rc.conf config is specific to the daemon being
installed by
the package, then the existing
On Sun, 10 Nov 2013, Daniel O'Connor wrote:
On 10 Nov 2013, at 24:24, Matthew Seaman wrote:
2) Should ports / packages populate these cron.d directories?
This is a much more interesting question. Effectively its asking
if a port / package should provide some level of automati
On Sun, Nov 10, 2013 at 05:14:58AM -0800, Adrian Chadd wrote:
> yup, same info as brandon. :)
http://pastebin.com/MwfL06z7
Stefan
> On 10 November 2013 04:17, Stefan Farfeleder wrote:
> > On Sat, Nov 09, 2013 at 08:29:30PM -0600, Brandon Gooch wrote:
> >> Turns out that not enabling MRR causes
On Sun, 10 Nov 2013, d...@gmx.com wrote:
I've built the ports with the following lines in my /etc/make.conf:
WITH_NEW_XORG=1
WITH_KMS=1
WITH_GALLIUM=1
And I've attempted to run ``startx''.
My -current is still from ~July 3, and I also got panics
when trying new Xorg. Take the drm devices o
On 2013-11-10 11:21, Warren Block wrote:
> On Sun, 10 Nov 2013, Daniel O'Connor wrote:
>
>>
>> On 10 Nov 2013, at 24:24, Matthew Seaman wrote:
>>>
>>> 2) Should ports / packages populate these cron.d directories?
>>>
>>> This is a much more interesting question. Effectively its asking
>>>
Warren Block schrieb:
[...]
ie either the file is named such that it is ignored by cron
(preferable IMO) or the entries in them are commented out.
Why not just use an additional entry in rc.conf?
rsnapshot_cron="YES"
(If there is a /usr/local/etc/cron.d/rsnapshot, add it to cron on
start/rest
Daniel Eischen wrote, On 11/10/2013 17:40:
My -current is still from ~July 3, and I also got panics
when trying new Xorg. Take the drm devices out of your
kernel configuration and let X load the necessary drm2
devices when it starts. This allowed it to work for me.
Hmm, works for me to avoid
On Sun, 10 Nov 2013, Philipp Ost wrote:
Warren Block schrieb:
[...]
ie either the file is named such that it is ignored by cron
(preferable IMO) or the entries in them are commented out.
Why not just use an additional entry in rc.conf?
rsnapshot_cron="YES"
(If there is a /usr/local/etc/cron
On Nov 10, 2013, at 12:20 PM, d...@gmx.com wrote:
>
> Daniel Eischen wrote, On 11/10/2013 17:40:
>> My -current is still from ~July 3, and I also got panics
>> when trying new Xorg. Take the drm devices out of your
>> kernel configuration and let X load the necessary drm2
>> devices when it star
Right near the end there you have 'status 83' which means 'transmit
failed, long retry hit' (the status codes are in if_iwnreg.h
somewhere.) The retry count hit 16, which is the max set for the
frame.
rate=80 (hex) is MCS0. So, you're seeing retransmits and failures at
MCS0, which is a bad sign.
And for reference, here's the paper:
http://hal.inria.fr/docs/00/07/07/84/PDF/RR-5208.pdf
-adrian
On 10 November 2013 10:48, Adrian Chadd wrote:
> Right near the end there you have 'status 83' which means 'transmit
> failed, long retry hit' (the status codes are in if_iwnreg.h
> somewhere.)
On Sun, Nov 10, 2013 at 10:48:48AM -0800, Adrian Chadd wrote:
> Right near the end there you have 'status 83' which means 'transmit
> failed, long retry hit' (the status codes are in if_iwnreg.h
> somewhere.) The retry count hit 16, which is the max set for the
> frame.
>
> rate=80 (hex) is MCS0.
Den 10/11/2013 kl. 09.45 skrev Julian Elischer :
>
> it would be interesting to know what you did. and what conclusions you came
> to..
I created a system with a build server, a set of slaves, and a website to
collect and publish the benchmark data in graphs and raw data and highlight
signific
Yes. So one of the.. unfortunately broken things in iwn is the ampdu tx
code doesn't do retransmits. So if amrr picks a rate that fails to transmit
everything, the driver doesn't retransmit them. It frees them.
Now when amrr is enabled the hardware will retry at lower rates until
something succeed
On Sun, Nov 10, 2013 at 9:34 AM, Daniel Eischen wrote:
>
> On Nov 10, 2013, at 12:20 PM, d...@gmx.com wrote:
> >
> > Daniel Eischen wrote, On 11/10/2013 17:40:
> >> My -current is still from ~July 3, and I also got panics
> >> when trying new Xorg. Take the drm devices out of your
> >> kernel con
On Nov 10, 2013, at 1:05 PM, Erik Cederstrand wrote:
> Imagine being able to fetch a VirtualBox disk image for a random SVN commit,
> booting it and start debugging right away.
I’ve been working on Crochet’s support for building
VMWare images recently and have started using
that approach to i
On Sat, 9 Nov 2013, Andreas Tobler wrote:
anyone interested in this patch to remove the WEAK_ALIAS and introduce
the WEAK_REFERENCE?
http://people.freebsd.org/~andreast/weak_ref.amd64.diff
I have this running since months on amd64 and I have no issues with.
I remember having had a communicati
On Sun, Nov 10, 2013 at 10:13 AM, Adrian Chadd wrote:
>
> The point I'm making is this:
>
> * when populating rc.conf.d/, don't just do 'cp' in a post-install script
> * when populating the cron daemon entries in rc.cron.d, don't just
> 'cp' in a post-install script.
>
>
sounds like we need a por
On Sat, Nov 09, 2013 at 11:16:08PM +0100, Andreas Tobler wrote:
> Hi all,
>
> anyone interested in this patch to remove the WEAK_ALIAS and introduce
> the WEAK_REFERENCE?
>
> http://people.freebsd.org/~andreast/weak_ref.amd64.diff
>
> I have this running since months on amd64 and I have no issue
24 matches
Mail list logo
