Re: virtualbox crash

2020-09-20 Thread Volodymyr Kostyrko

On 20.09.20 16:29, xto...@hotmail.com wrote:

Volodymyr Kostyrko wrote:

Hello.

I'm currently using 12.2-STABLE r365916. After update the host started 
crashing immediately after loading VirtualBox modules. Does anyone 
else experience similar behavior?


Tried rebuilding vbox kernel modules?


Was the first thing to try. No candy. It was working for me on the build 
from ~ Sep 9 or so. Bisecting to find the issue.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


virtualbox crash

2020-09-20 Thread Volodymyr Kostyrko

Hello.

I'm currently using 12.2-STABLE r365916. After update the host started 
crashing immediately after loading VirtualBox modules. Does anyone else 
experience similar behavior?


Thanks in advance.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: All the memory eaten away by ZFS 'solaris' malloc - on 11.1-R amd64

2018-08-13 Thread Volodymyr Kostyrko

23.07.18 18:12, Mark Martinec wrote:

After upgrading an older AMD host from FreeBSD 10.3 to 11.1-RELEASE-p11
(amd64), ZFS is gradually eating up all memory, so that it crashes every
few days when the memory is completely exhausted (after swapping heavily
for a couple of hours).


I've been in the same situation. ZFS, only pool, no ZFS errors.

I think the problem is rather between swapping and ZFS ARC. This host 
has different load, sometimes it needs more active memory, somtimes 
less... This means that active zone can expand and shrink like +-2G os 
mem (I have 16Gb installed there). The problem is, when huge task is 
idle it doesn't use much active memory and other activity is pushing 
it's memory to the swap. When active runs low and ARC runs >50% of 
memory it becomes very hard to make ARC give some memory back. My host 
even was broght to the point when it couldn't get tasks back into memory 
from swap, because while some pages were restored from swap the time 
passes by and the other pages are instead stored to swap due to zome ARC 
activity. Finally active zone shrinks so bad that the host becomes 
unresponsive.


Like 6 month ago I tried tweaking kernel and swap to make things go 
other way. Currently I have `vm.swap_idle_enabled=1` in /etc/loader.conf 
and looks like this solves my problem. The other interesting things to 
look at are `vfs.zfs.arc_free_target`, `vfs.zfs.arc_shrink_shift`, 
`vfs.zfs.arc_grow_retry`.


Or you can take another route and plain limit current ARC size with 
`vfs.zfs.arc_max`.


Hope that helps.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: lightly loaded system eats swap space

2018-06-19 Thread Volodymyr Kostyrko

19.06.18 20:29, Jeremy Chadwick wrote:

(I am not subscribed to -stable, so please CC me, though I doubt I can
help in any way/shape/form past this Email)

Not the first time this has come up -- and every time it has, all that's
heard is crickets in the threads.  Recent proof:

…

I may sound lame but I also faced this issues a few month ago. After a 
few days of load system was trying to push more and more data into the 
swap up to the point that active window becomes too small to handle all 
programs so they should be get back from swap and while they are not 
running something pinches ARC and ARC claims the memory and so on…


I wasn't ever a fan of limiting things. If something requires limits it 
can be easily exploited. Should I switch from normal limits to other 
limits when I, say, need to test something on 4 VMs?


So while paging through documentation I found a rather old memo in 
tuning(7) about vm.swap_idle_enabled. I played a little with thresholds 
but that was only making things worse. I left swap_idle_enable on and 
let machine live. That was near January I suppose. To my amusement swap 
problems were gone. This doesn't mean swap wasn't used, instead system 
survived weeks under irregular load without issues. The only other 
change that I did was bumping up vfs.zfs.arc_free_target a little bit 
higher then default to make some space between ARC and VM so they 
wouldn't clash on memory so often.


Since then all of my problems with swap was forgotten. I'm not sure what 
setting fixed that, neither I'm sure that wasn't some recent patches. 
I'm running 11-STABLE and rebuilding system at least once per month.


Hope that can help someone. WBR.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


ZFS bootable pool detection code strictness

2017-07-31 Thread Volodymyr Kostyrko

Hi all.

First of all thank you for working on ZFS support. ZFS stability is 
unmatchable and I'm heavily relying on ZFS right now.


Last bootcode updates had given me some fun time. My pool contains some 
vdevs with skein enabled so new bootcode forced my pool out of boot. I 
know that my hands are dirty but I'm sure the pool is bootable as 
everything required for booting was never touched by unsupported options 
(I know the boot will fail instantly). Yes, I do like experimenting a lot.


From my point of view the code committed is just too strict locking out 
anyone who tries to play with extra pool properties. The analyzer itself 
is nice and I don't want it to go away as every extra bit of information 
about why boot may fail is precious but I'd be very happy to have some 
loader knob to disable the pool blacklisting so that the code will test 
the pool, will report everything it finds unsuitable but would allow a 
booting attempt.


Thanks in advance.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


sys/amd64/conf/MINIMAL - full debugger support

2017-04-20 Thread Volodymyr Kostyrko

Hi all.

The MINIMAL configuration file at STABLE-11 has full debugging support 
enabled along with:


# For full debugger support use (turn off in stable branch):

Was that intentional to leave extra debugging/witness/invariants on in 
stable for MINIMAL kernel?


Thanks in advance.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Help! two machines ran out of swap and corrupted their zpools!

2016-11-22 Thread Volodymyr Kostyrko

Pete French wrote:

zpool import -N -O readonly=on -f -R /mnt/somezpoool

If that doesn't help try:

zpool import -N -O readonly=on -f -R /mnt/somezpoool -Fn


I got someone to do this (am still having toruble finding time
as am supposed to be off sick) and it causes instant kernel panic
on trying to import the pool. Same as it does on boot.


Instapanic, huh...

Ok, let's put documentation aside and focus on unsupported development 
features.


You'll need a list of available transactions:

zdb -ul 

This one when given a vdev lists all uberblocks with their respective 
transaction ids. You can take the highest one (it's not the last one) 
and try to mount pool with:


zpool import -N -O readonly=on -f -R /mnt/somezpool -F -T 
 


Then check available filesystems. If it breaks again - retry with older 
transaction id.



--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Help! two machines ran out of swap and corrupted their zpools!

2016-11-21 Thread Volodymyr Kostyrko

Pete French wrote:

So, I am off sick and my colleagues decided to load test our set of five
servers excesively. All ran out of swap. So far so irritating, but whats has
happened is that twoof them now will not boot, as it appears the ZFS pool
they are booting from has become corrupted.

One starts to boot, then crases importing the root pool. The other doenst
even get that far with gptzfsboot saying it can't find the pool to boot from!

Now I can recover these, but I am a bit worried, that it got like this at
all, as I havent ever seen ZFS corrupt a pool like this. Anyone got any 
insights,
or suggstions as to how to stop it happening again ?

We are swapping to a separate partition, not to the pool by theway.


Good.

Try downloading live disc or mfsBSD and importing pool r/o from there.

zpool import -N -O readonly=on -f -R /mnt/somezpoool

If that doesn't help try:

zpool import -N -O readonly=on -f -R /mnt/somezpoool -Fn

Drop us a line of your configuration and used ZFS features. Like dedup, 
snapshots, external l2 logs and caches.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


zfs crash under load on 11-Prerelease r305056

2016-09-03 Thread Volodymyr Kostyrko

Hi all.

Got one host without keyboard so can't dump it.

Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg

This is MINIMAL kernel with minor additions.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: swapoff: Cannot allocate memory FreeBSD 11 Beta2

2016-07-28 Thread Volodymyr Kostyrko

Johan Hendriks wrote:

Hello all.

Lately I noticed above (error) when I reboot machine.

It looks like this.

Stopping cron.
Waiting for PIDS: 1183
swapoff: /dev/gpt/swap-9M286954: Cannot allocate memory
stopping zfsd.
Waiti..

My swap space concists of two GPT swap partitions on the zfs mirror OS
disks, both 4GB each.
The machine has 4 GB mem.

This does not happen after normal use, but if i wait a day, do a
buildworld then the swapoff error shows.

content off /etc/fstab

/dev/gpt/swap-Z3TX7DTA   none   swapsw  0   0
/dev/gpt/swap-9M286954   none   swapsw  0   0


I think you are bitten by a bad swapoff logic. I made patch for it eons ego:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187081

From my point of view swapping off from non-late swap devices is just a 
waste of time.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Rescuing a GPT ZFS boot setup

2013-09-20 Thread Volodymyr Kostyrko

20.09.2013 10:41, Andy Moran wrote:

WIth the 10-ALPHA2 LiveCD, I get:

gpart: attrib 'active': Device not configured



GPT partitions don't have active attribute. You should omit -i argument.
Just run `gpart unset -a active ada0`.

--
WBR, Andrey V. Elsukov

--
WBR, Andrey V. Elsukov



That ran without errors.. but sadly did not solve my problem of the UEFI not 
recognizing it as a bootable disk. I think the problem is my particular 
UEFI doesn't recognize GPT drives that don't have an EFI partition on them.

So I gave up.  My server has been down for too long.   I took half the zfs 
mirror, created it with a MBR partition and installed FreeBSD 9.2 on it, and my 
UEFI can boot it in legacy mode.   From there I can mount the other half of the 
mirror and copy files off.   A painful process but at least I have a way 
forward.


Please, name your poison on list so that successors can google it in 
case someone wants to by the same piece of hardware.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Rescuing a GPT ZFS boot setup

2013-09-19 Thread Volodymyr Kostyrko

19.09.2013 09:36, Andrew Moran wrote:

3 years ago I followed https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror  
for a FreeBSD 8.1 system (which has since been upgraded to 9.1).A couple 
days ago I had massive hardware failure, and wound up having to put the two 
drives into an entirely new PC system.

Unfortunately I'm not able to get it to boot off the hard drives.  It doesn't even show the FreeBSD 
bootloader menu it normally would.  The BIOS sees both drives and it can boot off the 9.1 install/Live CD 
without any problems.   In the LiveCD, I can see both drives partition tables (gpart show ..) and 
I can import  the zpool (zpool import zroot), and see all my data.   I just can't seem to boot 
from it.   I tried rerunning the gpart bootcode commands on both drives (no errors), but no 
effect.

It's also not beyond the realm of possibility I have some BIOS setting wrong, 
but the drives do show up in the POST and BIOS setting.

Does anyone know how I can make my drives bootable again?


Maybe the machine is just too picky about partitioning scheme? Try this 
black magic:


printf '\ny\n\n\n\ny\n\ny\n\n\n\n\ny\n' | fdisk -u ${YourDiskName}

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Rescuing a GPT ZFS boot setup

2013-09-19 Thread Volodymyr Kostyrko

19.09.2013 16:43, Andrew Moran wrote:

Alas, that did not work. But it does look to be BIOS related.

I think this new system has a UEFI bios.

I just read from https://wiki.freebsd.org/UEFI:
* Partitions not seen. When using GPT, FreeBSD will create a protective 
MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks 
this partition active. This causes at least some UEFI implementations to ignore 
the GPT. To fix this the partition needs to be marked inactive.
* Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create 
filesystems that the UEFI code can't properly read. If the filesystem is small 
enough, use FAT16 or FAT12 instead.

I think this may be my issue.  But 9.1 LiveCD does boot and I can see the data 
once booted, so there must be a way to fix the boot loader on the drive to work.


Good catch. The fix landed in stable not so long ago 
(http://svnweb.freebsd.org/base?view=revisionrevision=255017) so you 
wouldn't find it in 9.2 either. Can you try this:


gpart unset -a active ada0

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


LOR's in 9.2-RC4, anyone?

2013-09-14 Thread Volodymyr Kostyrko

Hello.

That's from one of my machines running RC4:

Sep 14 11:19:36 slylandro kernel: lock order reversal:
Sep 14 11:19:36 slylandro kernel: 1st 0xfe002e41b878 tmpfs (tmpfs) @ 
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1907
Sep 14 11:19:36 slylandro kernel: 2nd 0xfe019b06c680 zfs (zfs) @ 
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1938

Sep 14 11:19:36 slylandro kernel: KDB: stack backtrace:
Sep 14 11:19:36 slylandro kernel: db_trace_self_wrapper() at 
db_trace_self_wrapper+0x2b/frame 0xff9f8492d2d0
Sep 14 11:19:36 slylandro kernel: kdb_backtrace() at 
kdb_backtrace+0x39/frame 0xff9f8492d380
Sep 14 11:19:36 slylandro kernel: witness_checkorder() at 
witness_checkorder+0xc0a/frame 0xff9f8492d400
Sep 14 11:19:36 slylandro kernel: __lockmgr_args() at 
__lockmgr_args+0x744/frame 0xff9f8492d520
Sep 14 11:19:36 slylandro kernel: vop_stdlock() at 
vop_stdlock+0x3c/frame 0xff9f8492d540
Sep 14 11:19:36 slylandro kernel: VOP_LOCK1_APV() at 
VOP_LOCK1_APV+0xbe/frame 0xff9f8492d570
Sep 14 11:19:36 slylandro kernel: unionfs_lock() at 
unionfs_lock+0x4c6/frame 0xff9f8492d600
Sep 14 11:19:36 slylandro kernel: VOP_LOCK1_APV() at 
VOP_LOCK1_APV+0xbe/frame 0xff9f8492d630
Sep 14 11:19:36 slylandro kernel: _vn_lock() at _vn_lock+0x54/frame 
0xff9f8492d690
Sep 14 11:19:36 slylandro kernel: unionfs_root() at 
unionfs_root+0x43/frame 0xff9f8492d6c0
Sep 14 11:19:36 slylandro kernel: lookup() at lookup+0x99d/frame 
0xff9f8492d750
Sep 14 11:19:36 slylandro kernel: namei() at namei+0x589/frame 
0xff9f8492d800
Sep 14 11:19:36 slylandro kernel: unp_connect() at 
unp_connect+0x1b3/frame 0xff9f8492da60
Sep 14 11:19:36 slylandro kernel: uipc_connect() at 
uipc_connect+0x47/frame 0xff9f8492da90
Sep 14 11:19:36 slylandro kernel: kern_connect() at 
kern_connect+0xdb/frame 0xff9f8492dae0
Sep 14 11:19:36 slylandro kernel: sys_connect() at 
sys_connect+0x96/frame 0xff9f8492db20
Sep 14 11:19:36 slylandro kernel: amd64_syscall() at 
amd64_syscall+0x259/frame 0xff9f8492dc30
Sep 14 11:19:36 slylandro kernel: Xfast_syscall() at 
Xfast_syscall+0xfb/frame 0xff9f8492dc30
Sep 14 11:19:36 slylandro kernel: --- syscall (98, FreeBSD ELF64, 
sys_connect), rip = 0x801f4d8ac, rsp = 0x7fff6c18, rbp = 
0x7fff6c40 ---


Sep 14 11:19:39 slylandro kernel: lock order reversal:
Sep 14 11:19:39 slylandro kernel: 1st 0xfe0089d87878 zfs (zfs) @ 
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:312
Sep 14 11:19:39 slylandro kernel: 2nd 0xfe0280cc9680 unionfs 
(unionfs) @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_subr.c:366
Sep 14 11:19:39 slylandro kernel: 3rd 0xfe002e3ec098 zfs (zfs) @ 
/usr/src/sys/kern/vfs_subr.c:2335

Sep 14 11:19:39 slylandro kernel: KDB: stack backtrace:
Sep 14 11:19:39 slylandro kernel: db_trace_self_wrapper() at 
db_trace_self_wrapper+0x2b/frame 0xff9f835fe120
Sep 14 11:19:39 slylandro kernel: kdb_backtrace() at 
kdb_backtrace+0x39/frame 0xff9f835fe1d0
Sep 14 11:19:39 slylandro kernel: witness_checkorder() at 
witness_checkorder+0xc0a/frame 0xff9f835fe250
Sep 14 11:19:39 slylandro kernel: __lockmgr_args() at 
__lockmgr_args+0x744/frame 0xff9f835fe370
Sep 14 11:19:39 slylandro kernel: vop_stdlock() at 
vop_stdlock+0x3c/frame 0xff9f835fe390
Sep 14 11:19:39 slylandro kernel: VOP_LOCK1_APV() at 
VOP_LOCK1_APV+0xbe/frame 0xff9f835fe3c0
Sep 14 11:19:39 slylandro kernel: _vn_lock() at _vn_lock+0x54/frame 
0xff9f835fe420
Sep 14 11:19:39 slylandro kernel: vputx() at vputx+0x21b/frame 
0xff9f835fe480
Sep 14 11:19:39 slylandro kernel: unionfs_noderem() at 
unionfs_noderem+0x1cf/frame 0xff9f835fe4f0
Sep 14 11:19:39 slylandro kernel: unionfs_reclaim() at 
unionfs_reclaim+0x14/frame 0xff9f835fe500
Sep 14 11:19:39 slylandro kernel: VOP_RECLAIM_APV() at 
VOP_RECLAIM_APV+0xb9/frame 0xff9f835fe530
Sep 14 11:19:39 slylandro kernel: vgonel() at vgonel+0x16e/frame 
0xff9f835fe5a0
Sep 14 11:19:39 slylandro kernel: vrecycle() at vrecycle+0x3e/frame 
0xff9f835fe5d0
Sep 14 11:19:39 slylandro kernel: unionfs_inactive() at 
unionfs_inactive+0x23/frame 0xff9f835fe5e0
Sep 14 11:19:39 slylandro kernel: VOP_INACTIVE_APV() at 
VOP_INACTIVE_APV+0xb9/frame 0xff9f835fe610
Sep 14 11:19:39 slylandro kernel: vinactive() at vinactive+0xc6/frame 
0xff9f835fe660
Sep 14 11:19:39 slylandro kernel: vputx() at vputx+0x263/frame 
0xff9f835fe6c0
Sep 14 11:19:39 slylandro kernel: lookup() at lookup+0xd2c/frame 
0xff9f835fe750
Sep 14 11:19:39 slylandro kernel: namei() at namei+0x589/frame 
0xff9f835fe800
Sep 14 11:19:39 slylandro kernel: unp_connect() at 
unp_connect+0x1b3/frame 0xff9f835fea60
Sep 14 11:19:39 slylandro kernel: uipc_connect() at 
uipc_connect+0x47/frame 0xff9f835fea90
Sep 14 11:19:39 slylandro kernel: kern_connect() at 
kern_connect+0xdb/frame 0xff9f835feae0
Sep 14 11:19:39 slylandro kernel: sys_connect() at 
sys_connect+0x96/frame 

Re: Possible kqueue related issue on STABLE/RC.

2013-09-11 Thread Volodymyr Kostyrko

11.09.2013 18:07, Jimmy Olgeni wrote:


Perhaps I found something weird while running 9.2-RC3 FreeBSD
9.2-RC3 #0 r255393 (ZFS-only setup).



Unfortunately I'm not able to get a minidump for the latest RC, but at this
point I suspect that something is going on with glib20 and kqueue on both
-STABLE and -RC.


Can you spare some more info on this?

1. What is your /etc/src.conf and /etc/make.conf files?
2. Does your copy of sources has some third-party patches applied?
3. Does this happens on more than one PC i.e. are you sure hardware is 
not involved?


Can you try to build world WITH_CLANG_IS_CC? Clang generated code is 
known to produce an instant coredump in situations where gcc generated 
code hits a loop or becomes unresponsive.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: can't build ^/releng/9.2 from ^/releng/9.1 (resolved)

2013-08-29 Thread Volodymyr Kostyrko

27.08.2013 21:03, Volodymyr Kostyrko wrote):

Was my local glitch, defining INSTALL=install -C in /etc/make.conf 
shadows install.sh


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: can't build ^/releng/9.2 from ^/releng/9.1 (resolved)

2013-08-29 Thread Volodymyr Kostyrko

29.08.2013 18:25, ill...@gmail.com wrote:

On 29 August 2013 07:44, Volodymyr Kostyrko c.kw...@gmail.com wrote:

27.08.2013 21:03, Volodymyr Kostyrko wrote):

Was my local glitch, defining INSTALL=install -C in /etc/make.conf shadows
install.sh


This is good to know, as bits of my /etc/make.conf
date back to 7.0.


Yeah, mine from 4.0 or so...


It looks like the syntax now (via make.conf(5)) is
INSTALL+= -C


Actually as I am a ZFS citizen I don't need this anymore as ZFS can 
simply ignore writes when SHA256 checksum matches.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


can't build ^/releng/9.2 from ^/releng/9.1

2013-08-27 Thread Volodymyr Kostyrko

Hi all.

Just tried building 9.2 on one of my servers:

=== usr.bin/makewhatis (obj,depend,all,install)
install -C -s -o root -g wheel -m 555   makewhatis 
/usr/obj/usr/src/tmp/legacy/usr/bin/makewhatis
install -C -o root  -g wheel -m 555 
/usr/src/usr.bin/makewhatis/makewhatis.local.sh 
/usr/obj/usr/src/tmp/legacy/usr/libexec/makewhatis.local
/usr/obj/usr/src/tmp/legacy/usr/libexec/catman.local - 
/usr/obj/usr/src/tmp/legacy/usr/libexec/makewhatis.local

install: illegal option -- l
usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 file2
   install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 ... fileN directory
   install -d [-v] [-g group] [-m mode] [-o owner] directory ...
*** [_installlinks] Error code 64
1 error
*** [bootstrap-tools] Error code 2
1 error
*** [_bootstrap-tools] Error code 2
1 error
*** [buildworld] Error code 2
1 error

I know I can build and install `install` by hand but this impales 
updating process a bit...


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ZFS: can't read MOS of pool

2013-08-02 Thread Volodymyr Kostyrko

22.07.2013 19:18, Łukasz Wąsikowski wrote:

I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm
getting:

ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS of pool klawisz
gptzfsboot: failed to mount default pool klawisz

Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM,
400 GB of local storage with SCSI Controller type: Default (lsi).

I'm not sure what I did to make this VM unbootable. I've installed
9.2-PRERELEASE, did source based upgrade to r253470, mergemaster,
reinstalled bootcode and rebooted. To this point VM was bootable.

Then I did installworld from /usr/src to ezjail's basejail (ezjail-admin
update -i), did mergemaster for jails, install some ports - none of this
should mess with booting. I rebooted VM and got unbootable system.

When I boot from liveCD I can import this pool (scrub shows no errors),
mount it, chroot to it, and work with it. I just can't get it to boot.

Some information about the system:
http://pastie.org/private/mtfhkx0wx0vve29xn0plw

I've tried to downgrade to r252316 - no luck, system is still unbootable.

Any hints how to go from here?


First, how did you update bootcode? `ls -la /boot` also wood help.

Second, what is your /etc/make.conf and /etc/src.conf?

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS: can't read MOS of pool

2013-08-02 Thread Volodymyr Kostyrko

02.08.2013 17:40, Łukasz Wąsikowski wrote:

Any hints how to go from here?


First, how did you update bootcode? `ls -la /boot` also wood help.

Second, what is your /etc/make.conf and /etc/src.conf?


I'm updating bootcode with:

gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0

/etc/src.conf doesn't exist (I'm using GENERIC kernel on this VM)
/etc/make.conf - http://pastebin.com/QapEWzfJ



Looks good.

Can you also try what Trond suggests about boot order? You can also list 
your boot fs in /boot/loader.conf like 
vfs.root.mountfrom=zfs:klawisz/ROOTFS. Or you can just add this at 
loader prompt.


There's also a ${SRC}/tools/tools/zfsboottest script that can tell you 
something about booting from your pool.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ZFS: can't read MOS of pool

2013-08-02 Thread Volodymyr Kostyrko

02.08.2013 17:56, Łukasz Wąsikowski wrote:

Can you also try what Trond suggests about boot order? You can also list
your boot fs in /boot/loader.conf like


I listed ROOTFS in /boot/loader.conf, didn't helped. I'm using this boot
order on 20+ boxes and never had any issues with it, but I'll check it
as I don't have better idea what to do next.


I'm almost out of suggestions...

1. Can you try to removing 'canmount' property from klawisz fs and 
'bootfs' property from pool?


2. Can you try fetching late nexenta or illumos and give your pool a 
full scrub?


3. Can you try disablng/enabling features? I assume you haven't used 
compression and have no snapshots.



vfs.root.mountfrom=zfs:klawisz/ROOTFS. Or you can just add this at
loader prompt.

There's also a ${SRC}/tools/tools/zfsboottest script that can tell you
something about booting from your pool.


This tools doesn't compile on 9.2-BETA2 r253884

# cd /usr/src/tools/tools/zfsboottest/  make

Warning: Object directory not changed from original
/usr/src/tools/tools/zfsboottest
ln -sf /usr/src/tools/tools/zfsboottest/../../../sys/i386/include machine
cc -O1  -I/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs
-I/usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs  -I.
-fdiagnostics-show-option  -W -Wextra -Wno-sign-compare
-Wno-unused-parameter  -Werror -std=gnu99 -fstack-protector  -c
zfsboottest.c
cc1: warnings being treated as errors
In file included from
/usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/zfssubr.c:122,
  from
/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:38,
  from zfsboottest.c:55:
/usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/lz4.c: In
function 'lz4_decompress':
/usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/lz4.c:45:
warning: implicit declaration of function 'htonl'
In file included from zfsboottest.c:55:
/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c: In
function 'spa_status':
/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
error: 'ZFS_MAXNAMELEN' undeclared (first use in this function)
/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
error: (Each undeclared identifier is reported only once
/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
error: for each function it appears in.)
*** [zfsboottest.o] Error code 1

Stop in /usr/src/tools/tools/zfsboottest.


Ahem, sorry. Never used that.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: 9.2PRERELEASE ZFS panic in lzjb_compress

2013-07-19 Thread Volodymyr Kostyrko

19.07.2013 07:04, olivier wrote:

Hi,
Running 9.2-PRERELEASE #19 r253313 I got the following panic

Fatal trap 12: page fault while in kernel mode
cpuid = 22; apic id = 46
fault virtual address   = 0xff827ebca30c
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x81983055
stack pointer   = 0x28:0xffcf75bd60a0
frame pointer   = 0x28:0xffcf75bd68f0
code segment= base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (zio_write_issue_hig)
trap number = 12
panic: page fault
cpuid = 22
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame
0xffcf75bd5b30
kdb_backtrace() at kdb_backtrace+0x37/frame 0xffcf75bd5bf0
panic() at panic+0x1ce/frame 0xffcf75bd5cf0
trap_fatal() at trap_fatal+0x290/frame 0xffcf75bd5d50
trap_pfault() at trap_pfault+0x211/frame 0xffcf75bd5de0
trap() at trap+0x344/frame 0xffcf75bd5fe0
calltrap() at calltrap+0x8/frame 0xffcf75bd5fe0
--- trap 0xc, rip = 0x81983055, rsp = 0xffcf75bd60a0, rbp =
0xffcf75bd68f0 ---
lzjb_compress() at lzjb_compress+0x185/frame 0xffcf75bd68f0
zio_compress_data() at zio_compress_data+0x92/frame 0xffcf75bd6920
zio_write_bp_init() at zio_write_bp_init+0x24b/frame 0xffcf75bd6970
zio_execute() at zio_execute+0xc3/frame 0xffcf75bd69b0
taskqueue_run_locked() at taskqueue_run_locked+0x74/frame 0xffcf75bd6a00
taskqueue_thread_loop() at taskqueue_thread_loop+0x46/frame
0xffcf75bd6a20
fork_exit() at fork_exit+0x11f/frame 0xffcf75bd6a70
fork_trampoline() at fork_trampoline+0xe/frame 0xffcf75bd6a70
--- trap 0, rip = 0, rsp = 0xffcf75bd6b30, rbp = 0 ---

lzjb_compress+0x185 corresponds to line 85 in
80 cpy = src - offset;
81 if (cpy = (uchar_t *)s_start  cpy != src 
82src[0] == cpy[0]  src[1] == cpy[1]  src[2] == cpy[2]) {
83 *copymap |= copymask;
84 for (mlen = MATCH_MIN; mlen  MATCH_MAX; mlen++)
85 if (src[mlen] != cpy[mlen])
86 break;
87 *dst++ = ((mlen - MATCH_MIN)  (NBBY - MATCH_BITS)) |
88(offset  NBBY);
89 *dst++ = (uchar_t)offset;

I think it's the first time I've seen this panic. It happened while doing a
send/receive. I have two pools with lzjb compression; I don't know which of
these pools caused the problem, but one of them was the source of the
send/receive.

I only have a textdump but I'm happy to try to provide more information
that could help anyone look into this.
Thanks
Olivier


Oh, I can add to this one. I have a full core dump of the same problem 
caused by copying large set of files from lzjb compressed pool to lz4 
compressed pool. vfs.zfs.recover was set.


#1  0x8039d954 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
#2  0x8039ddce in panic (fmt=value optimized out)
at /usr/src/sys/kern/kern_shutdown.c:637
#3  0x80620a6a in trap_fatal (frame=value optimized out,
eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:879
#4  0x80620d25 in trap_pfault (frame=0x0, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:700
#5  0x806204f6 in trap (frame=0xff821ca43600)
at /usr/src/sys/amd64/amd64/trap.c:463
#6  0x8060a032 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:232
#7  0x805a9367 in vm_page_alloc (object=0x80a34030,
pindex=16633, req=97) at /usr/src/sys/vm/vm_page.c:1445
#8  0x8059c42e in kmem_back (map=0xfe0001e8,
addr=18446743524021862400, size=16384, flags=value optimized out)
at /usr/src/sys/vm/vm_kern.c:362
#9  0x8059c2ac in kmem_malloc (map=0xfe0001e8, size=16384,
flags=257) at /usr/src/sys/vm/vm_kern.c:313
#10 0x80595104 in uma_large_malloc (size=value optimized out,
wait=257) at /usr/src/sys/vm/uma_core.c:994
#11 0x80386b80 in malloc (size=16384, mtp=0x80ea7c40, 
flags=0)

at /usr/src/sys/kern/kern_malloc.c:492
#12 0x80c9e13c in lz4_compress (s_start=0xff80d0b19000,
d_start=0xff8159445000, s_len=131072, d_len=114688, n=-2)
at 
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/lz4.c:843

#13 0x80cdde25 in zio_compress_data (c=value optimized out,
src=value optimized out, dst=0xff8159445000, s_len=131072)
at 
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c:109

#14 0x80cda012 in zio_write_bp_init (zio=0xfe0143a12000)
at 
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1107

#15 0x80cd8ec6 in zio_execute (zio=0xfe0143a12000)
at 
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1305

#16 0x803e25e6 in taskqueue_run_locked (queue=0xfe00060ca300)
at /usr/src/sys/kern/subr_taskqueue.c:312

Re: [resolved] stable/9 fails to compile: kmem_alloc_contig bad definition - radeon kms patches

2013-07-12 Thread Volodymyr Kostyrko

12.07.2013 08:51, Volodymyr Kostyrko wrote:


vm_extern.h:
vm_offset_t kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags,
 vm_paddr_t low, vm_paddr_t high, unsigned long alignment,
 unsigned long boundary, vm_memattr_t memattr);

Why boundary is unsigned long and not vm_paddr_t?

vm_contig.c:
vm_offset_t
kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags, vm_paddr_t low,
  vm_paddr_t high, u_long alignment, vm_paddr_t boundary,
  vm_memattr_t memattr)



That was caused by radeon drm patches found at 
https://wiki.freebsd.org/AMD_GPU


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


stable/9 fails to compile: kmem_alloc_contig bad definition

2013-07-11 Thread Volodymyr Kostyrko

Hello.

/usr/local/libexec/ccache/world/cc -c -O -pipe -march=native -std=c99 -g 
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef 
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option  -Wno-error-tautological-compare 
-Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I. 
-I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -mno-aes -mno-avx 
-mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector 
/usr/src/sys/vm/vm_contig.c
/usr/src/sys/vm/vm_contig.c:319:1: error: conflicting types for 
'kmem_alloc_contig'

kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags, vm_paddr_t low,
^
/usr/src/sys/vm/vm_extern.h:46:13: note: previous declaration is here
vm_offset_t kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags,
^
1 error generated.

vm_extern.h:
vm_offset_t kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags,
vm_paddr_t low, vm_paddr_t high, unsigned long alignment,
unsigned long boundary, vm_memattr_t memattr);

Why boundary is unsigned long and not vm_paddr_t?

vm_contig.c:
vm_offset_t
kmem_alloc_contig(vm_map_t map, vm_size_t size, int flags, vm_paddr_t low,
 vm_paddr_t high, u_long alignment, vm_paddr_t boundary,
 vm_memattr_t memattr)

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


can't build stable with clang after tcpdump import

2013-06-27 Thread Volodymyr Kostyrko

Hi all.

After recent tcpdump update I get this:

cc -O2 -pipe -I/usr/src/usr.sbin/tcpdump/tcpdump 
-I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump 
-DHAVE_CONFIG_H -D_U_=__attribute__((unused)) -DINET6 -DLBL_ALIGN 
-I/usr/obj/usr/src/tmp/usr/include/openssl -DHAVE_LIBCRYPTO 
-DHAVE_OPENSSL_EVP_H -DHAVE_NET_PFVAR_H -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body 
-Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value 
-Wno-parentheses-equality -Wno-unused-function -Wno-conversion -c 
/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-radius.c
/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-pfsync.c:330:23: 
error: use of undeclared identifier 'tcpstates'

printf(   %s:%s, tcpstates[src-state],
   ^

make buildincludes ; make installincludes doesn't fix a thing...

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Help! :( ZFS panic on boot, importing pool after server crash.

2013-06-14 Thread Volodymyr Kostyrko

14.06.2013 12:55, Dr Josef Karthauser:

Hi, I'm a bit at the end of my tether.

We had a ZFS panic last night on a machine that hosts all my mail and web; it 
was rebooted and it now panics mounting the ZFS root filesystem.

The call stack info is:

solaris assert: ss == NULL, file: 
/usr/src/sys/modules/zfs/../../cddl/contrib/opensource/uts/common/fs/zfs/space_map.c,
 line: 109

kdb_backtrace
panic
space_map_add
space_map_load
metaslab_activate
metaslab_allocate
zio_dva_allocate
zio_execute
taskqueue_run_locked
taskqueue_thread_loop
fork_exit
fork_trampoline

I can boot from the live DVD filesystem, but I can only mount the pool 
read-only without getting the same kernel panic.  This is with FreeBSD 9.0.

The machine is remote, and I don't have access other than through a DRAC 
console port (so I can't cut and paste; sorry for the poor stack trace).

Is anyone here in the position to advice me how I might process to get this 
machine mounting and running again in multi-user mode?


There's no official way.


p.s. the config, btw, is a ZFS mirror on two ad devices. It's got a ZFS root 
file system.


If you are fairly sure about your devices you can:

1. Remove second disk from pool or create another pool on top of it.

2. Recreate all FS structure on the second disk. You can dump al your FS 
with something like:


zfs list -Ho name | xargs -n1 zfs get -H all | awk 
'BEGIN{shard=;output=}{if(shard!=$1  shard!=){output=zfs 
create;for(param in params)output=output -o param=params[param];print
output shard;delete 
params;shard=}}$4~/local/{params[$2]=$3;shard=$1;next}$2~/type/{shard=$1}END{output=zfs 
create;for(param in params)output=output -o 
param=params[param];print output shard;}'


Be sure to rename the pool and change the first line.

3. Rsync all data to the second disk.

4. Try to boot from the second disk.

If everything worked you are free to attach first disk to second one to 
create a mirror again.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Help! :( ZFS panic on boot, importing pool after server crash.

2013-06-14 Thread Volodymyr Kostyrko

14.06.2013 15:51, Dr Josef Karthauser:

On 14 Jun 2013, at 12:00, Volodymyr Kostyrko c.kw...@gmail.com wrote:


14.06.2013 12:55, Dr Josef Karthauser:

Hi, I'm a bit at the end of my tether.



p.s. the config, btw, is a ZFS mirror on two ad devices. It's got a ZFS root 
file system.


If you are fairly sure about your devices you can:

1. Remove second disk from pool or create another pool on top of it.

2. Recreate all FS structure on the second disk. You can dump al your FS with 
something like:



Great. Thanks for that.

Have you got a hint as to how I can get access to the root file system? It's 
currently set to have a legacy mount point.  Which means that when I import the 
pool:

# zfs import -o readonly=on -o altroot=/tmp/zfs -f poolname

the root filesystem is missing.  Then if I try and set the mount point:

#zfs set mountpoint=/tmp/zfs2 poolname

it just sits there; probably because the command is blocking on the R/O pool, 
or something.

How do I temporarily remount the root filesystem so that I can get access to 
the files?


mount -t zfs pool-name mountpoint

Personally when I need to work with such pools I first import the pool 
with -N (nomount) option, then I mount root fs by hand and after that 
goes `zfs mount -a` which handles everything else.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Musings on ZFS Backup strategies

2013-03-04 Thread Volodymyr Kostyrko

02.03.2013 03:12, David Magda:


On Mar 1, 2013, at 12:55, Volodymyr Kostyrko wrote:


Yes, I'm working with backups the same way, I wrote a simple script that 
synchronizes two filesystems between distant servers. I also use the same 
script to synchronize bushy filesystems (with hundred thousands of files) where 
rsync produces a too big load for synchronizing.

https://github.com/kworr/zfSnap/commit/08d8b499dbc2527a652cddbc601c7ee8c0c23301


There are quite a few scripts out there:

http://www.freshports.org/search.php?query=zfs


A lot of them require python or ruby, and none of them manages 
synchronizing snapshots over network.



For file level copying, where you don't want to walk the entire tree, here is the 
zfs diff command:


zfs diff [-FHt] snapshot [snapshot|filesystem]

 Describes differences between a snapshot and a successor dataset. The
 successor dataset can be a later snapshot or the current filesystem.

 The changed files are displayed including the change type. The change
 type is displayed useing a single character. If a file or directory
 was renamed, the old and the new names are displayed.


http://www.freebsd.org/cgi/man.cgi?query=zfs

This allows one to get a quick list of files and directories, then use 
tar/rsync/cp/etc. to do the actual copy (where the destination does not have to 
be ZFS: e.g., NFS, ext4, Lustre, HDFS, etc.).


I know that but I see no reason in reverting to file-based synch if I 
can do block-based.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Musings on ZFS Backup strategies

2013-03-04 Thread Volodymyr Kostyrko

04.03.2013 19:04, David Magda:

On Mon, March 4, 2013 11:07, Volodymyr Kostyrko wrote:

02.03.2013 03:12, David Magda:

There are quite a few scripts out there:

http://www.freshports.org/search.php?query=zfs


A lot of them require python or ruby, and none of them manages
synchronizing snapshots over network.


Yes, but I think it is worth considering the creation of snapshots, and
the transfer of snapshots, as two separate steps. By treating them
independently (perhaps in two different scripts), it helps prevent the
breakage in one from affecting the other.


Exactly. My script is just an addition to zfSnap or any other tool that 
manages snapshots. Currently it does nothing more then comparing list of 
available snapshots and network transfer.



Snapshots are not backups (IMHO), but they are handy for users and
sysadmins for the simple situations of accidentally files. If your network
access / copying breaks or is slow for some reason, at least you have
simply copies locally. Similarly if you're having issues with the machine
that keeps your remove pool.


Yes, I addressed such thing specifically adding availability to restart 
transfer from any point or just even don't care - once initialized the 
process is autonomous and in case of failure anything would be rolled 
back to last known good snapshot. I also added possibility to 
compress/limit traffic.



By keeping the snapshots going separately, once any problems with the
network or remote server are solved, you can use them to incrementally
sync up the remote pool. You can simply run the remote-sync scripts more
often to do the catch up.

It's just an idea, and everyone has different needs. I often find it handy
to keep different steps in different scripts that are loosely coupled.


I just tried to give another use for snapshots. Or least the way to 
simplify things in one specific situation.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Musings on ZFS Backup strategies

2013-03-01 Thread Volodymyr Kostyrko

01.03.2013 16:24, Karl Denninger:

Dabbling with ZFS now, and giving some thought to how to handle backup
strategies.

ZFS' snapshot capabilities have forced me to re-think the way that I've
handled this.  Previously near-line (and offline) backup was focused on
being able to handle both disasters (e.g. RAID adapter goes nuts and
scribbles on the entire contents of the array), a double-disk (or worse)
failure, or the obvious (e.g. fire, etc) along with the aw crap, I just
rm -rf'd something I'd rather not!

ZFS makes snapshots very cheap, which means you can resolve the aw
crap situation without resorting to backups at all.  This turns the
backup situation into a disaster recovery one.

And that in turn seems to say that the ideal strategy looks more like:

Take a base snapshot immediately and zfs send it to offline storage.
Take an incremental at some interval (appropriate for disaster recovery)
and zfs send THAT to stable storage.

If I then restore the base and snapshot, I get back to where I was when
the latest snapshot was taken.  I don't need to keep the incremental
snapshot for longer than it takes to zfs send it, so I can do:

zfs snapshot pool/some-filesystem@unique-label
zfs send -i pool/some-filesystem@base pool/some-filesystem@unique-label
zfs destroy pool/some-filesystem@unique-label

and that seems to work (and restore) just fine.


Yes, I'm working with backups the same way, I wrote a simple script that 
synchronizes two filesystems between distant servers. I also use the 
same script to synchronize bushy filesystems (with hundred thousands of 
files) where rsync produces a too big load for synchronizing.


https://github.com/kworr/zfSnap/commit/08d8b499dbc2527a652cddbc601c7ee8c0c23301

I left it where it was but I was also planning to write some purger for 
snapshots that would automatically purge snapshots when pool gets low on 
space. Never hit that yet.



Am I looking at this the right way here?  Provided that the base backup
and incremental are both readable, it appears that I have the disaster
case covered, and the online snapshot increments and retention are
easily adjusted and cover the oops situations without having to resort
to the backups at all.

This in turn means that keeping more than two incremental dumps offline
has little or no value; the second merely being taken to insure that
there is always at least one that has been written to completion without
error to apply on top of the base.  That in turn makes the backup
storage requirement based only on entropy in the filesystem and not time
(where the tower of Hanoi style dump hierarchy imposed both a time AND
entropy cost on backup media.)


Well, snapshots can pose a value in a longer timeframe depending on 
data. Being able to restore some file accidentally deleted two month ago 
already saved 2k$ for one of our customers.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: zfs v28 solaris compatibility

2013-02-07 Thread Volodymyr Kostyrko

07.02.2013 14:16, Eugene M. Zheganin:

Hi.

Is the FreeBSD v28 zfs fully compatible with solaris zfs ? I need to
switch disks between servers, these disks are SAN disks, and it's about
20T of data. I don't want to lose them. I am aware that our zfs is
compatible with Solaris, but I just want to be sure, like really really
sure. Of course I can switch back at any moment, but only if the data
won't become corrupted.


I think one simple way to test that is to create a replication stream 
for some filesystem with `zfs send` on first machine and check whether 
this stream is received correctly on the second machine.


I'm mostly sure that you wouldn't lose your data, however Solaris is 
staying with ZFS v28 since the last release and FreeBSD is progressing 
slowly with Illumos. I'm pretty sure that 9-STABLE is already using ZFS 
feats and any pool created with current STABLE would not become writable 
for Solaris.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Ports and WITH_LIBCPLUSPLUS

2013-02-05 Thread Volodymyr Kostyrko

05.02.2013 13:59, Andreas Nilsson:


Thanks for trying this out.  Is there also a list of ports that *do*
compile (and hopefully run) successfully? :-)


I already switched to libc++ on my unstable STABLE-9 machines.
Currently I'm using this config:

*: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++

audio/flac databases/db5 devel/binutils devel/doxygen
devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm
graphics/libopenraw graphics/tesseract lang/gcc
multimedia/phonon-gstreamer net-p2p/transmission-cli
net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell
www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS

databases/mariadb-client emulators/pearpc www/libxul
x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS

www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS

snip



Could you clarify where you have these settings?


This is my desktops that I use @home and @work. I'm not going that 
experimental on any production machine.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Ports and WITH_LIBCPLUSPLUS

2013-02-05 Thread Volodymyr Kostyrko

05.02.2013 15:06, Andreas Nilsson:

Ah, sorry for being unclear. I meant which config files :)


I'm using ports-mgmt/portconf to keep track of all knobs.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Ports and WITH_LIBCPLUSPLUS

2013-02-04 Thread Volodymyr Kostyrko

03.02.2013 15:28, Dimitry Andric:

Thanks for trying this out.  Is there also a list of ports that *do*
compile (and hopefully run) successfully? :-)


I already switched to libc++ on my unstable STABLE-9 machines. Currently 
I'm using this config:


*: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++

audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer 
devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw 
graphics/tesseract lang/gcc multimedia/phonon-gstreamer 
net-p2p/transmission-cli net-p2p/transmission-daemon 
sysutils/smartmontools textproc/hunspell www/qt4-webkit 
x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS


databases/mariadb-client emulators/pearpc www/libxul 
x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS


www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS

Currently I have working seamonkey and slim built this way.

 ldd `which seamonkey`
/usr/local/bin/seamonkey:
libm.so.5 = /lib/libm.so.5 (0x800846000)
libcxxrt.so.1 = /lib/libcxxrt.so.1 (0x800a65000)
libc++.so.1 = /usr/lib/libc++.so.1 (0x800c7e000)
libthr.so.3 = /lib/libthr.so.3 (0x800f34000)
libc.so.7 = /lib/libc.so.7 (0x801156000)
libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x8014a5000)

I can post whole list of packages if anyone is interested. Everything 
looks even better then when clang was introduced to ports - almost any 
package works, the ones that doesn't just have a complicated 
build/install process. No painful glitches yet.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: xorg-server patch error

2013-02-01 Thread Volodymyr Kostyrko

01.02.2013 10:07, Andriy Kornatskyy:


# make install clean -sC /usr/ports/x11/xorg-minimal

=== Installing for xorg-minimal-7.5.2
=== xorg-minimal-7.5.2 depends on file: /usr/local/bin/Xorg - not found
=== Verifying install for /usr/local/bin/Xorg in 
/usr/ports/x11-servers/xorg-server
=== Patching for xorg-server-1.10.6_2,1
=== xorg-server-1.10.6_2,1 depends on file: /usr/local/bin/perl5.14.2 - found
=== Applying extra patch 
/usr/ports/x11-servers/xorg-server/files/extra-hw_dmx_glxProxy_compsize.h
=== Applying extra patch 
/usr/ports/x11-servers/xorg-server/files/extra-hw_dmx_glxProxy_glxcmds.h
=== Applying extra patch /usr/ports/x11-servers/xorg-server/files/extra-clang
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to hw/xfree86/common/xf86Xinput.c.rej
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to hw/xfree86/parser/InputClass.c.rej
Ignoring previously applied (or reversed) patch.
3 out of 3 hunks ignored--saving rejects to hw/xfree86/dri2/dri2.c.rej
*** [do-patch] Error code 5


Just a wild guess, can there be any old patches in 
/usr/ports/x11-servers/xorg-server/files? At revision 311359 port should 
contain only:


# svn status -v
311359   310652 zeising  .
311359   310652 zeising  Makefile
311359   300897 beat distinfo
311359   310652 zeising  files
311359   300897 beat files/extra-arch-ia64
311359   300897 beat files/extra-arch-powerpc
311359   308898 zeising  files/extra-clang
311359   300897 beat files/extra-dix_events.c
311359   300897 beat 
files/extra-hw_dmx_glxProxy_compsize.h
311359   300897 beat 
files/extra-hw_dmx_glxProxy_glxcmds.h

311359   300897 beat files/extra-include_eventstr.h
311359   310652 zeising  files/extra-new-arch-i386
311359   310652 zeising  files/extra-old-arch-i386
311359   300897 beat files/extra-patch-os-utils.c
311359   300897 beat 
files/patch-Xserver-hw-xfree86-common-xf86Config.c
311359   300897 beat 
files/patch-Xserver-hw-xfree86-os-support-bsd-i386_video.c
311359   300897 beat 
files/patch-Xserver-hw-xfree86-os-support-bsd-sparc64_video.c

311359   300897 beat files/patch-Xserver-os-xprintf.c
311359   300897 beat files/patch-servermd.h
311359   300897 beat files/patch-xorgconf.cpp
311359   303429 kwm  files/pkg-deinstall.in
311359   303429 kwm  files/pkg-install.in
311359   300897 beat pkg-descr
311359   303429 kwm  pkg-plist

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: No more torrents.....

2012-12-19 Thread Volodymyr Kostyrko

19.12.2012 01:22, Peter Wemm:

I would be very much be willing to assist with seeding if we make dht
torrent files available from my nodes located in downtown Los Angeles
for west-coast and APAC network presence.

as an aside:
I have been running libtorrent/rtorrent for a bit and it seems like a
pretty decent platform for building on.  having said that - I am not a
security researcher and would be keen to hear if libtorrent/rotrrent
suffers from these similar issues?


Oh wait, I told a lie.  It wasn't py-bittornado we used.. it was
rtorrent.  Thanks for prompting that.

I have no concerns with rtorrent except that it was a curses beastie.
It was something we had to manually start up after a machine reboot
until we did some evil scripts with screen.


The ports contain at least two torrent clients that can daemonize: 
transmission and btpd. At least first one surely knows about DHT.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: -stdlib=libc++ fails for some ports

2012-11-30 Thread Volodymyr Kostyrko

29.11.2012 23:38, Dimitry Andric:

I merged the snapshot to stable/9 in r243683.


Thank you.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


-stdlib=libc++ fails for some ports

2012-11-29 Thread Volodymyr Kostyrko

Hi all.

When compiling databases/db5 with CFLAGS+= -stdlib=libc++ I got this:

libtool: compile:  c++ -c -I. -I./../src -D_THREAD_SAFE -O2 -pipe 
-march=native -fno-strict-aliasing -stdlib=libc++ ../lang/cxx/cxx_db.cpp 
 -fPIC -DPIC -o .libs/cxx_db.o

In file included from ../lang/cxx/cxx_channel.cpp:13:
In file included from ./db_cxx.h:55:
In file included from /usr/include/c++/v1/iostream:38:
In file included from /usr/include/c++/v1/ios:216:
In file included from /usr/include/c++/v1/__locale:15:
In file included from /usr/include/c++/v1/string:434:
In file included from /usr/include/c++/v1/algorithm:590:
In file included from /usr/include/c++/v1/initializer_list:47:
/usr/include/c++/v1/cstddef:64:61: error: expected class member or base 
class name

_LIBCPP_ALWAYS_INLINE _LIBCPP_CONSTEXPR nullptr_t() : _(0) {}
^
./db_int.h:445:16: note: expanded from macro '_'
#define _(msg)  msg /* Replace with localization function. */
^

The problem is actually on libc++ side and has been fixed upstream:

http://llvm.org/viewvc/llvm-project?view=revrevision=167038

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Help review the FAQ

2012-11-26 Thread Volodymyr Kostyrko

26.11.2012 16:49, Jakub Lach:

Absolutely not, it's a heavily stripped custom kernel on this machine on
/boot/.


Do you call this heavily stripped? :)

 ls -la /boot/kernel/kernel
-r-xr-xr-x  1 root  wheel  5757970 Nov 26 10:57 /boot/kernel/kernel

However it's very hard to strip kernel further and make it usable for 
all machines.



I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
be
1.5-2.5 MB.


That's true...

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Latest for buildworld + clang + ccache

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 10:59, Beeblebrox:

9.1-PRERELEASE #2 r242867: When will buildworld + clang + ccache be
functional?
I think I read somewhere that buildworld + clang - ccache was working fine
now. Any info on date ccache will work with clang and when to try?


Define CCACHE_CPP2 as otherwise clang will yell at ccache trying to 
compile precompiled source with extra flags. This breaks libtool and a 
some other autoconf tests.


Care to not specify CCACHE_CPP2 for virtualbox and friends.


Also, clang users - do you see any speed advantage for kernel / world /
ports built with clang?


Builds faster.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Latest for buildworld + clang + ccache

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 11:20, Beeblebrox:

Care to not specify CCACHE_CPP2 for virtualbox and friends.

Not true for Jails I assume?


No, it's just that virtualbox still doesn't build with clang and gcc 
doesn't really like some -MD (?) flags.



Define CCACHE_CPP2 as otherwise clang will yell at ccache

Is this the same reason CMAKE yells at CCACHE?


Haven't seen this before. Can you share?

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Latest for buildworld + clang + ccache

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 11:30, Beeblebrox:

Is this the same reason CMAKE yells at CCACHE?

Haven't seen this before. Can you share?

I meant for ports, not buildworld...

I use bsdadminscripts  and specify preferences in
/usr/local/etc/buildflags.conf. I tried these and did not work. What is the
setting for this, and I assume I can set CCACHE_CPP2 in that file also?
USE_GCC=clang
BUILDFLAGS_GCC= clang


CC= clang
CPP= clang-cpp
CXX= clang++

Yes, you can include CCACHE_CPP2 in this file too.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Latest for buildworld + clang + ccache

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 11:46, Beeblebrox:

I think I made a mistake:
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
*** [tblgen] Error code 1
1 error
*** [bootstrap-tools] Error code 2
1 error
*** [_bootstrap-tools] Error code 2
1 error
*** [buildworld] Error code 2

in /urs/local/buildflags.conf I have:
/usr/src | /usr/src/*{
 CC= clang
 CPP=clang
 CXX=clang
 USE_CCACHE
 USE_CCACHE_CPP2  }


What I wrote is right for ports but not world. ccache port comes with 
readme file for this setup.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: buildworld with clang breaks because no cc

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 15:45, Beeblebrox:

I am now stuck with trying to make this work. I am doing buildworld with
clang and ccache enabled.

1. I have to keep re-starting buildworld at different points of break. When
re-started the build continues past the last break-point and goes on to
break somewhere else.
2. This continues until build gets to === usr.bin/ypwhich (all) and cannot
continue past the error.
3. I disable ccache in /usr/local/etc/buildflags.conf and re-start the
build. Progresses upto:
sh /asp/src/tools/install.sh -s -o root -g wheel -m 444 libz.so.6
/usr/obj/asp/src/lib32/usr/lib32
ln -fs libz.so.6 /usr/obj/asp/src/lib32/usr/lib32/libz.so

However, examining the contents after build-break of
/usr/obj/asp/src/lib32/usr/lib32/ shows libz.so.6 and its linked alias
libz.so.
I am not able to move any further without help because I cannot figure out
where the problem may be.

Thanks for any help.


Try running make buildworld without -j.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: buildworld with clang breaks because no cc

2012-11-23 Thread Volodymyr Kostyrko

23.11.2012 16:14, Beeblebrox:

Thanks for the suggestion. Build progressed a little further then had other
problem:

=== gnu/lib/libstdc++ (all)
building shared library libstdc++.so.6
/usr/obj/asp/src/tmp/usr/bin/ld: warning: creating a DT_TEXTREL in a shared
object.
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
*** [libstdc++.so.6] Error code 1
Stop in /asp/src/gnu/lib/libstdc++.
*** [all] Error code 1
Stop in /asp/src/gnu/lib.
*** [gnu/lib__L] Error code 1

Why is it building gcc4.2 ?? Should I not be using WITH_CLANG_IS_CC= yes ?
Bummer...


I'd rather say you should recheck/post your relevant make.conf / 
src.conf options. And WITHOUT_GCC is not right thing to do for now, gcc 
is still needed for a number of ports.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Logging of installed packages.

2012-11-20 Thread Volodymyr Kostyrko

20.11.2012 11:24, Peter Ankerstål wrote:

In the light of this: http://www.freebsd.org/news/2012-compromise.html

It would be nice if there was default way to log all package installations from 
both pkgs and ports.
Is there? If not, what would you recommend for doing this?


pkgng logs all installations/deinstallations. It's already default for 
CURRENT and you can switch to using it for other branches.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

buildworld fails on recent stable

2012-11-05 Thread Volodymyr Kostyrko

Hi all.

When CLANG_IS_CC build fails at sys/boot/i386/boot2:

ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o 
boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o 
sio.o

objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b 
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o 
boot2.ld -P 1 boot2.bin

kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1
client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0
output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0
-5 bytes available
*** [boot2] Error code 1

The relevant output before r242562 looked like:

ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o 
boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o 
sio.o

objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b 
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o 
boot2.ld -P 1 boot2.bin

kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1
client: fmt=bin size=1569 text=0 data=0 bss=0 entry=0
output: fmt=bin size=1df9 text=200 data=1bf9 org=0 entry=0
7 bytes available
dd if=boot2.ld of=boot2 obs=7680 conv=osync

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: buildworld fails on recent stable

2012-11-05 Thread Volodymyr Kostyrko

05.11.2012 17:42, Andriy Gapon wrote:

on 05/11/2012 16:51 Dimitry Andric said the following:

On 2012-11-05 12:41, Volodymyr Kostyrko wrote:

When CLANG_IS_CC build fails at sys/boot/i386/boot2:

ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o
boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o
sio.o
objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
boot2.ld -P 1 boot2.bin
kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1
client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0
output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0
-5 bytes available


This seems to be caused by r242562, which is an MFC of r241301.  The
code changes are quite trivial though.  Strangely enough, on head it
does build successfully, but head is using a newer version of clang, so
that may explain the difference.  Investigating...


I suspect that some earlier space-saving commit was not MFC-ed to stable/9.



This can be easily checked:

# cd /usr/src/sys/boot/i386/boot2/
# make clean
# svn up
Updated to revision 242616.
# setenv PATH /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# unsetenv CCACHE_PATH
# /usr/local/bin/clang -v
clang version 3.2 (trunk)
Target: amd64-portbld-freebsd9.1
Thread model: posix
# echo CC=/usr/local/bin/clang  /etc/src.conf
# echo CXX=/usr/local/bin/clang++  /etc/src.conf
# make

ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o 
boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o 
sio.o

objcopy -S -O binary boot2.out boot2.bin
btxld -v -E 0x2000 -f bin -b 
/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o 
boot2.ld -P 1 boot2.bin

kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1
client: fmt=bin size=154d text=0 data=0 bss=0 entry=0
output: fmt=bin size=1ddd text=200 data=1bdd org=0 entry=0
35 bytes available
dd if=boot2.ld of=boot2 obs=7680 conv=osync
14+1 records in
1+0 records out
7680 bytes transferred in 0.99 secs (77433305 bytes/sec)

I bet on clang 3.2.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: buildworld fails on recent stable

2012-11-05 Thread Volodymyr Kostyrko

05.11.2012 18:00, Andriy Gapon wrote:

I bet on clang 3.2.


Thank you for checking.

So how do we proceed from here?
I could just revert the MFC-es, but the functionality could be desirable to some
users.  Are there any alternatives?


Dunno, clang 3.2 is still pending so I guess it wouldn't be MFC'ed until 
December 16th? Being a minor issue it can make some people shrug from 
using clang for testing stable...


I think reverting the working change is not good as far as building 
world with clang is still not the true and default way.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: wine, gcc and clang with CPUTYPE

2012-11-05 Thread Volodymyr Kostyrko

05.11.2012 17:47, Howard Goldstein wrote:

Volodymyr, your initial email in this thread regarding clang's being
stuck on native code generation allowed me to wrap up a week of fighting
with an updated production box with a weird wine issue - thank you!

FWIW I filed a pr on this.  You've done much more useful legwork towards
a solution of the problem and I wanted to point it out to everyone how
helpful it was.  THANK YOU!

The pr is at http://www.freebsd.org/cgi/query-pr.cgi?pr=173337


I'm still unsure of my results though. I can't reproduce gcc core dump 
anymore. I think it's shadowed by some later fix.


As for wine my results are not complete:

1. Building a world with CPUTYPE=athlon-tbird on a world built with 
CPUTYPE=k6 makes wine work.
2. Building a world with CPUTYPE=athlon-tbird on a world built with 
CPUTYPE=athlon-xp makes wine fail.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


wine, gcc and clang with CPUTYPE

2012-10-24 Thread Volodymyr Kostyrko

Hi all.

I just have taken some time to inspect CPUTYPE support for clang. It 
seems to me that clang generates incorrect code in some cases.


The first failure point I discovered was inability to build gcc from 
sources or compile something with gcc. Code produced by gcc seem to fail 
whether this was gcc compiled from bootstrap or anything else:


http://lists.freebsd.org/pipermail/freebsd-multimedia/2012-October/013469.html

I started testing by commenting out CPUTYPE in make.conf. After first 
rebuild I also updated the ports and installed new version of 
wine-devel. And to my surprise it works like a charm. Rolling back to 
the world built with CPUTYPE=native makes wine break again.


To my surprise CPUTYPE was not the cause of wine failure per se. Wine 
continues to work for k6, k6-3, athlon and athlon-tbird. But it 
completely fails when the world was built with athlon-4 and athlon-xp.


Trying to recompile gcc I also found that everything works and yet again 
up to the athlon-tbird.


My conclusion is: clang incorrectly produces code within one of core 
libraries (I haven't tested which one yet, but I suspect libgcc_s.so) 
when optimizing for athlon-4 or athlon-xp.


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: wine, gcc and clang with CPUTYPE

2012-10-24 Thread Volodymyr Kostyrko

24.10.2012 11:12, Konstantin Belousov wrote:


My conclusion is: clang incorrectly produces code within one of core
libraries (I haven't tested which one yet, but I suspect libgcc_s.so)
when optimizing for athlon-4 or athlon-xp.


I am not versed in the AMD marketing monikers. I guess that athlon-{4,xp}
turns on SSE and might be SSE2, while previous selections turn it off.
Can you confirm/deny this ?


As http://en.wikipedia.org/wiki/Athlon states athlon-xp was first to 
include SSE support. I don't know whether athlon-xp actually differs 
from athlon-4. None of them include SSE2 support.



BTW, did you tested on i386 or amd64 ?


i386

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: wine, gcc and clang with CPUTYPE

2012-10-24 Thread Volodymyr Kostyrko

24.10.2012 13:05, Dimitry Andric wrote:

I just have taken some time to inspect CPUTYPE support for clang. It
seems to me that clang generates incorrect code in some cases.

The first failure point I discovered was inability to build gcc from
sources or compile something with gcc. Code produced by gcc seem to fail
whether this was gcc compiled from bootstrap or anything else:

http://lists.freebsd.org/pipermail/freebsd-multimedia/2012-October/013469.html


Can you attempt to figure out what the illegal instruction was, in that
case?


How can I do that? I'm not very familiar with gdb.


I started testing by commenting out CPUTYPE in make.conf. After first
rebuild I also updated the ports and installed new version of
wine-devel. And to my surprise it works like a charm. Rolling back to
the world built with CPUTYPE=native makes wine break again.

To my surprise CPUTYPE was not the cause of wine failure per se. Wine
continues to work for k6, k6-3, athlon and athlon-tbird. But it
completely fails when the world was built with athlon-4 and athlon-xp.

Trying to recompile gcc I also found that everything works and yet again
up to the athlon-tbird.

My conclusion is: clang incorrectly produces code within one of core
libraries (I haven't tested which one yet, but I suspect libgcc_s.so)
when optimizing for athlon-4 or athlon-xp.


On the problematic athlons, can you please post the exact CPUIDs from
dmesg?  If you have WITH_CLANG_EXTRAS enabled, please also post the
output of opt -version.


Oct 24 01:47:20 limbo kernel: CPU: AMD Athlon(tm) XP 2500+ (1833.95-MHz 
686-class CPU)
Oct 24 01:47:20 limbo kernel: Origin = AuthenticAMD  Id = 0x6a0 
Family = 0x6  Model = 0xa  Stepping = 0
Oct 24 01:47:20 limbo kernel: 
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
Oct 24 01:47:20 limbo kernel: AMD 
Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow!


I will rebuild WITH_CLANG_EXTRAS.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: wine, gcc and clang with CPUTYPE

2012-10-24 Thread Volodymyr Kostyrko

24.10.2012 14:00, Dimitry Andric wrote:

On the problematic athlons, can you please post the exact CPUIDs from
dmesg?  If you have WITH_CLANG_EXTRAS enabled, please also post the
output of opt -version.


Oct 24 01:47:20 limbo kernel: CPU: AMD Athlon(tm) XP 2500+ (1833.95-MHz
686-class CPU)
Oct 24 01:47:20 limbo kernel: Origin = AuthenticAMD  Id = 0x6a0
Family = 0x6  Model = 0xa  Stepping = 0


Ok, this CPU should be recognized by llvm as athlon-xp.  There is in
fact no need to compile all the WITH_CLANG_EXTRAS programs, I just
remembered.

If you compile a sample program with -march=native -v, it should show
you the detected CPU in the verbose command line output, e.g.:

   $ clang -v -march=native -c /home/dim/src/example.c
   FreeBSD clang version 3.2 (trunk 162107) 20120817
   Target: i386-unknown-freebsd10.0
   Thread model: posix
/usr/bin/clang -cc1 -triple i386-unknown-freebsd10.0 -emit-obj
-mrelax-all -disable-free -main-file-name example.c -mrelocation-model
static -mdisable-fp-elim -masm-verbose -mconstructor-aliases -target-cpu
core2 -momit-leaf-frame-pointer -v -coverage-file hw.o -resource-dir
/usr/bin/../lib/clang/3.2 -fmodule-cache-path
/home/dim/tmp/clang-module-cache -fdebug-compilation-dir /home/dim/src
-ferror-limit 19 -fmessage-length 265 -mstackrealign
-fobjc-runtime=gnustep -fdiagnostics-show-option -fcolor-diagnostics -o
hw.o -x c /home/dim/src/example.c
   clang -cc1 version 3.2 based upon LLVM 3.2svn default target
i386-unknown-freebsd10.0
   ignoring nonexistent directory /usr/bin/../lib/clang/3.2/include
   #include ... search starts here:
   #include ... search starts here:
/usr/include/clang/3.2
/usr/include
   End of search list.

In my case, it uses -target-cpu core2, as you can see.


Yes, my CPU is detected as athlon-xp by clang:

# : | clang -v -E -march=native -
FreeBSD clang version 3.1 (branches/release_31 156863) 20120523
Target: i386-unknown-freebsd9.0
Thread model: posix
 /usr/bin/clang -cc1 -triple i386-unknown-freebsd9.0 -E -disable-free 
-main-file-name - -mrelocation-model static -mdisable-fp-elim 
-masm-verbose -mconstructor-aliases -target-cpu athlon-xp 
-momit-leaf-frame-pointer -v -resource-dir /usr/bin/../lib/clang/3.1 
-fmodule-cache-path /var/tmp/clang-module-cache -fdebug-compilation-dir 
/usr/src -ferror-limit 19 -fmessage-length 186 -mstackrealign 
-fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak 
-fobjc-dispatch-method=non-legacy -fdiagnostics-show-option 
-fcolor-diagnostics -o - -x c -
clang -cc1 version 3.1 based upon LLVM 3.1 default target 
i386-unknown-freebsd9.0

ignoring nonexistent directory /usr/bin/../lib/clang/3.1/include
#include ... search starts here:
#include ... search starts here:
 /usr/include/clang/3.1
 /usr/include
End of search list.
# 1 stdin
# 1 stdin 1
# 1 built-in 1
# 1 built-in 3
# 147 built-in 3
# 1 command line 1
# 1 built-in 2
# 1 stdin 2

And as athlon-4 by gcc:

# : | gcc -v -E -march=native -
Using built-in specs.
Target: i386-undermydesk-freebsd
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]
 /usr/libexec/cc1 -E -quiet -v -D_LONGLONG - -march=athlon-4 
-mtune=athlon-4

#include ... search starts here:
#include ... search starts here:
 /usr/include/gcc/4.2
 /usr/include
End of search list.
# 1 stdin
# 1 built-in
# 1 command-line
# 1 stdin

# : | gcc46 -v -E -march=native -
Using built-in specs.
COLLECT_GCC=/usr/local/bin/gcc46
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc46/gcc/i386-portbld-freebsd9.1/4.6.3/lto-wrapper
Target: i386-portbld-freebsd9.1
Configured with: ./../gcc-4.6.3/configure --disable-bootstrap 
--disable-nls --libdir=/usr/local/lib/gcc46 
--libexecdir=/usr/local/libexec/gcc46 --program-suffix=46 
--with-as=/usr/local/bin/as --with-gmp=/usr/local 
--with-gxx-include-dir=/usr/local/lib/gcc46/include/c++/ 
--with-ld=/usr/local/bin/ld --with-libiconv-prefix=/usr/local 
--with-pkgversion='FreeBSD Ports Collection' --with-system-zlib 
--disable-libgcj --enable-languages=c,c++,objc,fortran 
--prefix=/usr/local --mandir=/usr/local/man 
--infodir=/usr/local/info/gcc46 --build=i386-portbld-freebsd9.1

Thread model: posix
gcc version 4.6.3 (FreeBSD Ports Collection)
COLLECT_GCC_OPTIONS='-v' '-E' '-march=native'
 /usr/local/libexec/gcc46/gcc/i386-portbld-freebsd9.1/4.6.3/cc1 -E 
-quiet -v - -march=athlon-4 -mno-cx16 -mno-sahf -mno-movbe -mno-aes 
-mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop 
-mno-bmi -mno-tbm -mno-avx -mno-sse4.2 -mno-sse4.1 --param 
l1-cache-size=64 --param l1-cache-line-size=64 --param l2-cache-size=512 
-mtune=athlon
ignoring nonexistent directory 
/usr/local/lib/gcc46/gcc/i386-portbld-freebsd9.1/4.6.3/../../../../../i386-portbld-freebsd9.1/include

#include ... search starts here:
#include ... search starts here:
 /usr/local/lib/gcc46/gcc/i386-portbld-freebsd9.1/4.6.3/include
 /usr/local/include
 /usr/local/lib/gcc46/gcc/i386-portbld-freebsd9.1/4.6.3/include-fixed
 /usr/include
End 

Re: kern.maxswzone is gone... what next?

2012-10-12 Thread Volodymyr Kostyrko

11.10.2012 19:27, Andriy Gapon wrote:

On 11 October 2012 19:32, Volodymyr Kostyrko c.kw...@gmail.com wrote:

Hi all.

I prefer to build all ports in /tmp, which is actually a tmpfs filesystem. I
have 8G partition. But when I tried to compile Apache OpenOffice system
starts shooting processes when I was near 6G of swap.

Oct 11 18:12:32 ar1l0u kernel: swap zone exhausted, increase kern.maxswzone
Oct 11 18:12:32 ar1l0u kernel: pid 1334 (java), uid 818, was killed: out of
swap space
Oct 11 18:12:32 ar1l0u kernel: pid 74518 (thunderbird), uid 1001, was
killed: out of swap space
Oct 11 18:12:32 ar1l0u kernel: swap zone ok



How much RAM (avail memory) do you have?


2G



What does vmstat -z | fgrep -i swap show?


SWAPMETA:   288, 252902, 363, 339,   38104,   0,   0

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


kern.maxswzone warning on boot

2012-10-12 Thread Volodymyr Kostyrko

Hi all.

I updated my old i386 machine and now it says:

Oct  8 16:57:12 limbo kernel: warning: total configured swap (2100821 
pages) exceeds maximum recommended amount (2041984 pages).
Oct  8 16:57:12 limbo kernel: warning: increase kern.maxswzone or reduce 
amount of swap.


I though someone tried to remove that warning with kern.maxswzone 
tunable altogether... What should I do to fix that?


# uname -a
FreeBSD limbo.xim.bz 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #1 r241326M: 
Mon Oct  8 05:00:21 EEST 2012 
arc...@limbo.xim.bz:/usr/obj/usr/src/sys/MINIMALx32  i386


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


kern.maxswzone is gone... what next?

2012-10-11 Thread Volodymyr Kostyrko

Hi all.

I prefer to build all ports in /tmp, which is actually a tmpfs 
filesystem. I have 8G partition. But when I tried to compile Apache 
OpenOffice system starts shooting processes when I was near 6G of swap.


Oct 11 18:12:32 ar1l0u kernel: swap zone exhausted, increase kern.maxswzone
Oct 11 18:12:32 ar1l0u kernel: pid 1334 (java), uid 818, was killed: out 
of swap space
Oct 11 18:12:32 ar1l0u kernel: pid 74518 (thunderbird), uid 1001, was 
killed: out of swap space

Oct 11 18:12:32 ar1l0u kernel: swap zone ok

As I'm running rather current version I see r240097 in the log that 
states that there is no maxswzone setting for amd64 anymore. When I 
tried to query this parameter I got:


 sysctl kern.maxswzone
kern.maxswzone: 0

What was that? Did that mean that 6G is a maximum swap size now?

PS: I'm retrying now with kern.maxswzone set to 256M.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: kern.maxswzone is gone... what next?

2012-10-11 Thread Volodymyr Kostyrko

11.10.2012 18:37, Sergey Kandaurov wrote:

On 11 October 2012 19:32, Volodymyr Kostyrko c.kw...@gmail.com wrote:

Hi all.

I prefer to build all ports in /tmp, which is actually a tmpfs filesystem. I
have 8G partition. But when I tried to compile Apache OpenOffice system
starts shooting processes when I was near 6G of swap.

Oct 11 18:12:32 ar1l0u kernel: swap zone exhausted, increase kern.maxswzone
Oct 11 18:12:32 ar1l0u kernel: pid 1334 (java), uid 818, was killed: out of
swap space
Oct 11 18:12:32 ar1l0u kernel: pid 74518 (thunderbird), uid 1001, was
killed: out of swap space
Oct 11 18:12:32 ar1l0u kernel: swap zone ok



How much RAM (avail memory) do you have?


2G

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: kern.maxswzone is gone... what next?

2012-10-11 Thread Volodymyr Kostyrko

11.10.2012 18:50, Andreas Nilsson wrote:

I can chime in with the exact same error. I was using poudriere to build
some ports, and on apache-oo the machine actually had a kernel panic.
Machine has 16gb of ram and 16gb swap.

I had top running (update every 1 sec) and there was 10gb of swap free
when panic happened.

The OS is fbsd 9.1-PRERELEASE, from before problematic changes with
nullfs/zfs interaction.


 uname -a
FreeBSD ar1l0u 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241438M: Thu 
Oct 11 10:20:20 EEST 2012 arcade@ar1l0u:/usr/obj/usr/src/sys/MINIMAL 
 amd64


Added patches: tmpfs nrbtree, zfs feats.

--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


lang/gcc fails building on old processor

2012-10-03 Thread Volodymyr Kostyrko

Hello.

It seems that lang/gcc starts producing incorrect binaries after some 
point. Right now it stops building with:


checking whether to build static libraries... yes
libtool.m4: error: problem compiling FC test program
checking for /tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/ 
-B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem 
/usr/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includeoption to produce PIC...
checking if /tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/ 
-B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem 
/usr/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includestatic flag  works... no
checking if /tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/ 
-B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem 
/usr/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includesupports -c -o 
file.o... no
checking if /tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/ 
-B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem 
/usr/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includesupports -c -o 
file.o... (cached) no
checking whether the 
/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/ 
-B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem 
/usr/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includelinker 
(/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/collect-ld) supports 
shared libraries... yes

checking dynamic linker characteristics... freebsd9.1 ld.so
checking how to hardcode library paths into programs... immediate
checking whether the GNU Fortran compiler is working... no
configure: error: GNU Fortran is not working; please report a bug in 
http://gcc.gnu.org/bugzilla, attaching 
/tmp/ports/usr/ports/lang/gcc/work/build/i386-portbld-freebsd9.1/libgfortran/config.log


configure:12860: /tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc/work/build/
./gcc/ -B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem /usr/local/i386-
portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-include-c   conftest.f 5

built-in:0:0: internal compiler error: Illegal instruction: 4
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
configure:12863: $? = 1
configure:12991: checking for 
/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gc
c/work/build/./gcc/ -B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem /us
r/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includeoption to produce

 PIC
configure:13276: result:
configure:13341: checking if 
/tmp/ports/usr/ports/lang/gcc/work/build/./gcc/gfortran 
-B/tmp/ports/usr/ports/lang/gcc
/work/build/./gcc/ -B/usr/local/i386-portbld-freebsd9.1/bin/ 
-B/usr/local/i386-portbld-freebsd9.1/lib/ -isystem /usr
/local/i386-portbld-freebsd9.1/include -isystem 
/usr/local/i386-portbld-freebsd9.1/sys-includestatic flag  works

configure:13369: result: no

Same with or without CPUTYPE set, building with clang or with in-base gcc.

My CPU is:
Oct  2 17:57:10 limbo kernel: CPU: AMD Athlon(tm) XP 2500+ (1833.95-MHz 
686-class CPU)
Oct  2 17:57:10 limbo kernel: Origin = AuthenticAMD  Id = 0x6a0 
Family = 0x6  Model = 0xa  Stepping = 0
Oct  2 17:57:10 limbo kernel: 
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
Oct  2 17:57:10 limbo kernel: AMD 
Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow!


--
Sphinx of black quartz, judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Missing lib on linking libc WITH_LIBCPLUSPLUS

2012-10-02 Thread Volodymyr Kostyrko

Hi all.

When enabling WITH_LIBCPLUSPLUS libc build fails with:

/usr/local/libexec/ccache/clang++  -O2 -pipe -march=native 
-I/usr/src/lib/libc++/../../contrib/libc++/include 
-I/usr/src/lib/libc++/../../contrib/libcxxrt -nostdlib -DLIBCXXRT 
-Qunused-arguments -fstack-protector -Wno-empty-body 
-Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value 
-Wno-parentheses-equality -Wno-unused-function -Wno-conversion 
-Wno-switch -Wno-switch-enum -Wno-parentheses -std=c++0x -c 
cxxrt_guard.cc -o cxxrt_guard.o

building shared library libc++.so.1
FreeBSD clang version 3.1 (branches/release_31 156863) 20120523
Target: x86_64-unknown-freebsd9.0
Thread model: posix
 /usr/bin/ld --eh-frame-hdr -Bshareable -o libc++.so.1 
/usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x --fatal-warnings 
--warn-shared-textrel -soname libc++.so.1 valarray.So utility.So 
typeinfo.So strstream.So regex.So random.So iostream.So debug.So 
chrono.So bind.So algorithm.So hash.So thread.So future.So exception.So 
locale.So mutex.So memory.So ios.So condition_variable.So 
system_error.So string.So stdexcept.So new.So -lcxxrt -lgcc --as-needed 
-lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed 
/usr/lib/crtendS.o /usr/lib/crtn.o

/usr/bin/ld: cannot find -lcxxrt
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)


This lib was already built:

# find /usr/obj -name libcxxrt.so
/usr/obj/usr/src/tmp/usr/lib/libcxxrt.so
/usr/obj/usr/src/lib/libcxxrt/libcxxrt.so

But this error is only fixed after:

# cd /usr/src/lib/libcxxrt ; make install

Other irrelevant data:

# uname -a
FreeBSD ar1l0u 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r241089M: Mon 
Oct  1 12:48:30 EEST 2012 arcade@ar1l0u:/usr/obj/usr/src/sys/MINIMAL 
 amd64


World is built WITH_CLANG_IS_CC and with ccache. Modifications are tmpfs 
directory patch.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Missing lib on linking libc WITH_LIBCPLUSPLUS

2012-10-02 Thread Volodymyr Kostyrko

02.10.2012 12:12, Dimitry Andric wrote:

On 2012-10-02 09:53, Volodymyr Kostyrko wrote:

When enabling WITH_LIBCPLUSPLUS libc build fails with:

/usr/local/libexec/ccache/clang++  -O2 -pipe -march=native
-I/usr/src/lib/libc++/../../contrib/libc++/include
-I/usr/src/lib/libc++/../../contrib/libcxxrt -nostdlib -DLIBCXXRT
-Qunused-arguments -fstack-protector -Wno-empty-body
-Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value
-Wno-parentheses-equality -Wno-unused-function -Wno-conversion
-Wno-switch -Wno-switch-enum -Wno-parentheses -std=c++0x -c
cxxrt_guard.cc -o cxxrt_guard.o
building shared library libc++.so.1
FreeBSD clang version 3.1 (branches/release_31 156863) 20120523
Target: x86_64-unknown-freebsd9.0
Thread model: posix
   /usr/bin/ld --eh-frame-hdr -Bshareable -o libc++.so.1
/usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x --fatal-warnings
--warn-shared-textrel -soname libc++.so.1 valarray.So utility.So
typeinfo.So strstream.So regex.So random.So iostream.So debug.So
chrono.So bind.So algorithm.So hash.So thread.So future.So exception.So
locale.So mutex.So memory.So ios.So condition_variable.So
system_error.So string.So stdexcept.So new.So -lcxxrt -lgcc --as-needed
-lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed
/usr/lib/crtendS.o /usr/lib/crtn.o
/usr/bin/ld: cannot find -lcxxrt
clang: error: linker command failed with exit code 1 (use -v to see
invocation)

This lib was already built:

# find /usr/obj -name libcxxrt.so
/usr/obj/usr/src/tmp/usr/lib/libcxxrt.so
/usr/obj/usr/src/lib/libcxxrt/libcxxrt.so

But this error is only fixed after:

# cd /usr/src/lib/libcxxrt ; make install


Are you getting this error as part of buildworld, or when you build
libc++ by hand?


As part of the buildworld. I feel that it looks for the lib in the 
system skipping /usr/obj.



Also, an obvious question is: does it work when you disable ccache?


Bingo. Yes, disabling ccache makes everything work.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Missing lib on linking libc WITH_LIBCPLUSPLUS

2012-10-02 Thread Volodymyr Kostyrko

03.10.2012 00:48, Dimitry Andric wrote:

Bingo. Yes, disabling ccache makes everything work.

please ping the ccache folk about this. It *shouldn't* matter. :)


In this case, ccache apparently does not realize that the world stage is
using the toolchain built during the cross-tools stage, which usually is
in /usr/obj/usr/src/tmp/usr/bin.

This toolchain uses another include and lib path, e.g. it only refers to
headers and libraries under /usr/obj, specifically *not* those in the
base system.

In Volodymyr's original log, you can see /usr/bin/ld being invoked by
the compiler driver, not /usr/obj/usr/src/tmp/usr/bin/ld.  I think
ccache invokes /usr/bin/cc, instead of /usr/obj/usr/src/tmp/usr/bin/cc.

Normally ccache searches the PATH to find the 'real' cc executable, but
I am not sure why this goes wrong during the world stage.  It would be
interesting to see some verbose logging from ccache, to see how it finds
the cc executable here.


That's also a good catch. My system is configured according to 
/usr/ports/devel/ccache/files/ccache-howto-freebsd.txt.in and 
CCACHE_PATH is set to /usr/bin:/usr/local/bin. Can I ask you what is a 
preferrred way of dealing with the PATH in the buildworld?


1. Rely on what environment contains.
2. Hardcode some sane default for ccache.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Clang as default compiler

2012-09-12 Thread Volodymyr Kostyrko

12.09.2012 00:49, Andreas Nilsson wrote:

On another clang note: Is there a page specifying valid settings for
-march, my google-foo is failing me. Ie, I'm looking for the equivalent of
http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options


I'm using the minimum of:

   : | gcc -E -v -march=native -
   : | clang -E -v -march=native -

because there are number of ports that still doesn't compile with clang 
or GCC4.6.



After successful install I went on to upgrade some ports. Is there a specif
PR to use for ports that fails with clang and does not specify to use gcc (
devel/cdecl and deskutils/calibre so were the culprits so far)


It's up to you to fix this ports and submit patches. You can always 
rollback to using GCC.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: 9-STABLE (238719) compilation fails on i386

2012-07-25 Thread Volodymyr Kostyrko

Volodymyr Kostyrko wrote:

When building procstat I get this:

clang -O2 -pipe -march=athlon-xp -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c
/usr/src/usr.bin/procstat/procstat_vm.c
/usr/src/usr.bin/procstat/procstat_vm.c:76:36: error: use of undeclared
identifier 'KVME_FLAG_GROWS_UP'
printf(%-1s , kve-kve_flags  KVME_FLAG_GROWS_UP ? U :
^
/usr/src/usr.bin/procstat/procstat_vm.c:77:24: error: use of undeclared
identifier 'KVME_FLAG_GROWS_DOWN'
kve-kve_flags  KVME_FLAG_GROWS_DOWN ? D : -);
^
2 errors generated.
*** [procstat_vm.o] Error code 1

Stop in /usr/src/usr.bin/procstat.


`make buildincludes installincludes` fixed this.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


9-STABLE (238719) compilation fails on i386

2012-07-24 Thread Volodymyr Kostyrko

Hi all.

When building procstat I get this:

clang -O2 -pipe -march=athlon-xp -std=gnu99 -Qunused-arguments 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch 
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wold-style-definition 
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c 
/usr/src/usr.bin/procstat/procstat_vm.c
/usr/src/usr.bin/procstat/procstat_vm.c:76:36: error: use of undeclared 
identifier 'KVME_FLAG_GROWS_UP'

printf(%-1s , kve-kve_flags  KVME_FLAG_GROWS_UP ? U :
 ^
/usr/src/usr.bin/procstat/procstat_vm.c:77:24: error: use of undeclared 
identifier 'KVME_FLAG_GROWS_DOWN'

kve-kve_flags  KVME_FLAG_GROWS_DOWN ? D : -);
 ^
2 errors generated.
*** [procstat_vm.o] Error code 1

Stop in /usr/src/usr.bin/procstat.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: [CFT] radeon_suspend/resume patch

2012-06-26 Thread Volodymyr Kostyrko

Mitsuru IWASAKI wrote:

I created the patches for drm/radeon in order to restore the graphic
state on resuming (ported from NetBSD code).

http://people.freebsd.org/~iwasaki/acpi/drm-radeon_suspend-20120623.diff

Unfortunately, I don't have the machine to test the patches.
Can anyone test this?


 uname -a
FreeBSD limbo.xim.bz 9.0-STABLE FreeBSD 9.0-STABLE #0 r237562M: Tue Jun 
26 03:35:06 EEST 2012 
arc...@limbo.xim.bz:/usr/obj/usr/src/sys/MINIMALx32  i386


vgapci0@pci0:1:0:0: class=0x03 card=0x40501458 chip=0x41531002 
rev=0x00 hdr=0x00

vendor = 'ATI Technologies Inc'
device = 'RV350 AS [Radeon 9550]'
class  = display
subclass   = VGA
vgapci1@pci0:1:0:1: class=0x038000 card=0x40511458 chip=0x41731002 
rev=0x00 hdr=0x00

vendor = 'ATI Technologies Inc'
device = 'RV350 AS [Radeon 9550] (Secondary)'
class  = display

 kldstat
Id Refs AddressSize Name
 1  166 0x8340 5898bc   kernel
 21 0x8398a000 5900 atavia.ko
 32 0x8399 6990 ataahci.ko
 43 0x83997000 80b0 atapci.ko
 51 0x839a 18d7f0   zfs.ko
 62 0x83b2e000 165f0krpc.ko
 72 0x83b45000 3ffc opensolaris.ko
 81 0x83b4a000 dae4 ahci.ko
 91 0x88507000 a000 tmpfs.ko
102 0x8852 6000 procfs.ko
112 0x8852e000 7000 pseudofs.ko
121 0x8853d000 4000 fdescfs.ko
131 0x88563000 8000 linprocfs.ko
141 0x8858f000 2a000linux.ko
151 0x88916000 4000 usb_quirk.ko
167 0x88951000 2b000usb.ko
171 0x889b 2000 accf_http.ko
181 0x889c1000 8000 aio.ko
191 0x889db000 d000 ehci.ko
201 0x88a23000 b000 if_re.ko
211 0x88a5d000 1f000miibus.ko
221 0x88abb000 3000 speaker.ko
231 0x88ace000 a000 uhci.ko
241 0x88d4a000 5000 ums.ko
251 0x88f44000 9000 umass.ko
261 0x88fa2000 6000 ng_ubt.ko
27   11 0x88fc9000 c000 netgraph.ko
281 0x88fe3000 b000 ng_hci.ko
293 0x88fe1000 2000 ng_bluetooth.ko
301 0x8908a000 a000 ukbd.ko
311 0x89182000 f000 ng_l2cap.ko
321 0x8920b000 2ng_btsocket.ko
331 0x8929f000 4000 ng_socket.ko
341 0x89963000 3000 ng_mppc.ko
351 0x89967000 2000 rc4.ko
361 0x8998b000 3000 ng_iface.ko
371 0x899a6000 7000 ng_ppp.ko
381 0x899d3000 2000 ng_tee.ko
391 0x89a34000 4000 ng_ether.ko
401 0x89abd000 6000 ng_pppoe.ko
411 0x89b05000 e000 fuse.ko
421 0x8a008000 23000snd_au8830.ko
431 0x8a084000 4c000sound.ko
441 0x8af79000 52000radeon.ko
451 0x8b024000 15000drm.ko
461 0x8b057000 18000agp.ko

Jun 26 08:15:03 limbo acpi: suspend at 20120626 08:15:03
Jun 26 08:15:06 limbo kernel: info: [drm] Num pipes: 1
Jun 26 08:15:08 limbo kernel: uhub1: at usbus1, port 1, addr 1 
(disconnected)

Jun 26 08:15:08 limbo kernel: ugen1.2: Logitech at usbus1 (disconnected)
Jun 26 08:15:08 limbo kernel: ums0: at uhub1, port 2, addr 2 (disconnected)
Jun 26 08:15:08 limbo kernel: uhub2: at usbus2, port 1, addr 1 
(disconnected)
Jun 26 08:15:31 limbo kernel: uhub3: at usbus3, port 1, addr 1 
(disconnected)

Jun 26 08:15:31 limbo kernel: ugen3.2: Broadcom at usbus3 (disconnected)
Jun 26 08:15:31 limbo kernel: uhub4: at uhub3, port 1, addr 2 (disconnected)
Jun 26 08:15:31 limbo kernel: ugen3.3: vendor 0x0a12 at usbus3 
(disconnected)
Jun 26 08:15:31 limbo kernel: ubt0: at uhub4, port 1, addr 3 
(disconnected) 

Jun 26 08:15:31 limbo kernel: ugen3.4: vendor 0x0a5c at usbus3 
(disconnected) 

Jun 26 08:15:31 limbo kernel: ukbd0: at uhub4, port 2, addr 4 
(disconnected) 

Jun 26 08:15:31 limbo kernel: ugen3.5: vendor 0x0a5c at usbus3 
(disconnected) 

Jun 26 08:15:31 limbo kernel: ums1: at uhub4, port 3, addr 5 
(disconnected) 

Jun 26 08:15:31 limbo kernel: uhub0: at usbus0, port 1, addr 1 
(disconnected) 

Jun 26 08:15:31 limbo kernel: ugen0.2: Kingston at usbus0 
(disconnected) 

Jun 26 08:15:31 limbo kernel: umass0: at uhub0, port 6, addr 2 
(disconnected) 

Jun 26 08:15:31 limbo kernel: (da0:umass-sim0:0:0:0): lost device - 0 
outstanding, 0 refs 

Jun 26 08:15:31 limbo kernel: (da0:umass-sim0:0:0:0): removing device 
entry 

Jun 26 08:15:31 limbo kernel: wakeup from sleeping state (slept 
00:00:19) 

Jun 26 08:15:31 limbo kernel: re0: link state changed to DOWN 



Jun 26 08:15:31 limbo kernel: uhub0: VIA EHCI root HUB, class 9/0, rev 
2.00/1.00, addr 1 on usbus0 

Jun 26 08:15:31 limbo kernel: uhub1: VIA UHCI root HUB, class 9/0, rev 
1.00/1.00, addr 1 on usbus2 

Jun 26 08:15:31 limbo kernel: uhub2: VIA UHCI root HUB, class 9/0, rev 
1.00/1.00, addr 1 on usbus1 

Jun 26 08:15:31 limbo kernel: uhub3: VIA UHCI root HUB, class 9/0, rev 
1.00/1.00, addr 1 on usbus3 

Jun 26 08:15:31 limbo kernel: uhub1: 2 ports with 2 removable, self 
powered 

Jun 26 08:15:31 limbo kernel: uhub2: 2 ports with 2 removable, self 
powered 

Jun 26 08:15:31 limbo kernel: uhub3: 2 ports with 2 

Re: [CFT] radeon_suspend/resume patch

2012-06-25 Thread Volodymyr Kostyrko

Mitsuru IWASAKI wrote:

I created the patches for drm/radeon in order to restore the graphic
state on resuming (ported from NetBSD code).

http://people.freebsd.org/~iwasaki/acpi/drm-radeon_suspend-20120623.diff

Unfortunately, I don't have the machine to test the patches.
Can anyone test this?


I have a desktop with Radeon 9550 AS. How can I trigger suspend/resume 
on that one manually?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: [CFT] radeon_suspend/resume patch

2012-06-25 Thread Volodymyr Kostyrko

Mitsuru IWASAKI wrote:

I have a desktop with Radeon 9550 AS. How can I trigger suspend/resume
on that one manually?


It's depends on whether the system support S3.  Please check it like this;
# sysctl hw.acpi.supported_sleep_state


hw.acpi.supported_sleep_state: S1 S3 S4 S5


If supported, to suspend;
# acpiconf -s 3
or
# zzz

To resume, just press the power button.


0k, rebuilding. I'll post results when ready.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ServeRAID BR10il (LSISAS1064E)

2012-05-16 Thread Volodymyr Kostyrko

Alexey V. Panfilov wrote:

I try to boot from CDROM with FreeBSD on IBM xServer x3250 M4 (P/N
2583-72G), but it always crash with message: NMI ISA b8, EISA ff
RAM parity error, likely hardware failure.


This can be RAM error.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ServeRAID BR10il (LSISAS1064E)

2012-05-16 Thread Volodymyr Kostyrko

Alexey V. Panfilov wrote:

P.S. my case is the same as
http://forums.freebsd.org/showthread.php?t=11222


And this is strange, on the machine where I have this one installed (as 
all other machines) I keep a MINIMAL kernel loading everything possible 
from modules. Distilled kernel config looks like:


options   CONFIG_AUTOGENERATED
ident   MINIMAL
machine amd64
cpu HAMMER
makeoptions DEBUG=-g
options DDB
options ALTQ_NOPCC
options ALTQ_PRIQ
options ALTQ_CDNR
options ALTQ_HFSC
options ALTQ_RIO
options ALTQ_RED
options ALTQ_CBQ
options ALTQ
options SW_WATCHDOG
options ZERO_COPY_SOCKETS
options SC_MOUSE_CHAR=0x3
options SC_ALT_MOUSE_IMAGE
options DIRECTIO
options BPF_JITTER
options DEVICE_POLLING
options USB_DEBUG
options AH_SUPPORT_AR5416
options IEEE80211_SUPPORT_MESH
options IEEE80211_AMPDU_AGE
options IEEE80211_DEBUG
options SC_PIXEL_MODE
options AHD_REG_PRETTY_PRINT
options AHC_REG_PRETTY_PRINT
options ATA_CAM
options SMP
options KDB_TRACE
options KDB
options INCLUDE_CONFIG_FILE
options MAC
options AUDIT
options HWPMC_HOOKS
options KBD_INSTALL_CDEV
options PRINTF_BUFR_SIZE=128
options _KPOSIX_PRIORITY_SCHEDULING
options SYSVSEM
options SYSVMSG
options SYSVSHM
options STACK
options KTRACE
options SCSI_DELAY=5000
options COMPAT_FREEBSD7
options COMPAT_FREEBSD32
options GEOM_LABEL
options GEOM_PART_GPT
options NFS_ROOT
options UFS_DIRHASH
options SOFTUPDATES
options FFS
options SCTP
options INET6
options INET
options PREEMPTION
options SCHED_ULE
options NEW_PCIB
options GEOM_PART_MBR
options GEOM_PART_EBR_COMPAT
options GEOM_PART_EBR
options GEOM_PART_BSD
device  isa
device  mem
device  io
device  uart_ns8250
device  acpi
device  pci
device  scbus
device  da
device  cd
device  pass
device  ses
device  atkbdc
device  atkbd
device  psm
device  kbdmux
device  vga
device  splash
device  sc
device  uart
device  loop
device  random
device  ether
device  tun
device  pty
device  md
device  bpf
device  atacore
device  atpic
device  mptable
device  smbios

I'll try GENERIC kernel JFF.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: lowest C-state changes

2012-04-05 Thread Volodymyr Kostyrko

Любомир Григоров wrote:

Hello all, I am using FreeBSD 9.0-STABLE with Konstantin's patch from March
22nd. Everything else is stock. However, after heavy load, or compiling,
C-states go to C1 as lowest. I think once they pass the threshold, they
don't go back.

ThinkPad X220
i5 2520M with integrated Intel video

In /etc/sysctl.conf
dev.cpu.0.cx_lowest=C3
dev.cpu.1.cx_lowest=C3
dev.cpu.2.cx_lowest=C3
dev.cpu.0.cx_lowest=C3

In /etc/rc.conf
powerd_enable=YES
powerd_flags=-a hiadaptive -b adaptive -i 85 -r 60 -p 100

However, once the  cores go to C1, they stay there forever, unless I
manually set them all back.

Any idea on this?



Have you checked http://wiki.freebsd.org/TuningPowerConsumption?

1. For CX states to function correctly you better disable throttling and 
powerd. I also witnessed at least one machine that hitting any CX mode 
stops generate interrupts on APIC clock (I had to boot it with a mousee 
until I disabled APIC clocks).


2. You don't need to set each processor CX value, you only need to set:

hw.acpi.cpu.cx_lowest=C3

All cpu's will inherit default profile.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: lowest C-state changes

2012-04-05 Thread Volodymyr Kostyrko

Любомир Григоров wrote:

  Have you checked http://wiki.freebsd.org/TuningPowerConsumption?
I have. It was kind of confusing and didn't know about:
  1. For CX states to function correctly you better disable throttling
  and powerd. I also witnessed at least one machine that hitting any CX
  mode stops generate interrupts on APIC clock (I had to boot it with a
  mousee until I disabled APIC clocks).
So do you recommend I use throttling or C3? I think C3 runs slightly
cooler. I can't tell since I don't drop under 50C in X. Fan increases at
60C and drops me back.


I wouldn't dare to recommend any particular configuration. Most times 
throttling is safer and with CX states you can get cooler. But both of 
them doesn't play nice together. If you want higher cooling you can try 
to disable throttling (and you will not need powerd as powerd takes care 
of frequencies) and enable CX but you will need to test everything 
thoroughly as unepected bugs can show up. Remember, the default way 
isn't the better one, just the safer one.



  First need to see what state the processor supports the current
  system
 sysctl -a | grep cx_
This is before heavy load while it still remembers the C3:


It's just about ability to set C3 or any other particular state. Some 
processors show only C1 state as available.


For example:

 sysctl hw.model
hw.model: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
 sysctl dev.cpu | grep cx
dev.cpu.0.cx_supported: C1/1
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% last 293us
dev.cpu.1.cx_supported: C1/1
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% last 15us

Setting lower CX on this machine results in:

# sysctl hw.acpi.cpu.cx_lowest=C3
hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument

--
Sphinx of black quartz judge my vow.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: trap 12 on 9.0 when memcache gets some load [resolved] ZERO_COPY trap

2012-03-29 Thread Volodymyr Kostyrko

Andriy Gapon wrote:

on 27/03/2012 18:48 Volodymyr Kostyrko said the following:

Hi all.

I'm just puzzled with this. At first I though this happens because of some 
memory
problems. But now project was moved to another server with some other brands for
motherboard/memory and different cpu's. And still once in an hour this happens 
again:

== screenshot
current_process = 1935 (memcached)
trap number = 12
panic: page fault
cpuid = 2
KDB: stack backtrace:
#0 0x8038ab38 at kdb_backtrace+0x58
#1 0x80358f80 at panic+0x190
#2 0x80567b15 at trap_fatal+0x395
#3 0x80567ce9 at trap_pfault+0x1c9
#4 0x80567536 at trap+0x3a6
#5 0x80552603 at calltrap+0x8
#6 0x803b2c90 at socow_setup+0xd0


I think that zero-copy sockets are not regarded as a reliable feature.
Not an expert, just my two cents.


Disabling zero_zopy seems to work as server still runs after 12 hours. 
Before that one hour was enough to trigger error.


kern.ipc.zero_copy.receive: 0
kern.ipc.zero_copy.send: 0

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


trap 12 on 9.0 when memcache gets some load

2012-03-27 Thread Volodymyr Kostyrko

Hi all.

I'm just puzzled with this. At first I though this happens because of 
some memory problems. But now project was moved to another server with 
some other brands for motherboard/memory and different cpu's. And still 
once in an hour this happens again:


== screenshot
current_process = 1935 (memcached)
trap number = 12
panic: page fault
cpuid = 2
KDB: stack backtrace:
#0 0x8038ab38 at kdb_backtrace+0x58
#1 0x80358f80 at panic+0x190
#2 0x80567b15 at trap_fatal+0x395
#3 0x80567ce9 at trap_pfault+0x1c9
#4 0x80567536 at trap+0x3a6
#5 0x80552603 at calltrap+0x8
#6 0x803b2c90 at socow_setup+0xd0
#7 0x803bc12a at sosend_copyin+0x10a
#8 0x803bc7c6 at sosend_generic+0x4f6
#9 0x803c2028 at kern_sendit+0x1e8
#10 0x803c22a1 at sendit+0xd1
#11 0x803c2331 at sys_sendmsg+0x61
#12 0x805681c5 at amd64_syscall+0x2a5
#13 0x805528eb at Xfast_syscall+0xfb
GEOM_MIRROR: Device beeb0swap: provider mirror/beeb0swap destroyed.
GEOM_MIRROR: Device beeb0swap destroyed.
GEOM_MIRROR: Device kohrah0swap: provider mirror/kohrah0swap destroyed.
GEOM_MIRROR: Device kohrah0swap destroyed.
Uptime: 1d10h46m37s
Dumping 9737 out of 12268 MB:
==

And everything stalls. I have dumpdev_auto set at /etc/rc.conf and 
selected swap device (kohrah0swap) size is 32Gb so it should save dumps 
but it doesn't. Next time i'll try to give it raw volume for dump.


The most curious thing for me is userland app crashing whole kernel. If 
I switch to redis everything works like a charm.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0

2012-03-22 Thread Volodymyr Kostyrko

Andriy Gapon wrote:

on 22/03/2012 15:19 Mike Tkachuk said the following:

kern.eventtimer.periodic: 0


It might make sense to try 1 here.
Also you could attempt to involve mav@ directly - here is an author of the code
and an expert on it.


Better ask before setting as this doubles hpet0 (with HPET) or 
cpu0:timer (with LAPIC) interrupt rate for me.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0

2012-03-22 Thread Volodymyr Kostyrko

Andriy Gapon wrote:

on 22/03/2012 17:33 Volodymyr Kostyrko said the following:

Andriy Gapon wrote:

on 22/03/2012 15:19 Mike Tkachuk said the following:

kern.eventtimer.periodic: 0


It might make sense to try 1 here.
Also you could attempt to involve mav@ directly - here is an author of the code
and an expert on it.


Better ask before setting as this doubles hpet0 (with HPET) or cpu0:timer (with
LAPIC) interrupt rate for me.


Does it make your system unusable?
Are you comparing with pre-eventtimers version of FreeBSD?


In short term - no. Haven't tested it thoroughly. Results are the same 
(double interrupt rate according to `systat 1 -v`) for:

 * i386 and amd64 9-STABLE;
 * amd64 9.0.

As everything related to timing/freq/acpi can be unpredictive I wouldn't 
recommend this to anyone. I own at least two Intel CPU's failing 
somewhere near timing/apic when loading cpufreq and enabling powerd.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0

2012-03-22 Thread Volodymyr Kostyrko

Andriy Gapon wrote:


As everything related to timing/freq/acpi can be unpredictive I wouldn't 
recommend
this to anyone. I own at least two Intel CPU's failing somewhere near 
timing/apic
when loading cpufreq and enabling powerd.

What exactly you wouldn't recommend?
Let's not introduce unrelated topics and vague uncertainties.

Setting kern.eventtimer.periodic to 1 makes eventtimer subsystem to behave less
efficiently but more similar to the pre-eventtimer code.  So this is #1 
suggestion
when people run into some new problems with eventtimers.  Which is what this
thread is about.


I'm sorry, I totally misunderstood the meaning of this tunable. Its 
unclear from man page which value enables or disables periodic code.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


mutex problem: adding address to pf table results in uma_zallog_arg: zone pfrktable

2012-03-21 Thread Volodymyr Kostyrko
Hi all. I have troubles running one server and recompiled kernel with 
DDB/WITNESS. I'll post some LOR's I can find.


This one is highly reproducible as this happens each time sshguard adds 
address to the table.


Mar 21 09:26:07 kohrah sshguard[5196]: Blocking 222.246.132.247:4 for 
945secs: 40 danger in 4 attacks over 45 seconds (all: 80d in 2 abuses 
over 1079s).
Mar 21 09:26:07 kohrah kernel: uma_zalloc_arg: zone pfrktable with the 
following non-sleepable locks held:
Mar 21 09:26:07 kohrah kernel: exclusive sleep mutex pf task mtx (pf 
task mtx) r = 0 (0x81104bf0) locked @ 
/usr/src/sys/modules/pf/../../contrib/pf/net/pf_ioctl.c:1589

Mar 21 09:26:07 kohrah kernel: KDB: stack backtrace:
Mar 21 09:26:07 kohrah kernel: db_trace_self_wrapper() at 
db_trace_self_wrapper+0x2b

Mar 21 09:26:07 kohrah kernel: kdb_backtrace() at kdb_backtrace+0x39
Mar 21 09:26:07 kohrah kernel: witness_warn() at witness_warn+0x434
Mar 21 09:26:07 kohrah kernel: uma_zalloc_arg() at uma_zalloc_arg+0x38
Mar 21 09:26:07 kohrah kernel: pfr_create_ktable() at pfr_create_ktable+0x33
Mar 21 09:26:07 kohrah kernel: pfr_add_addrs() at pfr_add_addrs+0x10b
Mar 21 09:26:07 kohrah kernel: pfioctl() at pfioctl+0x34ad
Mar 21 09:26:07 kohrah kernel: devfs_ioctl_f() at devfs_ioctl_f+0xf2
Mar 21 09:26:07 kohrah kernel: kern_ioctl() at kern_ioctl+0x1aa
Mar 21 09:26:07 kohrah kernel: sys_ioctl() at sys_ioctl+0x146
Mar 21 09:26:07 kohrah kernel: amd64_syscall() at amd64_syscall+0x211
Mar 21 09:26:07 kohrah kernel: Xfast_syscall() at Xfast_syscall+0xfb
Mar 21 09:26:07 kohrah kernel: --- syscall (54, FreeBSD ELF64, 
sys_ioctl), rip = 0x800d9c82c, rsp = 0x7fffcd58, rbp = 
0x7fffd1e0 ---
Mar 21 09:26:07 kohrah kernel: uma_zalloc_arg: zone pfrkentry with the 
following non-sleepable locks held:
Mar 21 09:26:07 kohrah kernel: exclusive sleep mutex pf task mtx (pf 
task mtx) r = 0 (0x81104bf0) locked @ 
/usr/src/sys/modules/pf/../../contrib/pf/net/pf_table.c:75

Mar 21 09:26:07 kohrah kernel: KDB: stack backtrace:
Mar 21 09:26:07 kohrah kernel: db_trace_self_wrapper() at 
db_trace_self_wrapper+0x2b

Mar 21 09:26:07 kohrah kernel: kdb_backtrace() at kdb_backtrace+0x39
Mar 21 09:26:07 kohrah kernel: witness_warn() at witness_warn+0x434
Mar 21 09:26:07 kohrah kernel: uma_zalloc_arg() at uma_zalloc_arg+0x38
Mar 21 09:26:07 kohrah kernel: pfr_add_addrs() at pfr_add_addrs+0x37c
Mar 21 09:26:07 kohrah kernel: pfioctl() at pfioctl+0x34ad
Mar 21 09:26:07 kohrah kernel: devfs_ioctl_f() at devfs_ioctl_f+0xf2
Mar 21 09:26:07 kohrah kernel: kern_ioctl() at kern_ioctl+0x1aa
Mar 21 09:26:07 kohrah kernel: sys_ioctl() at sys_ioctl+0x146
Mar 21 09:26:07 kohrah kernel: amd64_syscall() at amd64_syscall+0x211
Mar 21 09:26:07 kohrah kernel: Xfast_syscall() at Xfast_syscall+0xfb
Mar 21 09:26:07 kohrah kernel: --- syscall (54, FreeBSD ELF64, 
sys_ioctl), rip = 0x800d9c82c, rsp = 0x7fffcd58, rbp = 
0x7fffd1e0 ---


Sample config:

Install security/sshguard-pf.

== /etc/pf.conf
table sshguard persist
==

== /etc/syslog.conf
auth.info;authpriv.info |exec /usr/local/sbin/sshguard
==

Try to ssh to the box typing garbage as password, after 4 fails client 
address is temporarily banned and pushed to the table.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: mutex problem: adding address to pf table results in uma_zallog_arg: zone pfrktable

2012-03-21 Thread Volodymyr Kostyrko

Volodymyr Kostyrko wrote:

Hi all. I have troubles running one server and recompiled kernel with
DDB/WITNESS. I'll post some LOR's I can find.


Sorry, forgot to describe machine:

FreeBSD kohrah.xim.bz 9.0-RELEASE FreeBSD 9.0-RELEASE #0 r229375: Tue 
Mar 20 17:48:58 EET 2012 
arc...@kohrah.xim.bz:/usr/obj/usr/src/sys/MINIMAL  amd64


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Reducing the need to compile a custom kernel

2012-02-13 Thread Volodymyr Kostyrko

Jeremy Chadwick wrote:

I want to note here: the pf ALTQ options are a pain in the butt, quite
honestly.  I've found in the past that removing the ones you don't use
won't result in a successful build, thus one must include them all.  We
do need ALTQ support though, for rate-limiting capability.  The NOPCC
option is needed for SMP builds, which makes me wonder what the state of
SMP is in this regard -- meaning, on non-SMP builds, is it still safe
to include ALTQ_NOPCC?


It seems like I'm missing something. What is good about using non-SMP 
kernel?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Reducing the need to compile a custom kernel

2012-02-13 Thread Volodymyr Kostyrko

Jeremy Chadwick wrote:

On Mon, Feb 13, 2012 at 05:05:41PM +0200, Volodymyr Kostyrko wrote:

Jeremy Chadwick wrote:

I want to note here: the pf ALTQ options are a pain in the butt, quite
honestly.  I've found in the past that removing the ones you don't use
won't result in a successful build, thus one must include them all.  We
do need ALTQ support though, for rate-limiting capability.  The NOPCC
option is needed for SMP builds, which makes me wonder what the state of
SMP is in this regard -- meaning, on non-SMP builds, is it still safe
to include ALTQ_NOPCC?


It seems like I'm missing something. What is good about using
non-SMP kernel?


Nothing.  It's a question of whether or not use of ALTQ_NOPCC causes
breakage on non-SMP kernels, or if FreeBSD even bothers to support
non-SMP at this point.  Non-SMP means without options SMP.


You got my point. I'm a single core user today but I run SMP-enabled kernel.


Rephrased: if SMP is the default, and options SMP works just fine on
systems without multiple processors/cores, then the ALTQ_NOPCC option
should probably be removed.


Yep, works for me. However I had found some cruft about extra processing 
power which would be used in expense of correct work. Can this be 
something like IPFIREWALL_FORWARD that adds some latency to most cases 
providing some use only for chosen ones?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Reducing the need to compile a custom kernel

2012-02-13 Thread Volodymyr Kostyrko

Alexander Leidinger wrote:

Feasible: depend upon your definition of feasible. You would have to
add all keymaps statically into the kernel. No idea which parts exactly
we talk about, but:
---snip---
% du -h /usr/share/syscons/
40k /usr/share/syscons/scrnmaps
570k /usr/share/syscons/fonts
1.1M /usr/share/syscons/keymaps
1.8M /usr/share/syscons/
---snip---

I wouldn't mind for 40k, but 1.8M looks more like the value to calculate
with. Anyway, this is out of the scope of the original question.


Correct me if I'm wrong but zfs already fetches plain file 
/boot/zfs/zpool.cache on load. Can't this be:


 1. Postponed to later processing.
 2. After filesystems are mounted the keymap is loaded.

Or even:

 1. Put all viable files on the / partition.
 2. Select and load correct one before kernel is fired.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Reducing the need to compile a custom kernel

2012-02-10 Thread Volodymyr Kostyrko

Alexander Leidinger wrote:

during some big discussions in the last monts on various lists, one of
the problems was that some people would like to use freebsd-update but
can't as they are using a custom kernel. With all the kernel modules we
provide, the need for a custom kernel should be small, but on the other
hand, we do not provide a small kernel-skeleton where you can load just
the modules you need.

This should be easy to change. As a first step I took the generic kernel
and removed all devices which are available as modules, e.g. the USB
section consists now only of the USB_DEBUG option (so that the module is
build like with the current generic kernel). I also removed some storage
drivers which are not available as a module. The rationale is, that I
can not remove CAM from the kernel config if I let those drivers inside
(if those drivers are important enough, someone will probably fix the
problem and add the missing pieces to generate a module).

Such a kernel would cover situations where people compile their own
kernel because they want to get rid of some unused kernel code (and
maybe even need the memory this frees up).

The question is, is this enough? Or asked differently, why are you
compiling a custom kernel in a production environment (so I rule out
debug options zhich are not enabled in GENERIC)? Are there options which
you add which you can not add as a module (SW_WATCHDOG comes to my
mind)? If yes, which ones and how important are they for you?


The list would be too long for  me, that's a sample what I add to my 
MINIMAL after stripping GENERIC:


option DEVICE_POLLING
option BPF_JITTER
option DIRECTIO

option SC_ALT_MOUSE_IMAGE
option SC_MOUSE_CHAR=0x3

option ZERO_COPY_SOCKETS

option SW_WATCHDOG

option ALTQ
option ALTQ_CBQ
option ALTQ_RED
option ALTQ_RIO
option ALTQ_HFSC
option ALTQ_CDNR
option ALTQ_PRIQ
option ALTQ_NOPCC

device atpic
device mptable

I even don't use them on most machines however I prefer to build all 
machines from one kernel config however even this is impossible because 
for example I can't select scheduler by modules.


Some point can be superseded in future for example current work on ULE 
seems promising.


For example, why there are no modules for atpic and mptable? I don't 
need them on most machines but I can't load them at boot time.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Strange 'hangs' with RELENG_9

2012-01-19 Thread Volodymyr Kostyrko

László KÁROLYI wrote:

Hello,

Recently I updated my RELENG_8 to RELENG_9. Since then, the server hangs
from time to time for 5 minutes. When I run a top in a remote terminal,
I can see that it hangs so strong, that the clock hangs too. When it
continues to run , the time continues from the when it 'hanged'. TCP
connections are also dropped with timeout at that time. However, no
kernel panic, and i can't see anything in the dmesg log too.


Obtaining kernel dump is the way to go. You can occasionally find that 
obtaining dump on world built with clang is much easier than on 
gcc-compiled one. I remember at least one such case with broken zfs 
directory when trying to read such directory result in process with no 
state on gcc-compiled world and result in imminent panic in zfs code on 
clang-compiled world. Remember to set dumpdev to something appropriate.



/boot/loader.conf:
zfs_load=YES
vfs.root.mountfrom=zfs:pool/root
vfs.zfs.vdev.max_pending=8
geom_raid_load=YES
hint.siisch.0.sata_rev=1
hint.siisch.1.sata_rev=1

/etc/sysctl.conf:
vfs.zfs.l2arc_noprefetch=0


This has impact on performance. You sure you really need that one? Can 
you try without it?



/etc/make.conf, the kernel was compiled with this settings:
CPUTYPE?=athlon64


Compiling with clang you better turn that thing off.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Strange 'hangs' with RELENG_9

2012-01-19 Thread Volodymyr Kostyrko

László KÁROLYI wrote:


Volodymyr Kostyrko wrote:


Obtaining kernel dump is the way to go. You can occasionally find that
obtaining dump on world built with clang is much easier than on
gcc-compiled one. I remember at least one such case with broken zfs
directory when trying to read such directory result in process with no
state on gcc-compiled world and result in imminent panic in zfs code
on clang-compiled world. Remember to set dumpdev to something
appropriate.


I'm not near to the server for putting any dumpdevice in (if you meant
that way), and also, there's no kernel panic but just at the end of the
reboot process, and not all the time.


I mean setting dumpdev=auto in /etc/rc.conf so the kernel can dump to 
any available device such as swap partition.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: FB9-stable: bridge0 doesn't come up via rc

2012-01-17 Thread Volodymyr Kostyrko

Denny Schierz wrote:

hi,

I have problems starting the bridge via rc.d:

rc.conf:

cloned_interfaces=bridge0
ifconfig_bge0=up
ifconfig_bridge0=addm bge0 up
ifconfig_bridge0=inet 192.168.1.0 netmask 255.255.255.0 up


Remember that rc.conf is a pure shell script. The line above overwrites 
one with addm bge0 up.



defaultrouter=192.168.1.254
gateway_enable=YES

It doesn't work. After reboot I have to set up:

ifconfig bridge0 addm bge0

then it works.


Use igconfig_bridge0_alias0.


Also a problem: /etc/rc.d/netif stop doesn't destroy bridge0 and /etc/rc.d/netif 
start gives errors, because bridge exists already.

any suggestions?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: FreeBSD 9 recompile ports

2012-01-13 Thread Volodymyr Kostyrko

George Kontostanos wrote:

Greetings all and my apologies for cross posting!

There seems to be a confusion regarding the ABI change in FreeBSD 9
and if this affects the usual upgrade path which includes a full port
rebuild.

The relevant post is here: http://forums.freebsd.org/showthread.php?t=28831

Frankly, I am also confused because I remember a relevant discussion a
few months ago in the lists. Traditionally a major RELEASE upgrade
requires a full ports rebuild, however this time there is no
COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be
working fine. On the other hand this is stated in UPDATING:

20110828:
 Bump the shared library version numbers for libraries that
 do not use symbol versioning, have changed the ABI compared
 to stable/8 and which shared library version was not bumped.
 Done as part of 9.0-RELEASE cycle.

Your input would be appreciated!


Why can't it be that only shared libraries should be bumped, but no 
kernel incompatible changes were introduced?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: x11/nvidia-driver: crash with FreeBSD 9.0-STABLE/amd64 when module loaded via /boot/loader.conf

2012-01-03 Thread Volodymyr Kostyrko

03.01.2012 12:15, O. Hartmann wrote:

On one of my FreeBSD 9.0 boxes running FreeBSD 9.0-STABLE/amd64 (CLANG
built), equipted with a nVidia GT760Ti graphics board, loading the
nvidia module via /boot/loader.conf results in a page fault with random
error messages before rebooting.


9-STABLE, amd64, clang world and ports, GeForce 8500 GT - works like a 
charm for me.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: minor regression after patching

2011-12-28 Thread Volodymyr Kostyrko

28.12.2011 02:03, Dimitry Andric wrote:

.if (empty(.CURDIR:N*/usr/src/*) || empty(.CURDIR:N*/usr/obj/*))
!defined(NOCCACHE)


The problem is this test, it doesn't return true when you are exactly in
/usr/src. The result is that clang doesn't get built in the cross-tools
stage, and /usr/bin/clang is used instead for the rest of the world.


Oops, I messed up whole thing again. Thank you very much.

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: minor regression after patching

2011-12-27 Thread Volodymyr Kostyrko

27.12.2011 03:58, Dimitry Andric wrote:

ftpd.o: In function `pass':
/usr/src/libexec/ftpd/ftpd.c:(.text+0x2676): undefined reference to
`__FreeBSD_libc_enter_restricted_mode'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
*** Error code 1


This means that linker has not found a mentioned symbol, i.e. likely
you haven't updated your libc before trying to build ftpd.
In this case you need to act the next order:
1) rebuild reinstall libc
2) rebuild reinstall ftpd


Oh yes, I just remembered those sweet days I was sitting on HEAD. Each
build was a trial/error process.

And I'm not seeing this when compiling world with stock gcc or on i386.
It looks like rather nasty clang regression.


For me, stable/9 builds just fine with clang (or gcc), and the tinderbox
isn't complaining either. Are you sure you are running buildworld,
which is definitely necessary for this kind of upgrade?


Yes. I have set up a chrooted environment to retest. Config files are:

=== /etc/make.conf
# vim:set ft=make:

#CPUTYPE?=native
INSTALL:=install -C
KERNCONF?=MINIMAL
NO_CLEAN:=yes
WITHOUT_NOUVEAU:=yes
WRKDIRPREFIX=/tmp/ports

.if (empty(.CURDIR:N*/usr/src/*) || empty(.CURDIR:N*/usr/obj/*))  
!defined(NOCCACHE)

.  if !empty(TARGET:Mamd64)
  #CC=/usr/local/libexec/ccache/world-cc
  #CXX=/usr/local/libexec/ccache/world-c++
  CC:=${CC:C,^cc$,clang,1}
  CXX:=${CXX:C,^c\+\+$,clang++,1}
  CPP:=${CPP:C,^cpp$,clang -E,}
  NO_WERROR:=
  WERROR:=
.  else
  #CC=/usr/local/libexec/ccache/world/cc
  #CXX=/usr/local/libexec/ccache/world/c++
.  endif
.endif


=== /etc/src.conf
WITHOUT_ACCT='yes'
#WITHOUT_AMD='yes'
WITHOUT_ATM='yes'
WITHOUT_AUTHPF='yes'
#WITHOUT_BIND='yes'
WITHOUT_CTM='yes'
WITHOUT_FREEBSD_UPDATE='yes'
WITHOUT_HTML='yes'
WITHOUT_I4B='yes'
#WITHOUT_INFO='yes'
WITHOUT_IPFILTER='yes'
WITHOUT_IPFW='yes'
WITHOUT_IPX='yes'
#WITHOUT_JAIL='yes'
#WITHOUT_KERBEROS='yes'
WITHOUT_NDIS='yes'
#WITHOUT_NIS='yes'
WITHOUT_PMC='yes'
WITHOUT_PORTSNAP='yes'
#WITHOUT_PPP='yes'
WITHOUT_PROFILE='yes'
WITHOUT_QUOTAS='yes'
WITHOUT_RCMDS='yes'
#WITHOUT_RCS='yes'
WITHOUT_ROUTED='yes'
WITHOUT_SENDMAIL='yes'
WITHOUT_SLIP='yes'
WITHOUT_SYSINSTALL='yes'
WITHOUT_WIRELESS='yes'


No other changes was done to environment. Build was started with:

idprio 15 make -j2 buildworld

Also I found that there are files missing after successful buildworld so 
installworld fails at some points. Subsequent run of buildworld fixes that.


I'll start a new build from a scratch with one single job to catch all 
output.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: minor regression after patching

2011-12-27 Thread Volodymyr Kostyrko

27.12.2011 03:58, Dimitry Andric wrote:

ftpd.o: In function `pass':
/usr/src/libexec/ftpd/ftpd.c:(.text+0x2676): undefined reference to
`__FreeBSD_libc_enter_restricted_mode'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
*** Error code 1


This means that linker has not found a mentioned symbol, i.e. likely
you haven't updated your libc before trying to build ftpd.
In this case you need to act the next order:
1) rebuild reinstall libc
2) rebuild reinstall ftpd


Oh yes, I just remembered those sweet days I was sitting on HEAD. Each
build was a trial/error process.

And I'm not seeing this when compiling world with stock gcc or on i386.
It looks like rather nasty clang regression.


For me, stable/9 builds just fine with clang (or gcc), and the tinderbox
isn't complaining either. Are you sure you are running buildworld,
which is definitely necessary for this kind of upgrade?


=== libexec/ftpd (all)
clang -O2 -pipe  -DSETPROCTITLE -DLOGIN_CAP -DVIRTUAL_HOSTING 
-I/usr/src/libexec/ftpd -Dmain=ls_main 
-I/usr/src/libexec/ftpd/../../bin/ls -DINET6 -DUSE_PAM -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k 
-Wno-uninitialized -Wno-pointer-sign -c /usr/src/libexec/ftpd/ftpd.c
/usr/src/libexec/ftpd/ftpd.c:1565:3: warning: implicit declaration of 
function '__FreeBSD_libc_enter_restricted_mode' is invalid in C99 
[-Wimplicit-function-declaration]

__FreeBSD_libc_enter_restricted_mode();
^
1 warning generated.

I totally missed this warning when reporting the problem first time.

Version.map for libc contains this function:

FBSD_1.3 {
global:
__FreeBSD_libc_enter_restricted_mode;
} FBSD_1.2;

So the question is mainly about why 
/usr/obj/usr/src/tmp/usr/include/unistd.h was ignored in favor of 
installed one?


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


minor regression after patching

2011-12-26 Thread Volodymyr Kostyrko

Hi all.

Am I the only one seeing this on RELENG_9?

=== libexec/ftpd (all)
clang -O2 -pipe  -DSETPROCTITLE -DLOGIN_CAP -DVIRTUAL_HOSTING 
-I/usr/src/libexec/ftpd -Dmain=ls_main 
-I/usr/src/libexec/ftpd/../../bin/ls -DINET6 -DUSE_PAM -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k 
-Wno-uninitialized -Wno-pointer-sign  -o ftpd ftpd.o ftpcmd.o logwtmp.o 
popen.o ls.o cmp.o print.o util.o -lutil -lcrypt -lopie -lmd -lm -lpam

clang: warning: argument unused during compilation: '-std=gnu99'
ftpd.o: In function `pass':
/usr/src/libexec/ftpd/ftpd.c:(.text+0x2676): undefined reference to 
`__FreeBSD_libc_enter_restricted_mode'
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)

*** Error code 1

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: minor regression after patching

2011-12-26 Thread Volodymyr Kostyrko

26.12.2011 17:57, Sergey Kandaurov wrote:

Hi all.

Am I the only one seeing this on RELENG_9?

===  libexec/ftpd (all)
clang -O2 -pipe  -DSETPROCTITLE -DLOGIN_CAP -DVIRTUAL_HOSTING
-I/usr/src/libexec/ftpd -Dmain=ls_main -I/usr/src/libexec/ftpd/../../bin/ls
-DINET6 -DUSE_PAM -std=gnu99 -fstack-protector -Wsystem-headers -Wall
-Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign  -o ftpd ftpd.o
ftpcmd.o logwtmp.o popen.o ls.o cmp.o print.o util.o -lutil -lcrypt -lopie
-lmd -lm -lpam
clang: warning: argument unused during compilation: '-std=gnu99'
ftpd.o: In function `pass':
/usr/src/libexec/ftpd/ftpd.c:(.text+0x2676): undefined reference to
`__FreeBSD_libc_enter_restricted_mode'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
*** Error code 1


This means that linker has not found a mentioned symbol, i.e. likely
you haven't updated your libc before trying to build ftpd.
In this case you need to act the next order:
1) rebuild  reinstall libc
2) rebuild  reinstall ftpd


Oh yes, I just remembered those sweet days I was sitting on HEAD. Each 
build was a trial/error process.


And I'm not seeing this when compiling world with stock gcc or on i386. 
It looks like rather nasty clang regression.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server

2011-12-15 Thread Volodymyr Kostyrko

15.12.2011 15:48, Jeremy Chadwick wrote:

I'm getting to the point where I'm considering formulating a private
mail to Jeff Roberson, requesting that he be aware of the discussion
that's happening (not that he necessarily follow or read it), and that
based on what I can tell we're at a roadblock -- nobody so far is
absolutely certain how to benchmark and compare ULE vs. 4BSD in
multiple ways, so that those of us involved here can run such utilities
and provide the data somewhere central for devs to review.  I only
mention this because so far I haven't seen anyone really say okay, this
is what we should be using for these kinds of tests.  Yay nature of the
beast.


I'll try to summarize and propose a test scenario. I don't know whether 
this helps or not.


We should have two different task types for this one. The first would be 
Super Affine tasks. They should use few to none syscalls, use medium 
math, have low memory footprint. No syscalls means this tasks will never 
stop for memory/disk or other activity so each time the queue is looked 
upon this task will be ready to run. Medium math means this shouldn't be 
just a simple big loop so that processor will really compute something 
with this data. Low memory footprint means this task can reside with 
data on CPU L1 cache for eons. I'm not sure about branch prediction, 
should it be distorted or not...


The other task type would be Worker. It doesn't matter what it does but 
it agressively uses syscalls like working with files/directories.


There should be at least one SA-task per core and at least 10 (?) 
W-tasks per core.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: SCHED_ULE should not be the default

2011-12-09 Thread Volodymyr Kostyrko

09.12.2011 13:03, George Mitchell wrote:

dnetc is an open-source program from http://www.distributed.net/. It
tries a brute-force approach to cracking RC4 puzzles and also computes
optimal Golomb rulers. It starts up one process per CPU and runs at
nice 20 and is, for all intents and purposes, 100% compute bound.


nice 20 doesn't mean it should give time to just any other program. Have 
you tried setting dnetc_idprio?



Not everybody runs this sort of program, but there are plenty of
similar projects out there, and people who try to participate in
them will be mightily displeased with their FreeBSD systems when
they do. Is there some case where SCHED_ULE exhibits significantly
better performance than SCHED_4BSD? If not, I think SCHED-4BSD
should remain the default GENERIC configuration until this is fixed.


Not fully right, boinc defaults to run on idprio 31 so this isn't an 
issue. And yes, there are cases where SCHED_ULE shows much better 
performance then SCHED_4BSD. You incidentally found rare misbehavior of 
SCHED_ULE and I think this would be treated.


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


stable fails to build for me

2011-11-14 Thread Volodymyr Kostyrko

I'm running into this:

=== gnu/lib/libsupc++ (install)
clang -O2 -pipe  -std=gnu99 -fstack-protector -Wsystem-headers -Wall 
-Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c 
/usr/src/usr.bin/lex/lib/libyywrap.c
install -C -C -o root -g wheel -m 444   libsupc++.a 
/usr/obj/usr/src/tmp/usr/lib
/usr/src/lib/libgpib/ibfoo.c:37:10: fatal error: 'dev/ieee488/ugpib.h' 
file not found

#include dev/ieee488/ugpib.h
 ^
1 error generated.
mkdep: compile failed

/etc/src.conf:
WITHOUT_ACCT='yes'
WITHOUT_ATM='yes'
WITHOUT_AUTHPF='yes'
WITHOUT_CTM='yes'
WITHOUT_FREEBSD_UPDATE='yes'
WITHOUT_HTML='yes'
WITHOUT_I4B='yes'
WITHOUT_IPFILTER='yes'
WITHOUT_IPFW='yes'
WITHOUT_IPX='yes'
WITHOUT_NDIS='yes'
WITHOUT_PMC='yes'
WITHOUT_PORTSNAP='yes'
WITHOUT_PROFILE='yes'
WITHOUT_QUOTAS='yes'
WITHOUT_RCMDS='yes'
WITHOUT_RCS='yes'
WITHOUT_ROUTED='yes'
WITHOUT_SENDMAIL='yes'
WITHOUT_SLIP='yes'
WITHOUT_SYSINSTALL='yes'
WITHOUT_WIRELESS='yes'

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: stable fails to build for me [bad setup]

2011-11-14 Thread Volodymyr Kostyrko

14.11.2011 10:06, Volodymyr Kostyrko wrote:

I'm running into this:

=== gnu/lib/libsupc++ (install)
clang -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Wall
-Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/usr.bin/lex/lib/libyywrap.c
install -C -C -o root -g wheel -m 444 libsupc++.a
/usr/obj/usr/src/tmp/usr/lib
/usr/src/lib/libgpib/ibfoo.c:37:10: fatal error: 'dev/ieee488/ugpib.h'
file not found
#include dev/ieee488/ugpib.h
^
1 error generated.
mkdep: compile failed

/etc/src.conf:
WITHOUT_ACCT='yes'
WITHOUT_ATM='yes'
WITHOUT_AUTHPF='yes'
WITHOUT_CTM='yes'
WITHOUT_FREEBSD_UPDATE='yes'
WITHOUT_HTML='yes'
WITHOUT_I4B='yes'
WITHOUT_IPFILTER='yes'
WITHOUT_IPFW='yes'
WITHOUT_IPX='yes'
WITHOUT_NDIS='yes'
WITHOUT_PMC='yes'
WITHOUT_PORTSNAP='yes'
WITHOUT_PROFILE='yes'
WITHOUT_QUOTAS='yes'
WITHOUT_RCMDS='yes'
WITHOUT_RCS='yes'
WITHOUT_ROUTED='yes'
WITHOUT_SENDMAIL='yes'
WITHOUT_SLIP='yes'
WITHOUT_SYSINSTALL='yes'
WITHOUT_WIRELESS='yes'



I'm sorry, for some unknown reason the host lacks /usr/include/dev 
directory...


--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: xterm - truetype fonts and missing underscore

2011-08-24 Thread Volodymyr Kostyrko

24.08.2011 12:01, Tony Maher wrote:

Hello,

recently (not sure exactly when) my xterms no longer showed the
underscore character.
In my .Xresources I had (and have had this setting for years):

XTerm*faceName: Monospace
XTerm*faceSize: 10

I noticed when experimenting and modifying values that for one choice
the bottom part of letters like 'g' was missing.
So changed faceSize to 11 and all is good.

In gnome-terminal with Monospace/10 font underscores showed up fine
(and was ok in gnome font selector). So it appears to be xterm specific.

Has anyone else experienced this?


+1 from me

http://lists.nongnu.org/archive/html/freetype/2011-08/msg00020.html

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: HEADS UP: ZFS v28 merged to 8-STABLE

2011-06-10 Thread Volodymyr Kostyrko

06.06.2011 13:53, Martin Matuska написав(ла):

Hi,

I have merged ZFS version 28 to 8-STABLE (revision 222741)

New major features:

- data deduplication


Am I missing something? How about using fletcher[24] for dedup?

--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


  1   2   >