FUJITA Tomonori schrieb:
On Wed, 17 Dec 2008 16:09:58 +0100
Tomasz Chmielewski <mangoo@xxxxxxxx> wrote:
Tomasz Chmielewski schrieb:
FUJITA Tomonori schrieb:
Which will result in:
Dec 16 13:55:32 megathecus kernel: tgtd[4872]: segfault at 00000220
eip 0804f0b5 esp 77c43ff0 error 4
Hmm, unfortunately, I can't reproduce this.
Strange, it is 100% reproducible here, on a x86 system. I didn't try 64
bit.
I just do dmsetup suspend / wait a few seconds / dmsetup resume, while
the initiator is reading data, and tgtd segfaults.
It crashes if I wait about 120 seconds or more.
If I wait less, it does not crash.
I made sure that I wait about 120 seconds but I can't reproduce this
(it takes about 120 seconds to see the abort and close messages in the
log.
We should not see a series of 'conn_close' messages. Something
unexpected happens at your box.
Can you try this and send the log? It doesn't fix the problem but
gives more information.
Does it help?
Dec 17 16:50:25 megathecus tgtd: abort_task_set(988) found e0000a02 0
Dec 17 16:50:25 megathecus tgtd: iscsi_tcp_event_handler(167) connection closed 0x807028c
Dec 17 16:50:25 megathecus tgtd: conn_close(90) connection closed 0x807028c 2 0 11
Dec 17 16:50:28 megathecus tgtd: conn_close(90) connection closed 0x807028c 1 0 11
Dec 17 16:51:27 megathecus tgtd: abort_task_set(988) found f0000a06 0
Dec 17 16:51:27 megathecus tgtd: iscsi_tcp_event_handler(167) connection closed 0x807028c
Dec 17 16:51:27 megathecus tgtd: conn_close(90) connection closed 0x807028c 2 0 11
Dec 17 16:51:30 megathecus tgtd: conn_close(90) connection closed 0x807028c 1 0 11
Dec 17 16:51:54 megathecus kernel: tgtd[19616]: segfault at 000001e4 eip 0804c2da esp 77c8b430 error 4
--
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
