Richard wrote: > 71686 Sep 26 22:36:47 linux-j2cx kernel: connection1:0: iscsi: > detected conn error (1011) > 71687 Sep 26 22:36:48 linux-j2cx iscsid: poll result 1 > 71688 Sep 26 22:36:48 linux-j2cx iscsid: in ctldev_handle > 71689 Sep 26 22:36:48 linux-j2cx iscsid: in nl_read > 71690 Sep 26 22:36:48 linux-j2cx iscsid: ctldev_handle got event type > 102 > 71691 Sep 26 22:36:48 linux-j2cx iscsid: get conn context 0x63ad00 > 71692 Sep 26 22:36:48 linux-j2cx iscsid: message real length is 72 > bytes, recv_handle 0x63c600 > 71693 Sep 26 22:36:48 linux-j2cx iscsid: in nlpayload_read > 71694 Sep 26 22:36:48 linux-j2cx iscsid: sched conn context 0x63ad00 > event 3, tmo 0 > 71695 Sep 26 22:36:48 linux-j2cx iscsid: thread 0x63ad00 schedule: > delay 0 state 3 > 71696 Sep 26 22:36:48 linux-j2cx iscsid: exec thread 0063ad00 callback > 71697 Sep 26 22:36:48 linux-j2cx iscsid: Kernel reported iSCSI > connection 1:0 error (1011) state (3)
I am sorry to make this difficult, but I need a little before this. I am looking for the, "can not send nopin respons" message and then the stuff before that. There might be something like: expecting event %d, got %d, handling... (here %d is some num) or: Recieved iferror %d: %s", where %d is a error and %s is message like no mem or invalid param. or you might see soemthing like: send's begin state machine bug? or send's end state machine bug?" or send's end state machine corruption? or bad event: bug on send_pdu_end? Are you comfortatble applying patches? If so I can send a patch to just print exactly what I need, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
