From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <0c96d15d8e671ed86a19351e0334e096@brasstown.quanstro.net>
References: <CAA6Yd9U0GDakGZn0whEtDo7hmYque3uiQFs7GJ1SnaVT2_joAg@mail.gmail.com>
	<0c96d15d8e671ed86a19351e0334e096@brasstown.quanstro.net>
From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
Date: Fri,  6 Jun 2014 09:35:50 +0530
Message-ID: <CAA6Yd9WFC3szbN0f=Hz6wDZOQYj5nxZ_9uXMfcjGQkVPF89CHw@mail.gmail.com>
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: f5a71ce2-ead8-11e9-9d60-3106f5b1d025

On Fri, Jun 6, 2014 at 8:51 AM, erik quanstrom <quanstro@quanstro.net> 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