From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <0c96d15d8e671ed86a19351e0334e096@brasstown.quanstro.net> From: Ramakrishnan Muthukrishnan Date: Fri, 6 Jun 2014 10:48:21 +0530 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] suicide message on vmware Topicbox-Message-UUID: f5af27b6-ead8-11e9-9d60-3106f5b1d025 Well, looks like I cannot run any binaries anymore and getting the suicide message! I don't have anything critical on this vm image and can re-install it. But I want to see if I can recover it and how. I will re-read the "syscall 53" thread to look for any solutions. Ramakrishnan On Fri, Jun 6, 2014 at 9:35 AM, Ramakrishnan Muthukrishnan wrote: > On Fri, Jun 6, 2014 at 8:51 AM, erik quanstrom wrote: >> On Thu Jun 5 23:17:37 EDT 2014, vu3rdd@gmail.com wrote: >>> Hi, >>> >>> I just saw a suicide message on 9atom running on plan9 while updating >>> the system: >>> >>> % replica/pull -v /dist/replica/network >>> >>> After a while, I saw this printed, but the replica/pull is proceeding >>> without any problem. >>> >>> (not completely readable because stats window overwrote the screen) >>> ... bad sys call number 53 pc 101c6 >>> timesync 57: suicide: sys: bad syscall pc=0x101c6 >> >> nsec! arrrrrgh! > > Ah, I should have remembered. > > So, I guess, I got the updating sequence wrong? First upgrade kernel, > then upgrade the rest? > > -- > Ramakrishnan -- Ramakrishnan