From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] suicide message on vmware
Date: Fri, 6 Jun 2014 10:48:21 +0530 [thread overview]
Message-ID: <CAA6Yd9XYn5Ouc0OxqJHdE8rqhgXkupsxaPGK0mFAerCGRnsnRQ@mail.gmail.com> (raw)
In-Reply-To: <CAA6Yd9WFC3szbN0f=Hz6wDZOQYj5nxZ_9uXMfcjGQkVPF89CHw@mail.gmail.com>
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
<vu3rdd@gmail.com> wrote:
> 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
--
Ramakrishnan
next prev parent reply other threads:[~2014-06-06 5:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 3:15 Ramakrishnan Muthukrishnan
2014-06-06 3:21 ` erik quanstrom
2014-06-06 4:05 ` Ramakrishnan Muthukrishnan
2014-06-06 5:18 ` Ramakrishnan Muthukrishnan [this message]
2014-06-06 6:00 ` Bakul Shah
2014-06-06 7:32 ` Ramakrishnan Muthukrishnan
2014-06-06 8:00 ` Bakul Shah
2014-06-06 8:33 ` Ramakrishnan Muthukrishnan
2014-06-06 15:24 ` Bakul Shah
2014-06-06 15:35 ` erik quanstrom
2014-06-06 15:46 ` Ramakrishnan Muthukrishnan
2014-06-06 15:50 ` erik quanstrom
2014-06-06 16:49 ` Bakul Shah
2014-06-06 16:59 ` erik quanstrom
2014-06-06 15:52 ` Ramakrishnan Muthukrishnan
2014-06-06 15:55 ` erik quanstrom
2014-06-06 16:07 ` Ramakrishnan Muthukrishnan
2014-06-06 16:26 ` erik quanstrom
2014-06-06 16:38 ` Ramakrishnan Muthukrishnan
2014-06-07 11:24 ` Ramakrishnan Muthukrishnan
2014-06-07 11:29 ` Aram Hăvărneanu
2014-06-07 14:42 ` erik quanstrom
2014-06-07 17:11 ` Ramakrishnan Muthukrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA6Yd9XYn5Ouc0OxqJHdE8rqhgXkupsxaPGK0mFAerCGRnsnRQ@mail.gmail.com \
--to=vu3rdd@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).