|
| 	Update on this - I believe the SCSI to be a false alarm.
| 	The hang happened again with no reference to esp in dmesg, and
| 	the same netbsd32_read()...soreceive() in the syscall trace.
| 	Looks like there might be something suspect in the netbsd32()
| 	socket code?

That could well be the case.

| > | zsc_intr_hard()
| > | zshard()
| > | intr_list_handler()
| > | sparc_intr_retry(5a35ec8f, 0, 5a35ec8c, 2182620, 0, ffffffff) at sparc_intr_retry+0x48

In this case I would recommend dumping the trapframe where you took this
interrupt, which should be the 3rd argument... but the values don't seem 
right.  The interrupt stack should be around e0010000, and you have values
around 5a35ec8c, which isn't even 16-bit aligned.  What version of the 
kernel did you say this was?

| > | soreceive(216de80, 1854040, eb85ac0, 2182620, 0, 18540b8) at soreceive+0x7b4
| > | soo_read(893d70, e893da0, eb85ac0, 2170d00, 1, 104f420) at soo_read+0x20
| > | dofileread(e8a16b0, b, 8903d70, fffffffd, fffffffd, e893da0) at dofileread+0x8c
| > | sys_read(e8a16b0,  eb85c80, eb85dc0, fffffffd, 0, ffffb090) at sys_read+0x58
| > | netbsd32_read(e8a16b0, eb85dd0, eb85dc0, 1152760, 800, 1) at netbsd32_read+0x24
| > | syscall(eb85ed0, 3, 0, 40c515d4, 0, 775) at syscall+0x304
| > | syscall_setup(b, ffffb68b, fffffffd, 23, f75800, 1) at syscall_setup+0x12c

Eduardo