Re: [9fans] Rio panic

Re: [9fans] Rio panic

[Louis Beleos]

On Tue, 15 Aug 2000, Steve Simon wrote:

> Hi,
> 
> Before I start delving, I wonder if I have missed an upddate?
> 
> I have the 1st August installation
> 
> I rebuilt the entire system:
> 
> 	mk 'CONF=pc' install
> 
> now rio regularly panics - every 5 mins or so.
> ...

Have you applied the following patch?

 From rob@plan9.bell-labs.com Tue Aug 15 15:36:44 2000
Date: Sun, 30 Jul 2000 10:53:31 -0400
From: rob pike <rob@plan9.bell-labs.com>
Reply-To: 9fans@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: [9fans] rio
Status: RO
X-Status: 

Stupid bug introduced in rio, caused by our attempts to clean up
uses of %.*s.  /sys/src/cmd/rio/xfid.c:508 is missing an argument.
diff /n/dump/2000/0730/sys/src/cmd/rio/xfid.c xfid.c
508c508
< 			sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt));
---
> 			sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt), x->data);

The distributed binary is OK, but if you build from the unfixed
source all hell will break loose.

Mea culpa.  The compiler warns you and in all the furious building
I missed the warning.

-rob

[9fans] Rio panic

[Steve Simon]

Hi,

Before I start delving, I wonder if I have missed an upddate?

I have the 1st August installation

I rebuilt the entire system:

	mk 'CONF=pc' install

now rio regularly panics - every 5 mins or so.

I work around this by running rio in a subwindow so
when it dies I can kill the child and start another,
nifty feature of rio but a workaround nevertheless.

Every time rio panics it prints:

mem user overflow
pool sbrkmem block ?????
...
panic: pool panic
rio ????: abort: sys: trap: fault read addr 0x00000000 pc=x00026f4a
...

I include the read & PC addresses as they are the only constant numbers
in the
various panic messages.

Any ideas anyone?

-Steve