On Tue, Sep 15, 2009 at 10:51 PM, Chris Worley <worl...@gmail.com> wrote: > In lots of testing today, I've seen this panic twice on the Ubuntu 8.10 > targets: > > [ 330.155992] ib_srpt: disconnected session > 0x00247100000000460024710000000046 because a new SRP_LOGIN_REQ has > been received.
The above message means that an initiator logged in, did not log out and logged in again. Has one of the initiator systems e.g. been power cycled while an SRP connection was active ? > [ 357.207046] ib_srpt: srpt_xmit_response: tag= 17 channel in bad state 2 This means that an attempt was made by SRPT to transmit a response for a channel in the state 2 (disconnecting). This must be analyzed further, just like the bug report triggered from srpt_abort_scst_cmd(). [ ... ] > [ 411.636699] WARNING: at /root/scst/srpt/src/ib_srpt.c:924 > srpt_abort_scst_cmd+0xac/0x160 [ib_srpt]() > ... This message has been triggered by the statement WARN_ON("unexpected cmd state"). It must be analyzed whether this is a consequence of what went wrong before or whether this is a separate issue. [ ... ] > This may have been due to low memory, as I was using most target > memory for the ramdisk. The kernel warning message in ib_srpt.c at line 924 should never be triggered, not even under low memory circumstances. I'll have a look at this anyway. Thanks for the detailed report. Bart. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html