Skip to contentSkip to conversation

New: Initio sbp2 causes: "slab error in cache_free_debugcheck(): cache `size-512(DMA)': double free, or memory outside" object was overwritten

Bugme-new Douglas Gilbert 2 participants 4 messages Feb 22, 2006 SCSI

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines · Stefan Richter

What I don't understand is why mode page 8 is still accessed in your
log: http://bugzilla.kernel.org/attachment.cgi?id=7432&action=view
(Log lines "command: Mode Sense (10): 5a 00 08 00 00 00 00 00 d9 00", "SCSI transfer size = 17d9" --- yeah, into a 512 Bytes big buffer, "sda:
got wrong page".)

Stefan,
That sounds familiar. My guess is that a MODE SENSE (6) response is being returned for a MODE SENSE (10) cdb. "sdparm -f" can decode that in some contexts.

Doug Gilbert

P.S. I'm forced to use a broken smtp server hence my truncated reply.

#1 lore raw
Quoted 8 lines · Douglas Gilbert
Quoted 5 lines · Stefan Richter

What I don't understand is why mode page 8 is still accessed in your
log: http://bugzilla.kernel.org/attachment.cgi?id=7432&action=view
(Log lines "command: Mode Sense (10): 5a 00 08 00 00 00 00 00 d9 00", "SCSI transfer size = 17d9" --- yeah, into a 512 Bytes big buffer, "sda:
got wrong page".)

Quoted 4 lines

Stefan,
That sounds familiar. My guess is that a MODE SENSE (6) response is being returned for a MODE SENSE (10) cdb. "sdparm -f" can decode that in some contexts.

No. It's a broken bridge that replies to _everything_ with page 6 and doesn't return a header at all - not 4 bytes for MODE SENSE(6), not 8 bytes for MODE SENSE(10), *zero* bytes. Just the page 6 contents.

So in place of block descriptor length (offsets 6 and 7) you get the part of page 6 body. Which is going to be bits 31..16 of size in blocks. And that's going to be 0x17bd in his case (203928MB/0.5KB/65536).

#2 lore raw
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines · Stefan Richter

What I don't understand is why mode page 8 is still accessed in your
log: http://bugzilla.kernel.org/attachment.cgi?id=7432&action=view
(Log lines "command: Mode Sense (10): 5a 00 08 00 00 00 00 00 d9 00",

Also apart from being a MODE SENSE (10) rather than the required MODE SENSE (6), the DBD bit is not set as required by: www.t10.org/ftp/t10/drafts/rbc/rbc-r10a.pdf section 6.3 .

Perhaps someone could try setting DBD and see if the bridge is any better behaved. The cdb would be:
5a 08 08 00 .... or
1a 08 08 00 ....

Doug Gilbert

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

#3 lore raw
Quoted 10 lines · Douglas Gilbert
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines · Stefan Richter

What I don't understand is why mode page 8 is still accessed in your
log: http://bugzilla.kernel.org/attachment.cgi?id=7432&action=view
(Log lines "command: Mode Sense (10): 5a 00 08 00 00 00 00 00 d9 00",

Also apart from being a MODE SENSE (10) rather than the required MODE SENSE (6), the DBD bit is not set as required by: www.t10.org/ftp/t10/drafts/rbc/rbc-r10a.pdf section 6.3 .

Quoted 4 lines

Perhaps someone could try setting DBD and see if the bridge is any better behaved. The cdb would be:
5a 08 08 00 .... or
1a 08 08 00 ....

DBD doesn't affect the result, MODE SENSE (6) is actually even worse - you get the same page without header _and_ with the first byte missing. BTW, the reason why we don't get DBD is that bridge lies, claiming to be type 0. Note that for _all_ values of modepage it returns (mutilated) page 6, which isn't even defined for type 0.

And yes, the only chance that creators of that thing would ever see the light is colonoscopy; what else is new?