9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve_Kilbane@cegelecproj.co.uk Steve_Kilbane@cegelecproj.co.uk
Subject: 9ssfs and 9sscpu
Date: Fri, 23 Feb 1996 08:38:03 -0500	[thread overview]
Message-ID: <19960223133803.P-Rgd8ODghj_feAPMhuLDabzwjssHhahgcQKXssFlbU@z> (raw)



Back in December, I mentioned I was having problems getting 9ssfs to
scribble on a disk. I've had a deeper look, and I'm still baffled, but I can
at least give a little more detail. The physical setup is a 16MB SLC with
three 207MB Sun disks attached (SCSI targets 1-3).

wreninit() calls scsidrive(), calls probe(), calls scsiio(). For ids 0-6,
there's a delay of 60 seconds, then scsiio() returns 0. Id 7 is skipped.
scsidrive() returns something which wreninit() thinks is valid, so
it goes ahead, there's another delay, and then a kernel panic.

I know nothing about SCSI drivers, but two things strike me. The
first is that the disks are fine (they were in use under SunOS until
I swiped them), so I guess the probe shouldn't be reaching its
timeout limit, but it is. The second is that wreninit() still gets something
valid back. probe() seems to default to the drive being ready, unless
it gets definite notification otherwise.

I could only see one mention of boddles for fs, and that was for the
PC-specific stuff. I'll see if I can find out why wreninit() manages
to break things afterwards, but I'd be grateful for any suggestions - 
I'm pretty much clutching at straws in the dark here, to mix a
metaphore or two.

steve






             reply	other threads:[~1996-02-23 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-23 13:38 Steve_Kilbane [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-02-23 14:19 Steve_Kilbane
1995-12-07 22:01 forsyth
1995-12-07 21:13 Scott
1995-12-07 18:57 Steve_Kilbane
1995-12-07 16:01 Steve_Kilbane

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=19960223133803.P-Rgd8ODghj_feAPMhuLDabzwjssHhahgcQKXssFlbU@z \
    --to=steve_kilbane@cegelecproj.co.uk \
    /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).