[9fans] fossil gone :)

[9fans] fossil gone :)

[andrey mirtchovski]

with fireworks. the machine was hung on a
reading process (a fossil thread was in the running state) after a very long
running graphics-intensive program in a drawterm window had died. ^T^Tk
produced (note, i have (err, had) swap configured):

fossil killed because no swap configured
assert failed: p->writer != nil
fossil 50: suicide: sys: trap: fault read addr=0x0 pc=0x0002b5af
assert failed: b->nlock == 0
fossil 44: suicide: sys: trap: fault read addr=0x0 pc=0x0002b5af
fossil 42: suicide: sys: trap: fault read addr=0x1 pc=0x00029773
fossil 45: suicide: sys: trap: fault write addr=0x0 pc=0x0002b5c2
reboot...
i'm having problems with fossil
that's the only thing that's killing me
fsOpen error
superGet: superUnpack failed: corrupted super blockarchThread: superGet: corrup

Re: [9fans] fossil gone :)

[andrey mirtchovski]

On Mon, 18 Aug 2003, andrey mirtchovski wrote:

> i'm having problems with fossil
> that's the only thing that's killing me
>

this sneaked in from irc, i don't know how :) probably a good time to
announce that some of us from this list are gathering on #plan9 @
irc.freenode.net

mostly yaking about how great plan9 is and ooh-aah-ing at witty quotes
from the fortunes file :)

andrey

[9fans] IRC

[Skip Tavakkolian]

> some of us from this list are gathering on #plan9 @
> irc.freenode.net

when it comes to IRC, I'm green.  have you tried it with irctools?
what is the port number?  I've tried 59/113 and 194.

p.s.  are there updates to irctools?  btw, i don't see them on rsc's
page or in sources.

Re: [9fans] IRC

[andrey mirtchovski]

On Mon, 18 Aug 2003, Skip Tavakkolian wrote:

> > some of us from this list are gathering on #plan9 @
> > irc.freenode.net
>
> when it comes to IRC, I'm green.  have you tried it with irctools?
> what is the port number?  I've tried 59/113 and 194.
>
> p.s.  are there updates to irctools?  btw, i don't see them on rsc's
> page or in sources.
>

I use IRC on unix, unfortunately. There are several irc clients written for
Plan 9 (even I did one back in 2000) but their usability is at best
questionable. Try googling for 9irc. Another one is called 'ircc' but I
haven't had a chance to look at it.

'sirc' is a unix irc client written in Perl, it works fine in Plan 9 after
slight modifications. Email me privately if you want it (or if anyone else
wants it).

Ideally we'd have an ircfs and an Irc module for acme. Nobody willing to
write it, though :)

andrey

ps: the irc port to connect to is 6667, then you'd '/join #plan9'

Re: [9fans] IRC

[Jim Choate]

On Mon, 18 Aug 2003, Skip Tavakkolian wrote:

> > some of us from this list are gathering on #plan9 @
> > irc.freenode.net
>
> when it comes to IRC, I'm green.  have you tried it with irctools?
> what is the port number?  I've tried 59/113 and 194.
>
> p.s.  are there updates to irctools?  btw, i don't see them on rsc's
> page or in sources.

Any object if we post this on the H18 page?

 -- --
      ravage@ssz.com                            jchoate@open-forge.com
      www.ssz.com                               www.open-forge.com

Re: [9fans] fossil gone :)

[okamoto]

> reading process (a fossil thread was in the running state) after a very long
> running graphics-intensive program

How many physical memory do your machine has?

Kenji

Re: [9fans] fossil gone :)

[andrey mirtchovski]

On Tue, 19 Aug 2003 okamoto@granite.cias.osakafu-u.ac.jp wrote:

> > reading process (a fossil thread was in the running state) after a very long
> > running graphics-intensive program
>
> How many physical memory do your machine has?
>

512MB, the swap is another 700MB (silly, because i never use it :)..

does the swap need to be configured before fossil starts?

Re: [9fans] fossil gone :)

[okamoto]

> On Tue, 19 Aug 2003 okamoto@granite.cias.osakafu-u.ac.jp wrote:
>
>> > reading process (a fossil thread was in the running state) after a very long
>> > running graphics-intensive program
>>
>> How many physical memory do your machine has?
>>
>
> 512MB, the swap is another 700MB (silly, because i never use it :)..
>
> does the swap need to be configured before fossil starts?

I feel that 512MB is small, because mine has also 512MB
physical memory.

I wonder how quick this mail will dispatch from our Univ.
MS Blaster seems to be running here, too.

Kenji

Re: [9fans] fossil gone :)

[C H Forsyth]

>>SOMETHING killed because no swap configured

killbig() is normally invoked to kill something when swap wasn't
configured on a cpu server, and it is the function invoked when you
use the ^t^tk sequence.  it refuses to kill kfs but has no other
reservations.  fossil happened to be the biggest thing running.
it killed only one of the fossil processes, so i'm not surprised
it caused trouble, although i'm not sure why it caused those
particular errors.

i'd look at the super block first to see what's in it.
for instance, is it slightly wrong, or has it been overwritten
by something else?

Re: [9fans] fossil gone :)

[andrey mirtchovski]

it's alive! thanx to devfs only the first disk was killed.

now, would you like me to get some info out of the first one's superblock or
should i just rewrite it?

andrey

On Tue, 19 Aug 2003, C H Forsyth wrote:

> >>SOMETHING killed because no swap configured
>
> killbig() is normally invoked to kill something when swap wasn't
> configured on a cpu server, and it is the function invoked when you
> use the ^t^tk sequence.  it refuses to kill kfs but has no other
> reservations.  fossil happened to be the biggest thing running.
> it killed only one of the fossil processes, so i'm not surprised
> it caused trouble, although i'm not sure why it caused those
> particular errors.
>
> i'd look at the super block first to see what's in it.
> for instance, is it slightly wrong, or has it been overwritten
> by something else?
>

Re: [9fans] fossil gone :)

[andrey mirtchovski]

spoke too soon:

assert failed: (b->l.state&BsClosed)==0 && b->l.epoch < ehi
fossil 33: suicide: sys: trap: fault read addr=0x0 pc=0x0002b5af

after reinitializing fossil it crashed when i did a 'du /sys'.. now we can't
boot because of the above.

not really looking for help, just letting you know.