Kamil Kisiel wrote:
> I'm running open-iscsi-2.0.868 on a Linux 2.6.21 Xen DomU kernel. I


was this open-iscsi-2.0.868 test1 or rc1?


> find that when doing heavy I/O, particularly between two iSCSI
> targets, I receive the following messages in my kernel log:
> 
> Apr 10 10:23:07 mucilage BUG: scheduling while atomic:
> scsi_wq_5/0x10000001/7047
> Apr 10 10:23:07 mucilage
> Apr 10 10:23:07 mucilage Call Trace:
> Apr 10 10:23:07 mucilage [<ffffffff805d9e8e>] __sched_text_start+0x5e/
> 0x873
> Apr 10 10:23:07 mucilage [<ffffffff8022ecd5>] local_bh_enable+0x7c/
> 0xa5
> Apr 10 10:23:07 mucilage [<ffffffff8057f8c5>] dev_queue_xmit
> +0x237/0x25a
> Apr 10 10:23:07 mucilage [<ffffffff805958de>] ip_queue_xmit
> +0x378/0x3cd
> Apr 10 10:23:07 mucilage [<ffffffff8024fc50>] get_page_from_freelist
> +0x81/0x3d5
> Apr 10 10:23:07 mucilage [<ffffffff802241f1>] __cond_resched+0x1c/0x44
> Apr 10 10:23:07 mucilage [<ffffffff805da851>] cond_resched+0x2e/0x39
> Apr 10 10:23:07 mucilage [<ffffffff80575da4>] lock_sock_nested
> +0x16/0xb2
> Apr 10 10:23:07 mucilage [<ffffffff805dc435>] _spin_lock_bh+0x9/0x19
> Apr 10 10:23:07 mucilage [<ffffffff8059abcd>] tcp_sendmsg+0x1e/0xa71
> Apr 10 10:23:07 mucilage [<ffffffff80574189>] sock_sendmsg+0xcb/0xe3
> Apr 10 10:23:07 mucilage [<ffffffff8023c743>] autoremove_wake_function
> +0x0/0x2e
> Apr 10 10:23:07 mucilage [<ffffffff805a5536>] __tcp_push_pending_frames
> +0x53a/0x88e
> Apr 10 10:23:07 mucilage [<ffffffff805798c4>] __alloc_skb+0x75/0x134
> Apr 10 10:23:07 mucilage [<ffffffff805dc435>] _spin_lock_bh+0x9/0x19
> Apr 10 10:23:07 mucilage [<ffffffff80575cf7>] release_sock+0x13/0xaa
> Apr 10 10:23:07 mucilage [<ffffffff805752ca>] kernel_sendmsg+0x2c/0x3e
> Apr 10 10:23:07 mucilage [<ffffffff8801c2c6>]
> Apr 10 10:23:07 mucilage [<ffffffff805dcc57>] error_exit+0x0/0x79
> Apr 10 10:23:07 mucilage [<ffffffff805da6a3>] thread_return+0x0/0x137
> Apr 10 10:23:07 mucilage [<ffffffff8801c985>]
> Apr 10 10:23:07 mucilage
> [<ffffffff88015796>] :libiscsi:iscsi_free_mgmt_task+0x12d/0x318
> Apr 10 10:23:07 mucilage
> [<ffffffff8801642a>] :libiscsi:iscsi_conn_teardown+0x66a/0x7d3
> Apr 10 10:23:07 mucilage
> [<ffffffff88016026>] :libiscsi:iscsi_conn_teardown+0x266/0x7d3
> Apr 10 10:23:07 mucilage [<ffffffff80238dcc>] run_workqueue+0x8f/0x137
> Apr 10 10:23:07 mucilage [<ffffffff8023973a>] worker_thread+0x0/0x11f
> Apr 10 10:23:07 mucilage [<ffffffff8023c3c6>] keventd_create_kthread
> +0x0/0x65
> Apr 10 10:23:07 mucilage [<ffffffff80239827>] worker_thread+0xed/0x11f
> Apr 10 10:23:07 mucilage [<ffffffff80223cff>] default_wake_function
> +0x0/0xe
> Apr 10 10:23:07 mucilage [<ffffffff8023c61c>] kthread+0xd1/0x101
> Apr 10 10:23:07 mucilage [<ffffffff8020a008>] child_rip+0xa/0x12
> Apr 10 10:23:07 mucilage [<ffffffff8023c3c6>] keventd_create_kthread
> +0x0/0x65
> Apr 10 10:23:07 mucilage [<ffffffff8023c54b>] kthread+0x0/0x101
> Apr 10 10:23:07 mucilage [<ffffffff80209ffe>] child_rip+0x0/0x12
> 

The trace looks a little strange.

At this time, are you doing any other management operations like 
shutting down a session?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to