Neal Nelson | 15 Sep 17:50 2014

FreeBSD 10.1 BETA 1 on MacBook

Hi all.

I've been trying to install FreeBSD 10.1 BETA1 on a MacBook Pro as part
of a dual boot environment. I used to be able to install FreeBSD before
10.0, but not since. I was told this was an EFI problem, so I have tried
to make an EFI installation, which the installer doesn't seem to do.

Anyway, I am able to do an EFI boot using rEFInd which loads the loader
and kernel quite happily, but when it tried to boot the kernel I get:

Booting [/boot/kernel/kernel]...
Start  <at>  0xffffffff802d8990 ...

And then nothing else happens.

Has anyone got this working? Does it even make sense me trying to get
this working, since I am unable to get a bootable system using the
installer. Should dual booting on a Mac work these days >= 10.0?


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

jenkins-admin | 15 Sep 17:15 2014

Build failed in Jenkins: FreeBSD_stable_10 #753

See <>


[trasz] MFC r271169:

Turn two errors, which are possible to trigger only by bugs,
into assertions.

Approved by:	re (gjb)
Sponsored by:	The FreeBSD Foundation

[trasz] MFC r271157:

Fix typo.

Approved by:	re (marius)
Sponsored by:	The FreeBSD Foundation

[trasz] MFC r271436:

Fix typo.

Approved by:	re (marius)
Sponsored by:	The FreeBSD Foundation

[trasz] MFC r271317:

Avoid unlocking unlocked mutex in RCTL jail code.  Specific test case
is attached to PR.
(Continue reading)

Erich Dollansky | 15 Sep 08:59 2014

mq_open sets errno to 78 when queue does not exist


I have a very simple program. It basically tries to open a message
queue which does not exists. mq_open returns then -1 but errno is set
to 78 which is defined as this: 

#define	ENOSYS 78 /* Function not implemented */

The line in question:

res = mq_open ("/doesnotexist", O_RDWR);

"/doesnotexists" is the non-existing message queue the program tests
for. res will be set correctly to -1 but errno is set then to 78.

If I want to create the message queue, I will get the same error.

uname -a says:

r271420: Sat Sep 13 15:09:34 WITA 2014
erich <at>  amd64

Do I see or do something wrong or is this an error?

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

Mehmet Erol Sanliturk | 15 Sep 03:51 2014

FreeBSD 10.1 amd64 Beta1 : No bootable device

Dears All ,

I have installed FreeBSD 10.1 amd64 Beta 1 DVD .iso with only default
selections .

When the computer rebooted after installation , last message was the
following :

Intel(R) Boot Agent GE v1.2.42
No bootable device -- insert boot disk and press any key .

Many latest Linux distributions are able to boot in that computer after
their installations .

Thank you very much .

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

Glen Barber | 14 Sep 20:17 2014

FreeBSD 10.1-BETA1 Now Available

The first BETA build of the 10.1-RELEASE release cycle is now available
on the FTP servers for the amd64, armv6, i386, ia64, powerpc, powerpc64
and sparc64 architectures.

The image checksums follow at the end of this email.

Installer images and memory stick images are available here:

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "stable/10" branch.

A list of changes since 10.0-RELEASE are available on the stable/10
release notes page here:

Pre-installed virtual machine images for 10.1-BETA1 are also available
for amd64 and i386 architectures.

The images are located here:

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
(Continue reading)

Karl Denninger | 14 Sep 17:07 2014

Status update - ZFS "stalls" and other misbehavior

Those of you who have seen misbehavior of various sorts while running 
-STABLE w/ZFS filesystems may want to check out the developments in this 
thread on Bugzilla.

Work has continued on the candidate patch I posted back in March, and I 
recently put forward an updated version incorporating changes made by 
Steve as well that, at least in my testing and (thus far) on one 
production system here, have completely eliminated the problem.

More eyes looking at it and running it down are obvious better so if you 
have an interest in this issue or have had problems in this area 
(/*especially*/ if you have had system "stalls") please check it out.

Those who are using my previous patch from back in March definitely want 
to look at this; while the March changes did largely fix the issue they 
did so by moving the "danger zone" further out but did not prevent the 
ZFS code from invading system RAM to the point that it could produce 
stalls -- it just made it much less likely.  The most-recent patch, as 
far as I've been able to determine, completely prevent it even when the 
system is severely overstressed in terms of demanded I/O rate or when 
the target pool is compromised (e.g. during a resilver operation.)



Karl Denninger
karl <at> <mailto:karl <at>>
/The Market Ticker/
(Continue reading)

Harald Schmalzbauer | 14 Sep 14:21 2014

option *KB*_DFLT_KEYMAP and *map.h in sys/conf/files


currently I can't compile a kernel on a 10-stable machine with
differtent default keymap.
Reason is, that the k*map.h file gets generated at compile time, coded
in sys/conf/files.arch.

For any reason, on my 10-stable build machine, kbdcontrol(1) does look
for maps in /usr/share/vt/keymaps, although usr.sbin/kbdcontrol/path.h has
#define KEYMAP_PATH      "/usr/share/syscons/keymaps/
I guess it's because I have kern.vty=vt

Further guess is that I can build the kernel by setting 'env
KEYMAP_PATH=/usr/share/syscons/keymaps' for kernel configs having
*KB*_DFLT_KEYMAP set to syscons keymap name.

But I see some problematic cases in the way the neccessarry header files
gets generated.

First, I think that reading keymaps from the machine's installed maps
instead of the ones which are in the sources is not optimal.
Maybe it was intentional set to read machine's keymaps to be able to
compile a kernel without userland sources?!? But since 9k6 Modems and
ctm are obsolete, I can see no good reason any more.

Next is that buildkernel depends on kbdcontrol(1) on the build machine.
Don't know actually how this can be improoved, one must be able to
compile a kernel without userland, so there's most likely no obj tree
where we could use another kbdcontrol(1).

(Continue reading)

Toomas Aas | 13 Sep 18:25 2014

Failed to attach fbd device: 6

I just updated my 10-STABLE amd64 machine from r268926 to r271474. My  
PC has ATI Radeon X1300/X1550 video adapter and I am using radeonkms  
(loaded from loader.conf)

One message in dmesg.boot which wasnt't there before the update caught my eye

error: [drm:pid0:drm_fb_helper_single_fb_probe] *ERROR* Failed to  
attach fbd device: 6

Other than this error message, I am not seeing any ill effects. I'm  
just curious if something could be done to fix this.

Full dmesg:


Toomas Aas

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

Cristiano Deana | 12 Sep 10:53 2014

pkg info and dependencies (openssl related)


in a 9.x box I installed openssl from ports to have 1.x version. Now I
upgraded to 10-STABLE, so I'd prefer use openssl from base.

first problem: changing USE_OPENSSL_PORT to #USE_OPENSSL_PORT if I
have openssl installed recompiling ports needed openssl they linked
against the ports version, not the base version. If I specify
USE_OPENSSL_BASE I can't recompile (eg nginx) because openssl port is
So, what I should do is deinstalling all dep ports, delete openssl,
then reinstalling them.
Or I should force the recompiling against base openssl.

second problem: if I wanna know which ports depend from openssl i got:

pkg info -r openssl
(Continue reading)

Freddie Cash | 11 Sep 17:15 2014

Using CARP with multiple IP aliases (FBSD 10.0)

Good morning,

Just looking for some clarification around the proper use of CARP on
interfaces with multiple IPs.

I've been using the new CARP on FreeBSD 10.0 with great success on a pair
of systems with lots of vlans across 3 physical NIC ports.  However, those
systems only have a single IP per vlan.  The ifconfig lines are very
simple, and everything just works the way I expect it to, failing back and
forth between the two systems as needed.

I'm now trying to get CARP working on a second pair of systems, and running
into issues with one of the physical interfaces.  I think I might be doing
the ifconfig commands wrong, but the ifconfig(8) and carp(4) man pages
aren't very clear on this usage.

Are all of the carp-related parameters required for every IP alias added to
an interface?  Or are the pass/advbase/advskew only needed once per
interface, and you just pass the vhid to each IP alias?

Currently, I'm doing the former and having issues with both boxes claiming
to be master for that one interface.

Which is correct:

ifconfig igb0 inet vhid 30 pass mypass
ifconfig igb0 inet vhid 30 pass mypass alias
ifconfig igb0 inet vhid 30 pass mypass alias
ifconfig igb0 inet vhid 30 pass mypass alias
ifconfig igb0 inet vhid 30 pass mypass alias
(Continue reading)

John Marshall | 11 Sep 08:47 2014

10.1 kernel device config for drm2 and kms drivers

I cannot find any kernel device configuration statements for drm2 or KMS
(e.g. i915kms) drivers in any of the NOTES files in 10-STABLE.
Presumably configurtation statements for these ought to be available for
use in kernel configuration files for 10.1-RELEASE?

At present, the only way I have found to pick them up (short of hacking
sys/conf/files or building all modules) is by specifying the module in
make.conf and then adding the load_ directive to loader.conf.



John Marshall