On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan <vu3...@gmail.com> wrote: > 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.
Aren't the old binaries saved under the same name but prefixed with _? If you haven't rebooted yet, you can use those to copy the new kernel to the FAT partition. > > Ramakrishnan > > > On Fri, Jun 6, 2014 at 9:35 AM, Ramakrishnan Muthukrishnan > <vu3...@gmail.com> wrote: > > On Fri, Jun 6, 2014 at 8:51 AM, erik quanstrom <quans...@quanstro.net> wrot > e: > >> On Thu Jun 5 23:17:37 EDT 2014, vu3...@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 >
