9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "kazumi iwane" <kiwane@dream.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] kfs is suicidal
Date: Mon, 26 Mar 2001 22:40:04 +0900	[thread overview]
Message-ID: <LPBBIBIIHKHEGDBPHBDOOEEGCAAA.kiwane@dream.com> (raw)

Hello 9fans,

I just got a standalone system installed on sdC1,
but it is quite unstable. I am looking for some help.

kfs dies very very frequently. It only lasts about 15
minutes on average, leaving me almost no time to
investigate the problem. I am usually doing ordinary
things such as typing commands or reading files
when it happens, but I can't determine what action
actually kills kfs.

I get dying messages, such as:

  kfs 6: suicide: sys: trap: fault read addr=0x4b pc=0x000043f3

but it's not helping me in finding out the problem.

For what it's worth, here is what '#S/sdC1/ctl' says:

 inquiry QUANTUM FIREBALL EL5.1A
 config 045A capabilities 0F00 dma 00550004 dmactl 00000000 rwm 16 rwmctl 0
 geometry 10018890 512 10602 15 63
 part data 0 10018890
 part plan9 63 10008495
 part 9fat 63 20545
 part fs 20545 9853687
 part swap 9853687 10008495

And here is what 9pcdisk says about ata devices (I think)
at the boot time:

 dev A0 port 1F0 config 045A capabilities 0F00 mwdma 0407 dma 00000004 rwm 8
 dev B0 port 1F0 config 045A capabilities 0F00 mwdma 0007 udma 0407 dma
00550004 rwm 16
 dev A0 port 170 config 8580 capabilities 0A00 mwdma 2045 dma 00000000 rwm 0

After a couple of suicides, kfs manages to damage
its storage beyond recovery, and the system no longer
boots, making me to install again and again.

Any help is much appreciated. Thank you.



                 reply	other threads:[~2001-03-26 13:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=LPBBIBIIHKHEGDBPHBDOOEEGCAAA.kiwane@dream.com \
    --to=kiwane@dream.com \
    --cc=9fans@cse.psu.edu \
    /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).