Menu
▾
▴
Re: [Scst-devel] Using scsi_ses.ko, kernel error/crash in log.
|
From: Vladislav B. <vs...@vl...> - 2008-03-20 15:25:45
|
Bob Quincy wrote: > I am now using the 2.6.24 from kernel.org <http://kernel.org> on a real > machine instead of a vmware machine. > > I patched (hopefully correct) the scsi_ses.c file to build with the > change from scatterlist->page to scatterlist->page_link (I am newbie to > this stuff and my C skills are about 10 years old) > > Now, I get this: > > Mar 19 06:49:58 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:49:58 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:49:58 armadale kernel: 0: 1c 01 01 24 00 00 ...$.. > Mar 19 06:49:58 armadale kernel: [7828]: scst: > scst_alloc_space:1576:Warning: data direction 2 or/and zero buffer > length. Opcode 0x1c, handler dev_disk, target iscsi > Mar 19 06:49:58 armadale kernel: [7124]: scst: > scst_do_send_to_midlev:1798:scst_exec_req() failed: 67108864 > Mar 19 06:49:59 armadale kernel: [7828]: scst: > scst_parse_cmd:556:Warning: expected transfer length 9216 for opcode > 0x1c (handler dev_disk, target iscsi) doesn't match decoded value 0. > Faulty initiator (e.g. VMware is known to be such) or scst_scsi_op_table > should be updated? > Mar 19 06:49:59 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:49:59 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:49:59 armadale kernel: 0: 1c 01 01 24 00 00 ...$.. > Mar 19 06:49:59 armadale kernel: [7828]: scst: > scst_alloc_space:1576:Warning: data direction 2 or/and zero buffer > length. Opcode 0x1c, handler dev_disk, target iscsi > Mar 19 06:49:59 armadale kernel: [7102]: scst: > scst_do_send_to_midlev:1798:scst_exec_req() failed: 67108864 > Mar 19 06:50:00 armadale kernel: [7828]: scst: > scst_parse_cmd:556:Warning: expected transfer length 12 for opcode 0x25 > (handler dev_disk, target iscsi) doesn't match decoded value 8. Faulty > initiator (e.g. VMware is known to be such) or scst_scsi_op_table should > be updated? > Mar 19 06:50:00 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:50:00 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:50:00 armadale kernel: 0: 25 00 00 00 00 00 00 00 00 00 > %......... > Mar 19 06:50:00 armadale kernel: [7828]: scst: > scst_parse_cmd:556:Warning: expected transfer length 9216 for opcode > 0x1c (handler dev_disk, target iscsi) doesn't match decoded value 0. > Faulty initiator (e.g. VMware is known to be such) or scst_scsi_op_table > should be updated? > Mar 19 06:50:00 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:50:00 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:50:00 armadale kernel: 0: 1c 01 01 24 00 00 ...$.. > Mar 19 06:50:00 armadale kernel: [7828]: scst: > scst_alloc_space:1576:Warning: data direction 2 or/and zero buffer > length. Opcode 0x1c, handler dev_disk, target iscsi > Mar 19 06:50:00 armadale kernel: [7124]: scst: > scst_do_send_to_midlev:1798:scst_exec_req() failed: 67108864 > Mar 19 06:50:01 armadale kernel: [7828]: scst: > scst_parse_cmd:556:Warning: expected transfer length 9216 for opcode > 0x1c (handler dev_disk, target iscsi) doesn't match decoded value 0. > Faulty initiator (e.g. VMware is known to be such) or scst_scsi_op_table > should be updated? > Mar 19 06:50:01 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:50:01 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:50:01 armadale kernel: 0: 1c 01 01 24 00 00 ...$.. > Mar 19 06:50:01 armadale kernel: [7828]: scst: > scst_alloc_space:1576:Warning: data direction 2 or/and zero buffer > length. Opcode 0x1c, handler dev_disk, target iscsi > Mar 19 06:50:01 armadale kernel: [7102]: scst: > scst_do_send_to_midlev:1798:scst_exec_req() failed: 67108864 > Mar 19 06:50:02 armadale kernel: [7828]: scst: > scst_parse_cmd:556:Warning: expected transfer length 9216 for opcode > 0x1c (handler dev_disk, target iscsi) doesn't match decoded value 0. > Faulty initiator (e.g. VMware is known to be such) or scst_scsi_op_table > should be updated? > Mar 19 06:50:02 armadale kernel: [7828]: scst_parse_cmd:558:Suspicious CDB: > Mar 19 06:50:02 armadale kernel: > (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F > Mar 19 06:50:02 armadale kernel: 0: 1c 01 01 24 00 00 ...$.. > Mar 19 06:50:02 armadale kernel: [7828]: scst: > scst_alloc_space:1576:Warning: data direction 2 or/and zero buffer > length. Opcode 0x1c, handler dev_disk, target iscsi > Mar 19 06:50:02 armadale kernel: [7124]: scst: > scst_do_send_to_midlev:1798:scst_exec_req() failed: 67108864 It is improper implementation of RECEIVE DIAGNOSTIC RESULTS command. Try with the attached patch. Thanks, Vlad |