[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #14 from himanshu.madh...@cavium.com --- I am OOO. I will respond to your message when i am back at work. Thanks, Himanshu -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 Anthony (anthony.blood...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |CODE_FIX --- Comment #13 from Anthony (anthony.blood...@gmail.com) --- Patch in upstream now. Please close the bug. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #12 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) --- (In reply to loberman from comment #11) > - Original Message - > > From: "Laurence Oberman" <lober...@redhat.com> > > To: bugzilla-dae...@bugzilla.kernel.org > > Cc: linux-s...@kernel.org > > Sent: Thursday, May 18, 2017 2:11:43 PM > > Subject: Re: [Bug 195285] qla2xxx FW immediatly crashing after target start > > > > > > > > - Original Message - > > > From: bugzilla-dae...@bugzilla.kernel.org > > > To: linux-s...@kernel.org > > > Sent: Thursday, May 18, 2017 2:09:51 PM > > > Subject: [Bug 195285] qla2xxx FW immediatly crashing after target start > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=195285 > > > > > > --- Comment #6 from himanshu.madh...@cavium.com > > > (himanshu.madh...@qlogic.com) > > > --- > > > Hi Anthony, Laurence, > > > > > > Can you try attached patch to see if it works for you? > > > > > > if Yes, I'll send out to SCSI mailing list to be included into upstream. > > > > > > Thanks, > > > Himanshu > > > > > > -- > > > You are receiving this mail because: > > > You are watching the assignee of the bug. > > > > > Absolutely, and thanks > > Regards > > Laurence > > Its working fine for me too now > Thanks!! > Laurence Thanks Laurence. Appreciate your effort on testing this out. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #11 from lober...@redhat.com --- - Original Message - > From: "Laurence Oberman" <lober...@redhat.com> > To: bugzilla-dae...@bugzilla.kernel.org > Cc: linux-s...@kernel.org > Sent: Thursday, May 18, 2017 2:11:43 PM > Subject: Re: [Bug 195285] qla2xxx FW immediatly crashing after target start > > > > - Original Message - > > From: bugzilla-dae...@bugzilla.kernel.org > > To: linux-s...@kernel.org > > Sent: Thursday, May 18, 2017 2:09:51 PM > > Subject: [Bug 195285] qla2xxx FW immediatly crashing after target start > > > > https://bugzilla.kernel.org/show_bug.cgi?id=195285 > > > > --- Comment #6 from himanshu.madh...@cavium.com > > (himanshu.madh...@qlogic.com) > > --- > > Hi Anthony, Laurence, > > > > Can you try attached patch to see if it works for you? > > > > if Yes, I'll send out to SCSI mailing list to be included into upstream. > > > > Thanks, > > Himanshu > > > > -- > > You are receiving this mail because: > > You are watching the assignee of the bug. > > > Absolutely, and thanks > Regards > Laurence Its working fine for me too now Thanks!! Laurence -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #10 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) --- Hi Anthony, (In reply to Anthony from comment #9) > patch work fine on 4.12.0-0.rc1 with ql2xmqsupport enabled Thanks for validation. I'll send this patch to scsi tree with proper tags. -Himanshu -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #9 from Anthony (anthony.blood...@gmail.com) --- patch work fine on 4.12.0-0.rc1 with ql2xmqsupport enabled -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #8 from lober...@redhat.com --- - Original Message - > From: bugzilla-dae...@bugzilla.kernel.org > To: linux-s...@kernel.org > Sent: Thursday, May 18, 2017 2:09:51 PM > Subject: [Bug 195285] qla2xxx FW immediatly crashing after target start > > https://bugzilla.kernel.org/show_bug.cgi?id=195285 > > --- Comment #6 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) > --- > Hi Anthony, Laurence, > > Can you try attached patch to see if it works for you? > > if Yes, I'll send out to SCSI mailing list to be included into upstream. > > Thanks, > Himanshu > > -- > You are receiving this mail because: > You are watching the assignee of the bug. > Absolutely, and thanks Regards Laurence -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #7 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) --- Created attachment 256619 --> https://bugzilla.kernel.org/attachment.cgi?id=256619=edit Patch to address target configuration for ISP25xx -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #6 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) --- Hi Anthony, Laurence, Can you try attached patch to see if it works for you? if Yes, I'll send out to SCSI mailing list to be included into upstream. Thanks, Himanshu -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #5 from lober...@redhat.com --- - Original Message - > From: bugzilla-dae...@bugzilla.kernel.org > To: linux-s...@kernel.org > Sent: Tuesday, May 16, 2017 10:45:22 AM > Subject: [Bug 195285] qla2xxx FW immediatly crashing after target start > > https://bugzilla.kernel.org/show_bug.cgi?id=195285 > > --- Comment #4 from Anthony (anthony.blood...@gmail.com) --- > I'm trying to select working setting, and some investigation shows: > with parameter ql2xmqsupport=0 - target starting to work > > -- > You are receiving this mail because: > You are watching the assignee of the bug. > OK, I default to MQ so will look at testing without it later. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #4 from Anthony (anthony.blood...@gmail.com) --- I'm trying to select working setting, and some investigation shows: with parameter ql2xmqsupport=0 - target starting to work -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #3 from Anthony (anthony.blood...@gmail.com) --- Two cards installed in new test machine: QLE2462 and QLE2560 qle2560 spam with errors (without starting a target) scsi host8: qla2xxx qla2xxx [:05:00.1]-00fb:8: QLogic QLE2462 - PCI-Express Dual Channel 4Gb Fibre Channel HBA. qla2xxx [:05:00.1]-00fc:8: ISP2432: PCIe (2.5GT/s x4) @ :05:00.1 hdma+ host#=8 fw=8.06.00 (9496). qla2xxx [:09:00.0]-001a: : MSI-X vector count: 32. qla2xxx [:09:00.0]-001d: : Found an ISP2532 irq 16 iobase 0xba4886335000. qla2xxx [:09:00.0]-504b:9: RISC paused -- HCCR=40, Dumping firmware. qla2xxx [:09:00.0]-d001:9: Firmware dump saved to temp buffer (9/ba488c001000), dump status flags (0x3f). qla2xxx [:09:00.0]-1005:9: Cmd 0x59 aborted with timeout since ISP Abort is pending scsi host9: qla2xxx qla2xxx [:09:00.0]-00fb:9: QLogic QLE2560 - PCI-Express Single Channel 8Gb Fibre Channel HBA. qla2xxx [:09:00.0]-00fc:9: ISP2532: PCIe (5.0GT/s x8) @ :09:00.0 hdma+ host#=9 fw=8.06.00 (90d5). qla2xxx [:05:00.0]-500a:7: LOOP UP detected (4 Gbps). qla2xxx [:05:00.1]-500a:8: LOOP UP detected (4 Gbps). qla2xxx [:09:00.0]-00af:9: Performing ISP error recovery - ha=98315ee3. qla2xxx [:09:00.0]-504b:9: RISC paused -- HCCR=40, Dumping firmware. qla2xxx [:09:00.0]-d009:9: Firmware has been previously dumped (ba488c001000) -- ignoring request. qla2xxx [:09:00.0]-504b:9: RISC paused -- HCCR=40, Dumping firmware. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 --- Comment #2 from Anthony (anthony.blood...@gmail.com) --- All my test and and production environments a the same: on tagret: RAID controller (HP SmartArray / Adaptec 65xx) BCache in writeback mode on Intel SSD NVME QLE2564 in target mode on initiator QLE2562 optical patches 1 meter (MM) without FC switch -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 195285] qla2xxx FW immediatly crashing after target start
https://bugzilla.kernel.org/show_bug.cgi?id=195285 himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) changed: What|Removed |Added CC||himanshu.madh...@qlogic.com --- Comment #1 from himanshu.madh...@cavium.com (himanshu.madh...@qlogic.com) --- Hi Anthony, (In reply to Anthony from comment #0) > System always become unresposive after target start with messages > > qla2xxx [:07:00.0]-00fb:1: QLogic QLE2564 - PCI-Express Quad Channel 8Gb > Fibre Channel HBA. > qla2xxx [:07:00.0]-00fc:1: ISP2532: PCIe (5.0GT/s x8) @ :07:00.0 > hdma+ host#=1 fw=8.06.00 (90d5). > qla2xxx [:07:00.1]-001a: : MSI-X vector count: 32. > qla2xxx [:07:00.1]-001d: : Found an ISP2532 irq 103 iobase > 0xb830c62d5000. > qla2xxx [:07:00.1]-504b:2: RISC paused -- HCCR=40, Dumping firmware. > qla2xxx [:07:00.1]-8033:2: Unable to reinitialize FCE (258). > qla2xxx [:07:00.1]-8034:2: Unable to reinitialize EFT (258). > qla2xxx [:07:00.1]-00af:2: Performing ISP error recovery - > ha=88a2624e. > qla2xxx [:07:00.1]-504b:2: RISC paused -- HCCR=40, Dumping firmware. > > trying - kernel 4.11-rc5 > > Apr 07 23:39:58 : [ cut here ] > Apr 07 23:39:58 : WARNING: CPU: 0 PID: 1468 at lib/dma-debug.c:519 > add_dma_entry+0x176/0x180 > Apr 07 23:39:58 : DMA-API: exceeded 7 overlapping mappings of cacheline > 0x13e77000 > Apr 07 23:39:58 : Modules linked in: vhost_net vhost tap tun ebtable_filter > ebtables ip6table_filter ip6_tables tcm_qla2xxx target_core_user uio targ > Apr 07 23:39:58 : nvme_core scsi_transport_sas > Apr 07 23:39:58 : CPU: 0 PID: 1468 Comm: qemu-system-x86 Tainted: GW > I 4.11.0-0.rc5.git3.1.fc27.x86_64 #1 > Apr 07 23:39:58 : Hardware name: HP ProLiant DL180 G6 , BIOS O20 07/01/2013 > Apr 07 23:39:58 : Call Trace: > Apr 07 23:39:58 : dump_stack+0x8e/0xd1 > Apr 07 23:39:58 : __warn+0xcb/0xf0 > Apr 07 23:39:58 : warn_slowpath_fmt+0x5a/0x80 > Apr 07 23:39:58 : ? active_cacheline_read_overlap+0x2e/0x60 > Apr 07 23:39:58 : add_dma_entry+0x176/0x180 > Apr 07 23:39:58 : debug_dma_map_sg+0x11a/0x170 > Apr 07 23:39:58 : nvme_queue_rq+0x513/0x950 [nvme] > Apr 07 23:39:58 : blk_mq_try_issue_directly+0xbb/0x110 > Apr 07 23:39:58 : blk_mq_make_request+0x3a9/0xa70 > Apr 07 23:39:58 : ? blk_queue_enter+0xa3/0x2c0 > Apr 07 23:39:58 : ? blk_queue_enter+0x39/0x2c0 > Apr 07 23:39:58 : ? generic_make_request+0xf9/0x3b0 > Apr 07 23:39:58 : generic_make_request+0x126/0x3b0 > Apr 07 23:39:58 : ? iov_iter_get_pages+0xc9/0x330 > Apr 07 23:39:58 : submit_bio+0x73/0x150 > Apr 07 23:39:58 : ? submit_bio+0x73/0x150 > Apr 07 23:39:58 : ? bio_iov_iter_get_pages+0xe0/0x120 > Apr 07 23:39:58 : blkdev_direct_IO+0x1f7/0x3e0 > Apr 07 23:39:58 : ? SYSC_io_destroy+0x1d0/0x1d0 > Apr 07 23:39:58 : ? __atime_needs_update+0x7f/0x1a0 > Apr 07 23:39:58 : generic_file_read_iter+0x2e5/0xad0 > Apr 07 23:39:58 : ? generic_file_read_iter+0x2e5/0xad0 > Apr 07 23:39:58 : ? rw_copy_check_uvector+0x8a/0x180 > Apr 07 23:39:58 : blkdev_read_iter+0x35/0x40 > Apr 07 23:39:58 : aio_read+0xeb/0x150 > Apr 07 23:39:58 : ? sched_clock+0x9/0x10 > Apr 07 23:39:58 : ? sched_clock_cpu+0x11/0xc0 > Apr 07 23:39:58 : ? __might_fault+0x3e/0x90 > Apr 07 23:39:58 : ? __might_fault+0x3e/0x90 > Apr 07 23:39:58 : do_io_submit+0x5f8/0x920 > Apr 07 23:39:58 : ? do_io_submit+0x5f8/0x920 > Apr 07 23:39:58 : SyS_io_submit+0x10/0x20 > Apr 07 23:39:58 : ? SyS_io_submit+0x10/0x20 > Apr 07 23:39:58 : entry_SYSCALL_64_fastpath+0x1f/0xc2 > Apr 07 23:39:58 : RIP: 0033:0x7f73766216a7 > Apr 07 23:39:58 : RSP: 002b:7ffc9aac6108 EFLAGS: 0246 ORIG_RAX: > 00d1 > Apr 07 23:39:58 : RAX: ffda RBX: 55617d90b900 RCX: > 7f73766216a7 > Apr 07 23:39:58 : RDX: 7ffc9aac6120 RSI: 0002 RDI: > 7f737780 > Apr 07 23:39:58 : RBP: 0258 R08: 7ffc9aac6440 R09: > 55617d9a2000 > Apr 07 23:39:58 : R10: 556188f93cf0 R11: 0246 R12: > 0280 > Apr 07 23:39:58 : R13: 0130 R14: 0001 R15: > 0011 > Apr 07 23:39:58 : ---[ end trace 81f169903702b67d ]--- We are working internally to reproduce this issue. we'll report what we find out from reproduction. Thanks, Himanshu -- You are receiving this mail because: You are watching the assignee of the bug.
