FUJITA Tomonori schrieb:
If you could provide me some "debug" version of tgtd, maybe?
The following message showed up _after_ the segfault, right?
Did you see any message _before_ the segfault?
Once again - I connected the initiator at about 10:27, started copying the files.
Before the segfault there were messages below (this target has 3 connected initiators from
2 machines / IP addresses).
Hope it helps, let me know if you need any more info.
Feb 3 10:27:05 superthecus tgtd: conn_close(88) connection closed 0x8523e04 1
Feb 3 10:27:33 superthecus tgtd: conn_close(88) connection closed 0x8523e04 1
Feb 3 10:29:50 superthecus tgtd: conn_close(88) connection closed 0x8523e04 30
Feb 3 10:29:50 superthecus tgtd: conn_close(133) Forcing release of rx task 0x8574478 41
Feb 3 10:30:26 superthecus tgtd: conn_close(88) connection closed 0x857447c 31
Feb 3 10:30:26 superthecus tgtd: conn_close(133) Forcing release of rx task 0x8590010 10000054
Feb 3 10:31:22 superthecus tgtd: conn_close(88) connection closed 0x8590014 32
Feb 3 10:31:22 superthecus tgtd: conn_close(133) Forcing release of rx task 0x85bcd58 20000006
Feb 3 10:32:10 superthecus kernel: tgtd[7750]: segfault at 28 ip 0805814f sp 7780bfa0 error 4 in tgtd (deleted)[8048000+23000]
Feb 3 10:32:10 superthecus tgtd: conn_close(88) connection closed 0x85e3e04 33
Feb 3 10:32:10 superthecus tgtd: conn_close(115) Forcing release of tx task 0x8644d58 30000017 1
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
