From owner-freebsd-questions Thu Mar 2 20:53: 5 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id D02FB37B59C for ; Thu, 2 Mar 2000 20:52:56 -0800 (PST) (envelope-from sid@lambert.yi.org) Received: from sid.yi.org (host-209-214-69-146.atl.bellsouth.net [209.214.69.146]) by mail1.atl.bellsouth.net (3.3.5alt/0.75.2) with SMTP id XAA02809 for ; Thu, 2 Mar 2000 23:45:55 -0500 (EST) From: Sid Lambert Date: Fri, 03 Mar 2000 04:47:47 GMT Message-ID: <20000303.4474700@sid.yi.org> Subject: Staroffice5.1 and kernel error To: freebsd-questions@freebsd.org X-Mailer: Hi Kent (FreeBSD Damnit) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------=_4D480166307C2B1D5960" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------=_4D480166307C2B1D5960 Content-Description: filename="text1.txt" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am running FreeBSD 3.4 stable on a P100 , 64 megs and a 4 gig=20 hd(ide). I have kde installed and have just started using staroffice=20 (ver5.1) and have been getting this error. /kernel cmd soffice.bin pid (pid) tried to use non-present sched_yield I am assuming this is pretty common... I have talked to few others=20 that have the same problem but none of them knew of a fix.... I have=20 also talked to the former port maintainer ...If you have any=20 suggestions please send them my way. Thanks Sid Lambert --------------=_4D480166307C2B1D5960 Content-Description: filename="text1.html" Content-Type: text/html Content-Transfer-Encoding: quoted-printable Staroffice5.1 and kernel error

I am running FreeBSD 3.4 stable on a P100 , 64 megs and a 4 gig hd(ide). I have kde installed and have just started using staroffice (ver5.1) and have been getting this error.

/kernel cmd soffice.bin pid (pid) tried to use non-present sched_yield

I am assuming this is pretty common... I have talked to few others that have the same problem but none of them knew of a fix.... I have also talked to the former port maintainer ...If you have any suggestions please send them my way.



Thanks

Sid Lambert

--------------=_4D480166307C2B1D5960-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message