Some necessity running scsi_target that I have observed ( 10+ times )

[Nate Lawson]

On Mon, 29 Sep 2003, Jacky Xie wrote:
> 1. data transfer: total about 300GBytes - 1000GBytes) before scsi_target
> crash.

That's not too bad for "example" code.  :-)

> 2. machine running scsi_target crashed in targdone():
>
> Fatal trap 12: page fault while in kernel mode
> fatal virtual address = 0x2a
> fatal code = supervisor write, page not present
> instructioin pointer = 0x8:0xe12c3a8
> stack pointer = 0x10: 0xd49a7d48
> frame pointer = 0x10: 0xd49a7d50
> code segment = base 0x0, limit 0xfffff, type 0x16
>                         DPL 0, pres 1, def32 1, gran 1
> processor flags = trace trap, interrupt enabled, kernel IOPL=0
> current process = 26962(scsi_target)
> interrupt mask =
> kernel: type 12 trap, code = 0
> Breakpoint at targdone + 0x84: movl %eax, 0x20 (%edx)

It's hard to tell what is happening from just this message.  Are you using
4.x or 5.x?  There have been some changes recently by simokawa-san to
stabilize the usermode of scsi_target in 5.x.  They will eventually be
MFCd.

> 3. machine running "dd" to read/write "FreeBSD Emulated Disk" -- /dev/da0
> report kernel warnings:
>
> Sep 26 12:25:37 IA /kernel: (probe0:ahc0:0:5:0): SCB 0xe - timed out

This is a result of the target panic above.

-Nate