Ben Morrow | 3 Apr 23:28 2014

Re: [ANNOUNCE] ports 2014Q2 branched

Quoth Baptiste Daroussin <bapt <at>>:
> January 2014 saw the release of the first quaterly branch, intended at
> providing a stable and high-quality ports tree. Those stable branches
> are a snapshot of the head ports tree taken every 3 months and
> currently supported for three months, during which they receive
> security fixes as well as build and runtime fixes.

This is really good news.

I don't know who is in charge of the ports mirror on github, but if it
would be possible to mirror these branches as well that would be really
helpful. I switched to using git for my ports tree a while ago, because
I have some local modifications and I find it much easier to maintain
them in git than to fight with svn.


freebsd-stable <at> mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at>"

Baptiste Daroussin | 2 Apr 11:24 2014

[ANNOUNCE] ports 2014Q2 branched

Hi all,

I am pleased to announce that we have created the 2014Q2 branch of the ports

Because the first 2014Q1 branch was experimental you might not have heard of it

January 2014 saw the release of the first quaterly branch, intended at
providing a stable and high-quality ports tree. Those stable branches are a
snapshot of the head ports tree taken every 3 months and currently supported
for three months, during which they receive security fixes as well as build and
runtime fixes.

Packages are built on regular basis on that branch (weekly) and published as
usual via (/quarterly instead of the usual /latest).

They are signed the same way the /latest branch is.

While packages for 2014Q1 were only built for 10 (i386 and amd64) 2014Q2 will be
built for both FreeBSD 9 and 10 (i386 and amd64).

The first build of 2014Q2 will started this morning (wednesday at 1 am UTC) and should
hit your closest mirrors very soon.

On behalf of the port management team
Cassidy Larson | 1 Apr 17:35 2014

FS hang with suspfs

I have a backend mail server that seems to hang randomly with suspfs
states. Requires a power cycle because it never properly shuts down.
Sometimes it happens during the day, others at night.  Typically it will go
for ~3 weeks before it does it again.

Running FreeBSD 9.2-RELEASE-p1  (amd64)

I have a LSI SAS2308 (mps driver) for 8 SAS drives in a ZFS raidz2 for mail
data, and a LSI 9260-4i (mfi driver) with four SSDs (2xmirrored UFS for OS,
2x mirrored UFS for dovecot indexes).
The dovecot processes get stuck in a suspfs state, and keep adding up,
never being removed.  Killing them does nothing, and even a reboot will end
up hanging after syncing buffers but not finishing.. and the end course is
a hard power cycle.

I've seen this same suspfs lock-up on another 9.2-release box with four
drives in a RAID-10 UFS using a 3ware 9750-4i (tws driver) before, although
not as common as the one above.

I read past posts and noticed an issue like this when creating a snapshot
on a UFS+GJOURNAL setup, but I'm not doing any snapshots. The box today is
just doing simple mailbox checking and mail delivery but for a large number
of users.

Anybody have any ideas or suggestions? I would be immensely grateful.


(Continue reading)

jason-freebsd-stable | 1 Apr 01:20 2014

Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE?

I'm having the same problem.

Was running FreeBSD-9 for a long time with an msk card, no problems or 
issues.  Upgraded to 10-RELEASE and now my card reliably hangs after 
passing a total of about 2M of traffic.

I'm running amd64 with 2G of RAM.

I can provide the exact card ID later if it helps.

I tried modifying msk_stat_count as suggested by Curtis (both my modifying 
MSK_TX_RING_CNT/MSK_RX_RING_CNT as he did, as well as by setting it 
directly to 1k or 2k in if_msk.c), but that didn't help.  With each of 
these changes, after a reboot, the card will reliably pass about 2Mbyte of 
traffic and then hang (tried multiple reboots and power-cycles with each 

Has anyone else made any progress on this issue yet?

Has anyone tried just rolling back sys/dev/msk to the version from 



freebsd-stable <at> mailing list
(Continue reading)

Chris H | 31 Mar 22:06 2014

Process handlers, and zombies, or preap(1)

 I'm evaluating/experimenting on releng_9. The install, and now
custom kernel have noting exotic, or anything out of the ordinary.
top(1), and ps(1) indicate a (1) zombie, or <defunct> process. On
my releng_8 systems, when I occasionally encounter one of these,
they soon disappear (are reaped) from the process table. While I
have not investigated this far enough on both versions to determine
whether the parent process reaped the child on the releng_8 systems,
and the parent on releng_9 is simply an irresponsible parent, eg;
a different parent. Before I do, I was wondering if there was any
specific difference between the 2 versions that might cause better
handling of such situations. While I recognize that resource
starvation is HIGHLY unlikely, except by perhaps a rouge parent
spawning multitudes of zombies. I thought it might be useful for
"housekeeping" to 1) provide a process table housekeeper (zombie
reaper), or 2) create a system utility/command like SunOS/OpenSolaris
has; preap(1).

Thank you for your time, and consideration.


freebsd-stable <at> mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at>"

(Continue reading)

Harald Schmalzbauer | 31 Mar 09:44 2014

device ada n/ in kernconf, how to omitt for hv_storvsc.ko


I'm experimenting with MS-Hyper-V and saw that as soon as hv_storvsc.ko
is loaded, an IDE hdd attaches as 'da' _and_ 'ada' (the former seems to
be called “FastIDE” on “synthetic storage driver” and gains efficiency
for HDD workloads).

There's the hv_pci_ata_disengage.ko pseudo driver, but that also makes
IDE cdrom unavailable – same as disabling ata/atapci! Can't really get
the idea of that module…

I'd prefere to disable 'ada' only (leaving cdrom via atapci->ATA_CAM->cd).
But I can't find the place where “device ada” gets defined for kernel
conf. “device ata” is in GENERIC, along with da, sa, scbus etc., but no
'ada' ?!?. No trace of 'ada' in DEFAULTS either!?!

Is there something like hint.ada.disable=1 ?
Can I use “nodevice ada“ to exclude it from my custom kernel?



chrish | 30 Mar 22:12 2014

miibus0: mii_mediachg: can't handle non-zero PHY instance 31

 I'm not sure whether this best belonged on net <at> , or stable <at> 
so I'm using both. :)
I'm testing both releng_9, and MB, and I encountered a new
message I don't usually see using the nfe(4) driver:

miibus0: mii_mediachg: can't handle non-zero PHY instance 1
miibus0: mii_mediachg: can't handle non-zero PHY instance 31

Truncated for brevity (31 lines in total; 1-31). I don't know
how interpret this. An issue with my version of the driver, or
the hardware itself? This occurred with both GENERIC, as well
as my custom kernel.

# uname -a
FreeBSD demon0 9.2-STABLE FreeBSD 9.2-STABLE #0 r263756: Wed Mar 26 11:28:10 PDT 2014    
root <at> demon0:/usr/obj/usr/src/sys/DEMON0  amd64

Thank you for all your time, and consideration.


freebsd-stable <at> mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at>"

Levon Angaladyan | 30 Mar 16:12 2014

The most important thing.

"Now this is
eternal life: that they may know you, the only true God, and Jesus
Christ, whom you have sent" (John 17:3). 
"For it is by
grace that you have been saved, through faith. This does not depend
on anything you have achieved, it is the free gift of God; and
because it is not earned no one can boast about it." (Ephesians

Receiving Christ
involves turning to God from self (a spirit of repentance) and
trusting Christ to come into our lives to forgive us of our sins and
make us what he wants us to be. Just to agree intellectually that
Jesus Christ is the Son of God and that he died on the cross for our
sins is not enough. Nor is it enough to have an emotional experience.
We receive Jesus Christ by faith, as an act of our will.

freebsd-stable <at> mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at>"
Chris H | 30 Mar 03:37 2014

where's the full copy of dmesg(8)?

 I'm testing on 9.2-STABLE, and was experimenting on an AMD sempron
(140). Booting from the boot-only, or DVD-1 DVD's doesn't emit the
entire dmesg(8) output. Building, and installing a custom kernel also
didn't provide the full dmesg(8) output.
Specifically; it omits the top N lines (N = as yet, undetermined Number).
I have no idea why, or how to correct this. I'm pretty confident
the processor, and motherboard (MSI) are not too new for FreeBSD.
Example (dmesg) output:

pci_link8: Picked IRQ 21 with weight 0
pcib0: slot 2 INTA routed to irq 21 via \134_SB_.LUB0
ohci early: SMM active, request owner change
found->	vendor=0x10de, dev=0x03f2, revid=0xa3
	domain=0, bus=0, slot=2, func=1
	class=0c-03-20, hdrtype=0x00, mfdev=1
	cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns)
	intpin=b, irq=11
	powerspec 2  supports D0 D1 D2 D3  current D0
	map[10]: type Memory, range 32, base 0xdff7ec00, size  8, enabled

that's from /var/run/dmesg.boot. /var/log/messages gives me no more than
dmesg(8) does. Interestingly, misc/cpuid returns:

 eax in    eax      ebx      ecx      edx
00000000 00000005 68747541 444d4163 69746e65
00000001 00100f62 00010800 00802009 078bfbff
00000002 00000000 00000000 00000000 00000000
00000003 00000000 00000000 00000000 00000000
(Continue reading)

Troyax | 28 Mar 17:00 2014

Freebsd 10 install kernel not booting.


I would like to move to Freebsd 10, but the USB install kernel doesnot boot on my laptop (HP EliteBook Folio
9470m); I have send a PR, number 187488 ( ).

freebsd-stable <at> mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at>"

Dmitry Sivachenko | 26 Mar 20:28 2014

10/stable lldb build failure


I have the following FreeBSD version:
10.0-STABLE FreeBSD 10.0-STABLE #0 r263422: Thu Mar 20 17:24:32 MSK 2014

I try to build:
URL: svn://
Relative URL: ^/stable/10
Repository Root: svn://
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 263769
Node Kind: directory
Schedule: normal
Last Changed Author: dim
Last Changed Rev: 263765
Last Changed Date: 2014-03-26 11:42:43 +0400 (Wed, 26 Mar 2014)

my src.conf:


c++  -O2 -pipe -O2 -fno-strict-aliasing -pipe
-I/opt/WRK/src/usr.bin/clang/lldb/../../../contrib/llvm/tools/lldb/include -I/opt/WRK/src/usr.bin/clang/lldb/../../../contrib/llvm/i
nclude -I/opt/WRK/src/usr.bin/clang/lldb/../../../contrib/llvm/tools/clang/include
-I/opt/WRK/src/usr.bin/clang/lldb/../../../contrib/llvm/tools/lldb/tools/driver -I. -I/opt/WRK/
src/usr.bin/clang/lldb/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX
(Continue reading)