From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 23 Feb 1996 08:38:03 -0500
From: Steve_Kilbane@cegelecproj.co.uk Steve_Kilbane@cegelecproj.co.uk
Subject: 9ssfs and 9sscpu
Topicbox-Message-UUID: 3d308c9e-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960223133803.P-Rgd8ODghj_feAPMhuLDabzwjssHhahgcQKXssFlbU@z>



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