Re: physio split the request.. cannot proceed

[manu%netbsd.org@localhost (Emmanuel Dreyfus)]

Thor Lancelot Simon <tls%panix.com@localhost> wrote:

> For what it's worth, I've been *very* busy, but there's not actually much
> left to do on the maxphys branch 

I gave it a try, and here is the result on i386:
/netbsd: mpii0: error 27 loading dmamap
/netbsd: st0(mpii0:0:3:0): passthrough: adapter inconsistency

While the kernel says that, here is ltfs log:

LTFS12015I Attempting to load the medium
LTFS20010D SCSI request: [ 1B 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS12026D Locking medium in the drive
LTFS20010D SCSI request: [ 1E 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS11007D Tape is loaded
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=68
LTFS20057D Backend capacity part0: (36750, 36750)
LTFS20057D Backend capacity part1: (2425551, 2425551)
LTFS11008D Reading partition labels
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20039D Backend read: 524288 bytes
LTFS20010D SCSI request: [ 08 02 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS11175E Cannot read ANSI label: expected 80 bytes, but received 0
LTFS11170E Failed to read label (-1012) from partition 0
LTFS11009E Cannot mount volume: failed to read partition labels.
LTFS14013E Cannot mount the volume

I assume the kernel error happens on the read SCSI request [ 08 02 08 00 00 00
], although this is difficult to be sure.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost