CyberSCSI MK-II support and my HD

[Miloslaw Smyk <thorgal%dedal.man.szczecin.pl@localhost>]

Hello,

I've been testing new 1.2G kernel (phase5 SCSI support) with my CyberSCSI
MK-II attached to CyberStorm MK-II 060/50MHz. I booted it from my IDE
drive and:

It recognized SCSI interface and attached devices correctly:

Oct 11 19:52:23 amiga /netbsd: zbus0 at mainbus0: i/o size 0x04000000
Oct 11 19:52:23 amiga /netbsd: cbiisc0 at zbus0 rom 0xea0000 man/pro
8512/25: address 0x2f3ff03: FAS216, 40MHz, SCSI ID 7
Oct 11 19:52:23 amiga /netbsd: scsibus1 at cbiisc0: 8 targets
Oct 11 19:52:23 amiga /netbsd: probe(cbiisc0:3:0): max sync rate 10.00Mb/s
Oct 11 19:52:23 amiga /netbsd: cd0 at scsibus1 targ 3 lun 0: <TOSHIBA,
CD-ROM XM-5701TA, 0167> SCSI2 5/cdrom removable
Oct 11 19:52:23 amiga /netbsd: probe(cbiisc0:4:0): max sync rate 10.00Mb/s
Oct 11 19:52:23 amiga /netbsd: sd1 at scsibus1 targ 4 lun 0: <QUANTUM,
FIREBALL_TM3200S, 300X> SCSI2 0/direct fixed
Oct 11 19:52:23 amiga /netbsd: sd1: 3067MB, 6810 cyl, 5 head, 184 sec, 512
bytes/sect x 6281856 sectors

Then, following lines were displayed:

Oct 11 19:52:23 amiga /netbsd: warning found rdb->secpercyl(794) !=
rdb->nsectors(159) * rdb->nheads(5)
Oct 11 19:52:23 amiga /netbsd: warning lp->d_sparespercyl(1) not multiple of
lp->d_ntracks(5)
Oct 11 19:52:24 amiga /netbsd: Partition 'hd0' geometry 5/159 differs from
RDB 5/159
Oct 11 19:52:24 amiga /netbsd: Partition 'hd1' geometry 5/159 differs from
RDB 5/159
Oct 11 19:52:24 amiga /netbsd: Partition 'hd3' geometry 5/159 differs from
RDB 5/159

Two first lines are ok, as this is true that Fireball TM3200S with firmware
300X reports such config. I am not sure what the next three lines are for.

What's more, instead of listing unrecognized partitions once at boot time,
the kernel insisted on displaying them every 30 seconds or so.

Oct 11 19:52:24 amiga /netbsd: warning unknown dostype: 0x0 marking unused


I then prepared one of SCSI drive's partitions with

newfs -b4096 <partition>

and here is what I got:

/dev/rsd1j:1027436 sectors in 1294 cylinders of 5 tracks, 159 sectors
501.7MB in 81 cyl groups (16 c/g, 6.20MB/g, 2976 i/g)
super-block backups (for fsck -b #) at:
 32, 12896, 25760, 38624, 51488, 64352, 77216, 90080,
 101664, 114528, 127392, 140256, 153120, 165984, 178848, 191712,
 203296, 216160, 229024, 241888, 254752, 267616, 280480, 293344,
 304928, 317792, 330656, 343520, 356384, 369248, 382112, 394976,
 406560, 419424, 432288, 445152, 458016, 470880, 483744, 496608,
 508192, 521056, 533920, 546784, 559648, 572512, 585376, 598240,
 609824, 622688, 635552, 648416, 661280, 674144, 687008, 699872,
 711456, 724320, 737184, 750048, 762912, 775776, 788640, 801504,
 813088, 825952, 838816, 851680, 864544, 877408, 890272, 903136,
 914720, 927584, 940448, 953312, 966176, 979040, 991904, 1004768,
 1016352,

So far so good.

I mounted the partition under /mnt and copied kernel file there. Then, I
unmounted the partition and ran `fsck -f` on it. It reported no problems. So
I mounted the partition again and tried comparing (cmp) the original kernel
file with the one on /mnt. At this point I got the following msg:

panic: pmap_alloc_pv: pgi_nfree inconsistent
Stopped at 0xb1a26: unlk a6

and I found myself in the debugger.


Now, I do not know if problems are due to buggy driver or my HD. The latter
is more probable, as this Fireball thing had serious problems
under Linux-m68k and although people at Linux-m68k ML did not manage to
determine the cause of them, it may well be that the difference between
number of sectors per surface multiplied by number of heads and number of
sectors per cylinder contributes here.

Oh, one more thing: under AmigaOS FFS makes no problem of it, but AFS
does - it miscalculates the size of the partition.

Help?

cu,
Milek
-- 
http://wfmh.man.szczecin.pl/~thorgal

"In 1977 an heavenly being spoke to me about
an injury to my head that happened in 1968."