Date: Sat, 19 Aug 2006 13:48:25 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: Yuri <yuri.pankov@gmail.com>, freebsd-emulation@freebsd.org Subject: Re: panic when running acroread on recent -CURRENT/amd64 Message-ID: <20060819134825.17a98fb1@Magellan.Leidinger.net> In-Reply-To: <20060819104117.GA99504@stud.fit.vutbr.cz> References: <b02aa3c10608181629kdaeb542i8fda838fbe3ada1@mail.gmail.com> <20060819104117.GA99504@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Divacky Roman <xdivac02@stud.fit.vutbr.cz> (Sat, 19 Aug 2006 12:41:18 +0200): > On Sat, Aug 19, 2006 at 03:29:18AM +0400, Yuri wrote: > > Hi, > > > > After upgrading to -CURRENT/amd64 as of 18 August 2006, around 7PM > > GMT, I'm getting panics when running acroread, even without X. Ports > > were upgraded too. > > > > linux_base-fc-4_8 > > acroread7-7.0.8,1 > > > > If more information is needed, it's 100% reproducible here. > > > > --- > > Unread portion of the kernel message buffer: > > panic: no emuldata found for userreting process. > > I know what causes it.. and netchild's fix wont fix it. but I dont know what to do with it... Uhm... I thought the missing parts have no impact there! And didn't we protected the emuldata part with the osrelease sysctl? I will have a look at this in an hour and come back to you. > 1) I can fix this (its trivial) and wait what else will cause panic > > 2) I can port MI emuldata stuff to amd64 (but I cannot test it) and this > should fix all these panics like the one you are seeing > > 3) I can say "amd64 linuxolator is broken now pls wait" Forget about 3), either 2) or 1). Bye, Alexander. -- How come we never talk anymore? http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060819134825.17a98fb1>