On 08/08/2012 04:42 AM, Fubo Chen wrote:
> Anyone seen this before ? Also occurs with 3.4.1.
> 
> 
> ======================================================
> [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ]
> 3.6.0-rc1-debug+ #1 Not tainted
> ------------------------------------------------------
> swapper/1/0 [HC0[0]:SC1[1]:HE0:SE0] is trying to acquire:
>  (&(&session->lock)->rlock){+.-...}, at: [<ffffffffa025dc08>]
> iscsi_eh_cmd_timed_out+0x58/0x2e0 [libiscsi]

I have not seen this before, but lock stuff above looks like it is
detecting a bug. Not sure if something changed or if it was always this
way. I will dig into the git commits some more and come up with a patch.

Thanks for the report.

-- 
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 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to