Subject: A Quirk with the new MESH driver on a G3DT233
To: None <port-macppc@netbsd.org>
From: Erik Bertelsen <erik@mediator.uni-c.dk>
List: port-macppc
Date: 02/27/1999 00:25:35
Hello ppc people,

I have some problems with the newly-integrated MESH SCSI driver
for the PowerMac.

The problem manifests itself by one of the disks not being probed.
This is quite inconvenient to me, as the non-probed disk is the
only bootable disk that I have :-( (I'm booting of the disk on
SCSI target 6 (sd2), but having my active file systems on sd0).

Included below is the console output related to the MESH disks
when running with the mesh driver that I've retrieved from
nandra before it got integrated into the main sources and from
a boot with the current MESH driver. The line "mesh: intr_error" 
is added to the driver by me to indicate that the following
output from mesh_error is from the call about line 347 in
mesh.c masked my MESH_INTR_ERROR rather than the one masked
by MESH_INTR_EXCEPTION.

As the driver has been modified quite heavily since the version
from nandra, I've not been able to quickly find out why one
version works, but not the other one.

Other than a disk not being probed, both versions of the MESH
driver seem to work reasonable well -- at least stable enough
to allow the machine to build its own system and run X, etc.

By the way: This is on a PowerMac G3 DT 233MHz with the internal
IDE disk used by MacOS and the SCSI disks by NetBSD-current as
of today.

# With old mesh driver:
mesh0 at obio0 offset 0x10000 irq 12: MESH SCSI ID 7
scsibus0 at mesh0: 8 targets, 1 luns per target
sd0 at scsibus0 targ 2 lun 0: <QUANTUM, FIREBALL ST3.2S, 0F0C> SCSI2 0/direct fixed
sd0: 3090MB, 7068 cyl, 4 head, 223 sec, 512 bytes/sect x 6328861 sectors
 SCSI Bus 0 target 4: rejecting message 0x1e
sd1 at scsibus0 targ 4 lun 0: <IBM OEM, 0662S12, 2 22> SCSI2 0/direct fixed
sd1: 1003MB, 4119 cyl, 5 head, 99 sec, 512 bytes/sect x 2055035 sectors
sd2 at scsibus0 targ 6 lun 0: <CONNER, CFP1080S, 4649> SCSI2 0/direct fixed
sd2: 1030MB, 3658 cyl, 6 head, 96 sec, 512 bytes/sect x 2110812 sectors

# With current mesh driver:
mesh0 at obio0 offset 0x10000 irq 12: 50MHz, SCSI ID 7
scsibus0 at mesh0: 8 targets, 8 luns per target
sd0 at scsibus0 targ 2 lun 0: <QUANTUM, FIREBALL ST3.2S, 0F0C> SCSI2 0/direct fixed
sd0: 3090MB, 7068 cyl, 4 head, 223 sec, 512 bytes/sect x 6328861 sectors
probe(mesh0:4:0): max sync rate 10.00Mb/s
sd1 at scsibus0 targ 4 lun 0: <IBM OEM, 0662S12, 2 22> SCSI2 0/direct fixed
sd1: 1003MB, 4119 cyl, 5 head, 99 sec, 512 bytes/sect x 2055035 sectors
mesh: intr_error
mesh: unexpected disconnect
mesh: intr_error
mesh: unexpected disconnect

best regards
Erik Bertelsen