Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Jan 2012 17:58:06 +0200
From:      Bartosz Fabianowski <freebsd@chillt.de>
To:        Hans Petter Selasky <hselasky@c2i.net>, freebsd-current@freebsd.org,  freebsd-usb@freebsd.org, poyopoyo@puripuri.plala.or.jp
Subject:   Re: umass regression
Message-ID:  <4F09BD0E.5090606@chillt.de>
In-Reply-To: <86r4zagqyv.wl%sf@FreeBSD.org>
References:  <4EF9D06C.9060501@chillt.de>	<201201031726.03885.hselasky@c2i.net>	<4F03317D.6080702@chillt.de>	<201201031815.32624.hselasky@c2i.net> <86r4zagqyv.wl%sf@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Interesting timing. I am just in the middle of a debug session to try 
and debug this. I know nothing about umass and/or SCSI, so it is all one 
big learning experience for me. Here is what I am seeing (snippets from 
[1]):

* SCSI command "REPORT LUNS" is sent:

55 53 42 43 03 00 00 00  18 00 00 00 80 00 0C A0
00 00 00 00 00 00 00 00  18 00 00 00 00 00 00

* List of LUNs is received:

00 00 00 10 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 01

This list contains exactly two LUNs, 0 and 1. The list is then processed 
by scsi_xpt.c. After reading the first entry, LUN 0 is scanned and da0 
created. Then, the next entry is read. And something seems to go wrong 
here. The debug output I get is:

cam_debug: next lun to try at index 1 is 0

IMHO, this should not be. The entry at index 1 is LUN 1, not LUN 0. It 
seems that instead of scanning LUN 0 and LUN 1, the code ends up 
scanning LUN 0 twice. I have no idea why though.

- Bartosz



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F09BD0E.5090606>