See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/184/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/185/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Hi Current,
It seems like there is constant flow (leak) of memory from ARC to Inact in
FreeBSD 11.0-CURRENT #0 r273165.
Normally, our system (FreeBSD 11.0-CURRENT #5 r260625) keeps ARC size very
close to vfs.zfs.arc_max:
Mem: 16G Active, 324M Inact, 105G Wired, 1612M Cache, 3308M Buf, 1094M
This is likely spikes in uma zones used by ARC.
The VM doesn't ever clean uma zones unless it hits a low memory
condition, which explains why your little script helps.
Check the output of vmstat -z to confirm.
On 04/11/2014 11:47, Dmitriy Makarov wrote:
Hi Current,
It seems like there is
John-Mark Gurney j...@funkthat.com wrote:
John-Mark Gurney wrote this message on Fri, Oct 17, 2014 at 09:58 -0700:
I did some work at this a while back... and if you're interested in
improving performance and willing to do some testing... I can send you
some patches..
There are a
ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP
UMA Kegs: 384, 0, 210, 10, 216, 0, 0
UMA Zones: 2176, 0, 210, 0, 216, 0, 0
UMA Slabs: 80, 0, 2921231, 1024519,133906002, 0, 0
UMA
Hi current@
Maybe this is a transient no one else will see ?:
with no /boot/loader.conf, my old custom kernel booted my new one paniced:
panic: Lock (sx) random_adaptors not locked @ dev/random/random_adaptors.c:278
-r-xr-xr-x 1 root wheel 13625036 Nov 1 18:37
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/186/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Sorry to bring this one back but I see no changes have been made to this in
current.
The issue is that USB devices are detected after the geli prompt and so the
geli paraphrase prompt becomes hidden, and the simple solution would be
to change the order the prompt show as in wait a few secs
Hi!
The issue is that USB devices are detected after the geli prompt and so the
geli paraphrase prompt becomes hidden, and the simple solution would be
to change the order the prompt show as in wait a few secs for the usb
devices to be detected.
I've seen the same issue on 10.x, and a
Miguel Clara miguelmcl...@gmail.com wrote:
Sorry to bring this one back but I see no changes have been made to this in
current.
The issue is that USB devices are detected after the geli prompt and so the
geli paraphrase prompt becomes hidden, and the simple solution would be
to change the
Hi!
If you don't need any USB devices to boot, you can delay their
detection by loading the modules through /etc/rc.d/kld instead
of the loader:
fk@r500 ~ $grep kld /etc/rc.conf
kld_list=usb.ko usb_quirk.ko ehci.ko umass.ko
Does this really help with the GENERIC kernel ?
If I add this to
On Nov 4, 2014, at 0:06, jenkins-ad...@freebsd.org wrote:
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/184/
It appears that some of the new results from the libc testcases are causing
Jenkins to crash in some cases:
-
On 11/04/2014 10:24, Kurt Jaeger wrote:
Hi!
If you don't need any USB devices to boot, you can delay their
detection by loading the modules through /etc/rc.d/kld instead
of the loader:
fk@r500 ~ $grep kld /etc/rc.conf
kld_list=usb.ko usb_quirk.ko ehci.ko umass.ko
Does this really help
Kurt Jaeger p...@opsec.eu wrote:
If you don't need any USB devices to boot, you can delay their
detection by loading the modules through /etc/rc.d/kld instead
of the loader:
fk@r500 ~ $grep kld /etc/rc.conf
kld_list=usb.ko usb_quirk.ko ehci.ko umass.ko
Does this really help with
On 11/04/2014 11:17, Kris Moore wrote:
On 11/04/2014 10:24, Kurt Jaeger wrote:
Hi!
If you don't need any USB devices to boot, you can delay their
detection by loading the modules through /etc/rc.d/kld instead
of the loader:
fk@r500 ~ $grep kld /etc/rc.conf
kld_list=usb.ko usb_quirk.ko
Hello!
As announced a week ago, vt(4) is now the default console driver in
11-CURRENT as of r274085.
You may have to update your console settings in /etc/rc.conf. During
boot, /etc/rc.d/syscons will indicate what you need to do.
The original HEADS UP mentioned several known issues. Among them,
On 11/04/2014 08:22, Dmitriy Makarov wrote:
ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP
UMA Kegs: 384, 0, 210, 10, 216, 0, 0
UMA Zones: 2176, 0, 210, 0, 216, 0, 0
UMA Slabs: 80,
On Nov 4, 2014, at 9:22 AM, Allan Jude allanj...@freebsd.org wrote:
On 11/04/2014 08:22, Dmitriy Makarov wrote:
ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP
UMA Kegs: 384, 0, 210, 10, 216, 0, 0
UMA Zones: 2176,
On 04/11/2014 17:22, Allan Jude wrote:
snip...
Justin Gibbs and I were helping George from Voxer look at the same issue
they are having. They had ~169GB in inact, and only ~60GB being used for
ARC.
Are there any further debugging steps we can recommend to him to help
investigate this?
The
On 04/11/2014 17:57, Ben Perrault wrote:
snip...
I would also be interested in any additional debugging steps and would be
willing to help test in any way I can - as I've seen the behavior a few times
as well. As recently a Sunday evening, I caught a system running with ~44GB ARC
but ~117GB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/04/14 06:01, Julian H. Stacey wrote:
Hi current@
Maybe this is a transient no one else will see ?: with no
/boot/loader.conf, my old custom kernel booted my new one
paniced:
panic: Lock (sx) random_adaptors not locked @
On Tue, Nov 4, 2014 at 5:10 PM, Allan Jude allanj...@freebsd.org wrote:
On 11/04/2014 11:17, Kris Moore wrote:
On 11/04/2014 10:24, Kurt Jaeger wrote:
Hi!
If you don't need any USB devices to boot, you can delay their
detection by loading the modules through /etc/rc.d/kld instead
of
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/187/
--
[...truncated 3505 lines...]
local/lutok/state_test:set_metatable - passed [0.024s]
local/lutok/state_test:set_table__ok - passed [0.023s]
local/lutok/state_test:set_table__nil -
On Nov 4, 2014, at 12:09, jenkins-ad...@freebsd.org wrote:
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/187/
...
Hi Craig/Jenkins admins,
I opened a pull request to increase the timeout from 1 to 2 hours when
running kyua test”:
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/188/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Nov 4, 2014, at 15:10, jenkins-ad...@freebsd.org wrote:
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/188/
Hi!
I’ve filed the following bugs to track these failures. I’ll closely
monitor the tests for another couple hours, then open up reviews to fix the
issues
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD/1772/changes
Changes:
[dumbbell] vt(4): Support syscons' SC_HISTORY_SIZE to configure history size
Therefore, to set histry size to 2000 lines, add the following line to
your kernel configuration file:
options SC_HISTORY_SIZE=2000
--- all_subdir_libdpv ---
static struct config dialogrc_config[] = {
^
/usr/src/lib/libdpv/dialogrc.h:53:8: note: forward declaration of
'struct config'
struct config *dialogrc_config_option(const char *_directive);
^
Fixing!
Sorry! Pointy-Hat (really pointy)
--
Devin
-Original Message-
From: jenkins-ad...@freebsd.org [mailto:jenkins-ad...@freebsd.org]
Sent: Tuesday, November 4, 2014 5:16 PM
To: jenkins-ad...@freebsd.org; freebsd-current@freebsd.org;
dumbb...@freebsd.org;
Build is unbroken ;D Thanks! hehe (and sorry)
http://svnweb.freebsd.org/base?view=revisionrevision=274121
shurd and I learned today that WARNS=6 means something
different on -CURRENT than on 9 or 10 (or at least, the 9 and 10
that I have deployed for my testing [smiles]).
--
Devin
On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sébastien Pédron
jean-sebastien.ped...@dumbbell.fr wrote
Hello!
As announced a week ago, vt(4) is now the default console driver in
11-CURRENT as of r274085.
You may have to update your console settings in /etc/rc.conf. During
boot,
OK OK... my bad!
I wasn't doing buildworld for my test.
This should address the issue... (would love a quick test feedback)
Thank you so much, by the way.
http://svnweb.freebsd.org/base?view=revisionrevision=274123
--
Devin
-Original Message-
From: Larry Rosenman
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD/1773/changes
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/189/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Tue, Nov 04, 2014 at 06:13:44PM +, Steven Hartland wrote:
On 04/11/2014 17:22, Allan Jude wrote:
snip...
Justin Gibbs and I were helping George from Voxer look at the same issue
they are having. They had ~169GB in inact, and only ~60GB being used for
ARC.
Are there any
36 matches
Mail list logo