Re: qla2xxx Call Trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2014-07-31 at 16:37 -0700, Nicholas A. Bellinger wrote:
> Hi deeepdish,
> 
> Apologies for the delayed response, comments are inline below.
> 
> On Mon, 2014-07-07 at 14:06 -0400, deeepdish wrote:
> > Hello,
> > 
> > I've been able to obtain additional logs.   The call traces pertaining 
> > to tcm_qla2xxx are quite frequent when there's a ESXi (5.5.0 update 1) 
> > connected.
> > 
> > 
> > Jul 07 13:53:21 localhost.localdomain kernel: Updating session ffff8808e8c8e480 from port 50:01:43:80:03:ba:2f:8e loop_id 3 -> 1 s_id 4:a:1 -> 4:a:1
> > Jul 07 13:53:18 localhost.localdomain kernel:  rport-2:0-3: blocked FC remote port time out: removing rport
> > Jul 07 13:53:18 localhost.localdomain kernel:  rport-4:0-3: blocked FC remote port time out: removing rport
> > Jul 07 13:53:16 localhost.localdomain kernel:  rport-4:0-5: blocked FC remote port time out: removing rport
> > Jul 07 13:53:15 localhost.localdomain kernel: ---[ end trace 71a5cd3df560c243 ]---
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae1f0>] ? insert_kthread_work+0x40/0x40
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8170083c>] ret_from_fork+0x7c/0xb0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae1f0>] ? insert_kthread_work+0x40/0x40
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae2d1>] kthread+0xe1/0x100
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a7460>] ? rescuer_thread+0x3b0/0x3b0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a757b>] worker_thread+0x11b/0x3a0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a68e6>] process_one_work+0x176/0x430
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa010b55a>] qlt_del_sess_work_fn+0x8a/0xe0 [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e7791>] tcm_qla2xxx_put_sess+0x41/0x50 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e5b52>] tcm_qla2xxx_release_session+0x12/0x20 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa010a102>] qlt_unreg_sess+0x22/0x80 [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e6ecc>] tcm_qla2xxx_clear_nacl_from_fcport_map+0x16c/0x180 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8108a2fa>] warn_slowpath_null+0x1a/0x20
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff816f0502>] dump_stack+0x45/0x56
> > Jul 07 13:53:15 localhost.localdomain kernel: Call Trace:
> > Jul 07 13:53:15 localhost.localdomain kernel:  ffff8811e0676040 ffff8808ec0b4660 ffff8811ea3c2c40 ffff8811e0676000
> > Jul 07 13:53:15 localhost.localdomain kernel:  0000000000000000 ffff8811dad15d28 ffffffff8108a1cd ffff8811d8ac7280
> > Jul 07 13:53:15 localhost.localdomain kernel:  0000000000000000 0000000037487358 ffff8811dad15cf0 ffffffff816f0502
> > Jul 07 13:53:15 localhost.localdomain kernel: Workqueue: events qlt_del_sess_work_fn [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel: Hardware name: HP ProLiant BL490c G6, BIOS I21 07/02/2013
> > Jul 07 13:53:15 localhost.localdomain kernel: CPU: 0 PID: 1985 Comm: kworker/0:3 Tainted: G        W I  3.14.8-200.fc20.x86_64 #1
> > Jul 07 13:53:15 localhost.localdomain kernel: Modules linked in: tcm_qla2xxx target_core_pscsi target_core_file target_core_iblock iscsi_target_mod target_core_mod team_mode_roundrobin team cfg80211 rfkill iTCO_wdt iTCO_ven
> > Jul 07 13:53:15 localhost.localdomain kernel: WARNING: CPU: 0 PID: 1985 at drivers/scsi/qla2xxx/tcm_qla2xxx.c:710 tcm_qla2xxx_clear_nacl_from_fcport_map+0x16c/0x180 [tcm_qla2xxx]()
> > Jul 07 13:53:15 localhost.localdomain kernel: ------------[ cut here ]------------
> > Jul 07 13:53:15 localhost.localdomain kernel: ---[ end trace 71a5cd3df560c242 ]---
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae1f0>] ? insert_kthread_work+0x40/0x40
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8170083c>] ret_from_fork+0x7c/0xb0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae1f0>] ? insert_kthread_work+0x40/0x40
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810ae2d1>] kthread+0xe1/0x100
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a7460>] ? rescuer_thread+0x3b0/0x3b0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a757b>] worker_thread+0x11b/0x3a0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff810a68e6>] process_one_work+0x176/0x430
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa010b55a>] qlt_del_sess_work_fn+0x8a/0xe0 [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e7791>] tcm_qla2xxx_put_sess+0x41/0x50 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e5b52>] tcm_qla2xxx_release_session+0x12/0x20 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa010a102>] qlt_unreg_sess+0x22/0x80 [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffffa08e6ecc>] tcm_qla2xxx_clear_nacl_from_fcport_map+0x16c/0x180 [tcm_qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8108a2fa>] warn_slowpath_null+0x1a/0x20
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0
> > Jul 07 13:53:15 localhost.localdomain kernel:  [<ffffffff816f0502>] dump_stack+0x45/0x56
> > Jul 07 13:53:15 localhost.localdomain kernel: Call Trace:
> > Jul 07 13:53:15 localhost.localdomain kernel:  ffff8808eaff0840 ffff8808de20d260 ffff8811e8f5d440 ffff8808eaff0800
> > Jul 07 13:53:15 localhost.localdomain kernel:  0000000000000000 ffff8811dad15d28 ffffffff8108a1cd ffff8808ea3d3b00
> > Jul 07 13:53:15 localhost.localdomain kernel:  0000000000000000 0000000037487358 ffff8811dad15cf0 ffffffff816f0502
> > Jul 07 13:53:15 localhost.localdomain kernel: Workqueue: events qlt_del_sess_work_fn [qla2xxx]
> > Jul 07 13:53:15 localhost.localdomain kernel: Hardware name: HP ProLiant BL490c G6, BIOS I21 07/02/2013
> > Jul 07 13:53:15 localhost.localdomain kernel: CPU: 0 PID: 1985 Comm: kworker/0:3 Tainted: G        W I  3.14.8-200.fc20.x86_64 #1
> > Jul 07 13:53:15 localhost.localdomain kernel: Modules linked in: tcm_qla2xxx target_core_pscsi target_core_file target_core_iblock iscsi_target_mod target_core_mod team_mode_roundrobin team cfg80211 rfkill iTCO_wdt iTCO_ven
> > Jul 07 13:53:15 localhost.localdomain kernel: WARNING: CPU: 0 PID: 1985 at drivers/scsi/qla2xxx/tcm_qla2xxx.c:710 tcm_qla2xxx_clear_nacl_from_fcport_map+0x16c/0x180 [tcm_qla2xxx]()
> > Jul 07 13:53:15 localhost.localdomain kernel: ------------[ cut here ]------------
> > Jul 07 13:53:09 localhost.localdomain kernel:  rport-4:0-2: blocked FC remote port time out: removing rport
> > Jul 07 13:53:09 localhost.localdomain kernel:  rport-2:0-0: blocked FC remote port time out: removing rport
> > Jul 07 13:52:58 localhost.localdomain kernel: Updating session ffff8808e8c8e480 from port 50:01:43:80:03:ba:2f:8e loop_id 2 -> 3 s_id 4:b:1 -> 4:a:1
> > Jul 07 13:52:57 localhost.localdomain kernel: Updating session ffff8808e8c8e680 from port 50:01:43:80:03:ba:2f:8c loop_id 1 -> 3 s_id 3:b:1 -> 3:a:1
> > 
> > 
> 
> Would it be possible to obtain target side logs with the following debug
> bits enabled..?  The first involves enabling qla2xxx debugging at
> modprobe qla2xxx time with:
> 
>   modprobe qla2xxx ql2xextended_error_logging=0x1e40f000
> 
> and the second is enabling tcm_qla2xxx debugging (via debugfs +
> CONFIG_DYNAMIC_DEBUG=y) with:
>   
>   echo 'module tcm_qla2xxx +p' > /debug/dynamic_debugging/control
> 
> Having the logs with both of these debug bits enabled would be very
> helpful in pinpointing the issue.
> 
> Also, adding CC' for Roland + Joern, as they where the last ones to
> touched this specific piece of code..
> 
> Roland + Joern, I know that at some point you had converted from btree
> -> radix trees due to some issues in lib/btree.c code, but never pushed
> this conversion patch for tcm_qla2xxx upstream.  Can you give an idea of
> what caused to conversion to radix trees, and if the bug reported here
> is similar..?
> 

Roland + Joern, I'm specifically talking about the following patches:

https://github.com/rolandd/qla-target/commit/77bd729e5e9f858495dfded7c08e548bc9ecc9be
https://github.com/rolandd/qla-target/commit/79ae07a141950c0008480a46f91d72318a1d799e

Can you please confirm if these are related to what deeepdish has
reported here..?

Thanks,

--nab

--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux