The NDISulator is a crutch from a time when there wasn't _any_ real
alternative.
There are plenty of alternatives now. What's lacking is desire and
person-power. But the datasheets are there, or the vendor code has been
released, or there's linux/otherbsd drivers.
Leaving it in there is
On 22 Oct 2013, at 00:43, Sean Bruno sean_br...@yahoo.com wrote:
Heh, Matthew suggested the obvious in private mail, it seems that this
would be better spelled as isalpha :-)
This looks wrong. The behaviour of isalpha() depends on the current locale.
You probably want isalpha_l(), with the
I've just upgraded to 11-CURRENT and noticed a couple of new
cam_periph_mapmem warnings in the dmesg output:
Trying to mount root from zfs:zroot []...
WARNING: attempt to domain_add(netgraph) after domainfinalize()
cam_periph_mapmem: attempt to map 2779097930 bytes, which is greater
than 65536
Ок, just up to now no error on l2arc
L2 ARC Summary: (HEALTHY)
Passed Headroom:1.99m
Tried Lock Failures:144.53m
IO In Progress: 130.15k
Low Memory Aborts: 7
Free on
First off I just wanted to clarify that you don't need to compression on
dataset for L2ARC to use LZ4 compression, it does this by default as is
not currently configurable.
Next up I believe we've found the cause of this high load and I've just
committed the fix to head:
First of all Thank you for help.
As for high load on system, looks like problems with l2arc have litle impact on
load comparatively to another just now
not fully classifed things.
Looks like ower internal software and libs that it use didn't like new VMEM
subsystem, at last
system behavior
If you are still seeing high load try commenting out the following
which should disable l2arc compression.
sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c
if (l2arc_compress)
hdr-b_flags |= ARC_L2COMPRESS;
Regards
Steve
- Original Message -
From: Vitalij
Hi all.
I'm playing with 10 beta1 and found that:
/usr/ports/editors/vim# make
make: /etc/make.conf line 17: warning: WITH_BDB_VER=5
make: /etc/make.conf line 18: Need an operator
make: /etc/make.conf line 17: warning:
_JAVA_PREFERRED_PORTS=JAVA_PORT_NATIVE_OPENJDK_JDK_1_7
make:
On Mon, 21 Oct 2013 22:34:45 +0200 Ulrich Spörlein wrote:
On Mon, 2013-10-21 at 13:18:55 +0200, Tilman Keskinöz wrote:
* Ulrich Spörlein [Sun, 20 Oct 2013 20:27:23 +0200]:
ever since that iconv thing replaced the ports version, I run into
trouble with several ports that I have installed on a
2013/10/22 Tijl Coosemans t...@coosemans.org:
On Mon, 21 Oct 2013 22:34:45 +0200 Ulrich Spörlein wrote:
On Mon, 2013-10-21 at 13:18:55 +0200, Tilman Keskinöz wrote:
* Ulrich Spörlein [Sun, 20 Oct 2013 20:27:23 +0200]:
ever since that iconv thing replaced the ports version, I run into
trouble
2013/10/22 Ulrich Spörlein u...@freebsd.org:
2013/10/22 Tijl Coosemans t...@coosemans.org:
On Mon, 21 Oct 2013 22:34:45 +0200 Ulrich Spörlein wrote:
On Mon, 2013-10-21 at 13:18:55 +0200, Tilman Keskinöz wrote:
* Ulrich Spörlein [Sun, 20 Oct 2013 20:27:23 +0200]:
ever since that iconv thing
TB --- 2013-10-22 23:28:44 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-22 23:28:44 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
I get a gnop lock panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock gnop lock 0xf80002566640 already initialized
# kgdb /boot/kernel.r256923/kernel /var/crash/vmcore.last
...
Unread portion of the kernel message buffer:
panic: lock gnop lock
Encountered twice:
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0x802e612a
stack pointer = 0x28:0xfe118af62b20
frame pointer = 0x28:0xfe118af62b60
code segment= base 0x0,
OK, here's a bit of history of this box. Never wanted to run CURRENT,
but had no choice, STABLE wouldn't boot. So I followed all the advice
how to disable all debugging features. Now I'm trying to build latest
10 and I'm getting the error below.
What's wrong?
cc -O2 -pipe -march=core2
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
I get a gnop lock panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock gnop lock 0xf80002566640 already initialized
# kgdb /boot/kernel.r256923/kernel /var/crash/vmcore.last
...
Unread
On Tue, Oct 22, 2013 at 07:49:21PM -0500, Saul A. Peebsen wrote:
OK, here's a bit of history of this box. Never wanted to run CURRENT,
but had no choice, STABLE wouldn't boot. So I followed all the advice
how to disable all debugging features. Now I'm trying to build latest
10 and I'm getting
On Wed, 23 Oct 2013, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
I get a gnop lock panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock gnop lock 0xf80002566640 already initialized
# kgdb
On 10/22/13 20:55, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:49:21PM -0500, Saul A. Peebsen wrote:
OK, here's a bit of history of this box. Never wanted to run CURRENT,
but had no choice, STABLE wouldn't boot. So I followed all the advice
how to disable all debugging features. Now I'm
On Wed, 23 Oct 2013 02:55:02 +0200
Mateusz Guzik mjgu...@gmail.com wrote:
On Tue, Oct 22, 2013 at 07:49:21PM -0500, Saul A. Peebsen wrote:
OK, here's a bit of history of this box. Never wanted to run
CURRENT, but had no choice, STABLE wouldn't boot. So I followed all
the advice how to
On Tue, Oct 22, 2013 at 09:15:45PM -0400, Keith White wrote:
On Wed, 23 Oct 2013, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
I get a gnop lock panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock gnop lock
Regresssion in 10.0-BETA1, mdconfig -l -v return code changed from 0
to 255. OK, its not specfied in manual, but has changed.
A test script I was using caught it:
http://www.berklix.com/~jhs/bin/sh/mdconfig_tst
Probably in next day or 2 I'll hack the C send-pr.
Julian
--
Julian Stacey,
On 23/10/2013 11:50, Saul A. Peebsen wrote:
Never wanted to run CURRENT, but had no choice, STABLE wouldn't boot.
is there anything else I need to modify to move from
10-CURRENT to BETA and ultimately to RELEASE?
I believe HEAD has been renamed to 11-CURRENT
stable/10 was created 12 days
Julian H. Stacey j...@berklix.com wrote
in 201310230254.r9n2sld1067...@fire.js.berklix.net:
jh Regresssion in 10.0-BETA1, mdconfig -l -v return code changed from 0
jh to 255. OK, its not specfied in manual, but has changed.
jh A test script I was using caught it:
jh
Hi there,
Just now my pretty fresh 11-CURRENT rebooted unexpectedly in the middle of
'svn up'. Some information from core.txt.0 (full version available upon
request) given in the end of this email. (Machine: 11.0-CURRENT/i386 built
on Oct 18, GENERIC kernel, default install, single / partition
25 matches
Mail list logo
