Linuxu­lat­or in -cur­rent ready for test­ing the 2.6.16 emu­la­tion

Today I com­mit­ted two patches which fix the last two pan­ics we know about in the 2.6.16 emu­la­tion. Now we need test­ers. Here’s the text of the mail I did send to current@ a few mo­ments ago:


today I com­mit­ted the last fixes for the showstop­per prob­lems (pan­ics) in the linux 2.6.16 emu­la­tion. I in­tend to switch the de­fault ver­sion to 2.6.16 on i386 “soon” (see be­low), so please help test­ing it.

More re­cent linux dis­tri­bu­tions (e.g. FC5) re­quire a 2.6 ker­nel and don’t work with 2.4.2 any­more. And be­cause FC4 is “abandon-​ware” (no se­cur­ity fixes from fe­dor­alegacy any­more), get­ting 2.6.16 emu­la­tion up an run­ning is very im­port­ant.

If you use a linux pro­gram, please add compat.linux.osrelease=2.6.16 to /etc/sysctl.conf (my desktop is run­ning with 2.6.16 emu­la­tion since some days already). After the next boot (or after run­ning “sy­sctl compat.linux.osrelease=2.6.16”, please make sure no linux pro­gram is run­ning already) any linux pro­gram will start with a linux ker­nel ver­sion of 2.6.16 in­stead of 2.4.2. The de­fault linux base port (FC4) will then use dif­fer­ent code paths (e.g. with­in glibc). In case you want to switch back to the 2.4.2 emu­la­tion without a re­boot, please make sure no linux pro­gram is run­ning any­more.

So far we fixed all known/​repeatable prob­lems with acror­ead, real­play­er, skype and linux fire­fox. If you en­counter strange be­ha­vi­or with any linux pro­gram, please tell us (emulation@​freebsd.​org) which pro­gram you used, how to re­peat the prob­lem, what the prob­lem is, and if it only is vis­ible with 2.6.16 or with 2.4.2 too. You should also watch out for mes­sages in the dmesg (un­im­ple­men­ted sys­tem calls or oth­er stuff, this is used to de­term­ine the pri­or­ity of miss­ing sy­scalls). Please also have a look at http://​wiki​.FreeBSD​.org/​l​i​n​u​x​-​k​e​r​nel, I in­tend to doc­u­ment the known prob­lems there. If you find your prob­lem there, please tell us about it if you are will­ing to test fixes.

We are spe­cially in­ter­ested in re­ports (good or bad) on SMP sys­tems. Please beat the hell out of the linuxu­lat­or!

On amd64 sys­tems we have not the same func­tion­al­ity as on i386, miss­ing are fu­texes and TLS. In P4 we already have the fu­tex part covered, but the TLS part is still miss­ing (any­one with a clue about the ker­nel side of TLS on amd64 is wel­come to give a hint or two to jkim@ and rdivacky@). So if you get a mes­sage about miss­ing fu­texes or TLS on amd64: we know about it (test­ers for the fu­tex stuff are wel­come, but first you need to use a pro­gram which uses fu­texes and com­plains).

As long as we get prob­lem re­ports with 2.6.16 I will not switch the de­fault to 2.6.16. If we don’t get a re­port at all, I will switch the de­fault on i386 to 2.6.16 in two weeks. If we get some prob­lem re­ports, we will push back the switch a little bit de­pend­ing on the sever­ity of the prob­lem.


1 thought on “Linuxu­lat­or in -cur­rent ready for test­ing the 2.6.16 emu­la­tion”

  1. Pingback: Video for linux (v4l) emulation coming to the linuxulator « The Daily BSD

Leave a Reply

Your email address will not be published. Required fields are marked *