[Bug 466431] New: lpfc module with Emulex Corporation Helios-X LightPulse Fibre Channel Adapter (rev 01) [LP11002] not working
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c1 Summary: lpfc module with Emulex Corporation Helios-X LightPulse Fibre Channel Adapter (rev 01) [LP11002] not working Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kristjan.eentsalu@err.ee QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 During lpfc module load it throws out errors and card does not work. I loaded the module with options lpfc_log_verbose=0xffff HBA: Emulex Corporation Helios-X LightPulse Fibre Channel Adapter (rev 01) [LP11002] Kernel version: 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux lpfc module version: version: 0:8.2.8.7 This is the error: lpfc 0000:09:06.0: PCI INT A -> GSI 31 (level, low) -> IRQ 31 lpfc 0000:09:06.0: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.0: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:0462 PCI enable MSI mode success. lpfc 0000:09:06.0: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.0: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.0: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:0455 Vital Product Data: x82 x21 x0 x48 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x88 issue Data: x0 x100 x1 lpfc 0000:09:06.0: 0:0444 Firmware in SLI 2 mode. Max_vpi 0 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x21 issue Data: x0 x300 x1 lpfc 0000:09:06.0: 0:0:0443 Adapter failed to set maximum DMA length mbxStatus x0 lpfc 0000:09:06.0: 0:(0):0309 Mailbox cmd x9 issue Data: x0 x300 x1 lpfc 0000:09:06.0: 0:0446 Adapter failed to init (255), mbxCmd x9 CFG_RING, mbxStatus x0, ring 0 lpfc 0000:09:06.0: 0:0445 Firmware initialization failed lpfc 0000:09:06.0: 0:1477 Failed to set up hba lpfc 0000:09:06.0: 0:(0):0248 Cancel Discovery Timer state x0 Data: x80000 x0 x0 lpfc 0000:09:06.0: 0:(0):0248 Cancel Discovery Timer state x0 Data: x80000 x0 x0 lpfc 0000:09:06.0: 0:0337 Restart HBA Data: x0 x200 lpfc 0000:09:06.0: 0:0325 Reset HBA Data: x0 x200 lpfc 0000:09:06.0: 0:0432 Worker thread stopped. lpfc 0000:09:06.0: PCI INT A disabled lpfc 0000:09:06.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34 lpfc 0000:09:06.1: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.1: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:0462 PCI enable MSI mode success. lpfc 0000:09:06.1: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.1: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:0337 Restart HBA Data: x0 x100 lpfc 0000:09:06.1: 0:0325 Reset HBA Data: x0 x100 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x11 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x17 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:0455 Vital Product Data: x82 x21 x0 x48 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x88 issue Data: x0 x100 x1 lpfc 0000:09:06.1: 0:0444 Firmware in SLI 2 mode. Max_vpi 0 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x21 issue Data: x0 x300 x1 lpfc 0000:09:06.1: 0:0:0443 Adapter failed to set maximum DMA length mbxStatus x0 lpfc 0000:09:06.1: 0:(0):0309 Mailbox cmd x9 issue Data: x0 x300 x1 lpfc 0000:09:06.1: 0:0446 Adapter failed to init (255), mbxCmd x9 CFG_RING, mbxStatus x0, ring 0 lpfc 0000:09:06.1: 0:0445 Firmware initialization failed lpfc 0000:09:06.1: 0:1477 Failed to set up hba lpfc 0000:09:06.1: 0:(0):0248 Cancel Discovery Timer state x0 Data: x80000 x0 x0 lpfc 0000:09:06.1: 0:(0):0248 Cancel Discovery Timer state x0 Data: x80000 x0 x0 lpfc 0000:09:06.1: 0:0337 Restart HBA Data: x0 x200 lpfc 0000:09:06.1: 0:0325 Reset HBA Data: x0 x200 lpfc 0000:09:06.1: 0:0432 Worker thread stopped. lpfc 0000:09:06.1: PCI INT B disabled Also tried it with ubuntu 8.10 and it worked fine, there the lpfc module version was 8.2.7 Kristjan Reproducible: Always Steps to Reproduce: 1. Happens every time when I load lpfc module -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |hare@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User hare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c1 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |james.smart@emulex.com --- Comment #1 from Hannes Reinecke <hare@novell.com> 2009-01-22 01:28:29 MST --- James, can you help here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c2 James Smart <james.smart@emulex.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |james.smart@emulex.com --- Comment #2 from James Smart <james.smart@emulex.com> 2009-01-22 09:40:43 MST --- I'm guessing this is due to a change that was made to set the PCI max_read length. See the routine lpfc_sli_set_dma_length. This was done for a particular OEM whose platform couldn't do the right thing in config space. Anyway - the command that is issued, SET_VARIABLE, is supposed to be innoculous on f/w that doesn't recognize it. However, it appears that the command is never completing, and is in fact hanging the adapter. To verify, noop this function and see if board init completes. First - please specify information about the adapter: the firmware revision information lspci information Second - update the adapter to the latest firmware and see if the symptom changes. Once I have the results from these 2 steps, we can formulate what our risk is and how to address it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c3 --- Comment #3 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-23 00:55:37 MST --- firmware versions: boot code 1.70a3 firmware 2.10a10 lspci -v output: 00:00.0 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset) (rev 33) Flags: fast devsel Kernel modules: sworks-agp 00:00.1 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset) Flags: fast devsel Kernel modules: sworks-agp 00:00.2 Host bridge: Broadcom CMIC-LE Host Bridge (GC-LE chipset) Flags: fast devsel Kernel modules: sworks-agp 00:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA controller]) Subsystem: IBM Device 0240 Flags: bus master, stepping, medium devsel, latency 64, IRQ 10 Memory at fd000000 (32-bit, non-prefetchable) [size=16M] I/O ports at 2200 [size=256] Memory at febff000 (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 88000000 [disabled] [size=128K] Capabilities: [5c] Power Management version 2 00:0f.0 Host bridge: Broadcom CSB5 South Bridge (rev 93) Subsystem: Broadcom CSB5 South Bridge Flags: bus master, medium devsel, latency 64 Kernel driver in use: piix4_smbus Kernel modules: i2c-piix4, sworks-agp 00:0f.1 IDE interface: Broadcom CSB5 IDE Controller (rev 93) (prog-if 82 [Master PriP]) Subsystem: Broadcom CSB5 IDE Controller Flags: bus master, medium devsel, latency 64 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at 0700 [size=16] Kernel driver in use: Serverworks_IDE Kernel modules: serverworks 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) (prog-if 10 [OHCI]) Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at febfe000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:0f.3 ISA bridge: Broadcom CSB5 LPC bridge Subsystem: Broadcom Device 0230 Flags: bus master, medium devsel, latency 0 00:10.0 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05) Flags: 66MHz, medium devsel Capabilities: [60] PCI-X non-bridge device Kernel modules: sworks-agp 00:10.2 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05) Flags: 66MHz, medium devsel Capabilities: [60] PCI-X non-bridge device Kernel modules: sworks-agp 00:11.0 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05) Flags: 66MHz, medium devsel Capabilities: [60] PCI-X non-bridge device Kernel modules: sworks-agp 00:11.2 Host bridge: Broadcom CIOB-X2 PCI-X I/O Bridge (rev 05) Flags: 66MHz, medium devsel Capabilities: [60] PCI-X non-bridge device Kernel modules: sworks-agp 02:08.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) Subsystem: IBM Device 026f Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 29 Memory at fbff0000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] PCI-X non-bridge device Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data <?> Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable- Kernel driver in use: tg3 Kernel modules: tg3 05:03.0 RAID bus controller: Adaptec ServeRAID Controller (rev 02) Subsystem: IBM ServeRAID-xx Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 22 Memory at f3fff000 (32-bit, non-prefetchable) [size=4K] Memory at f4000000 (32-bit, prefetchable) [size=64M] [virtual] Expansion ROM at 88080000 [disabled] [size=512K] Capabilities: [c0] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable- Capabilities: [e0] PCI-X non-bridge device Kernel driver in use: ips Kernel modules: ips 07:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) Subsystem: Broadcom Corporation NetXtreme BCM5703 1000Base-T Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 24 Memory at f1ff0000 (64-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at 88020000 [disabled] [size=64K] Capabilities: [40] PCI-X non-bridge device Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data <?> Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable- Kernel driver in use: tg3 Kernel modules: tg3 09:06.0 Fibre Channel: Emulex Corporation Helios-X LightPulse Fibre Channel Host Adapter (rev 01) Subsystem: Emulex Corporation Helios-X LightPulse Fibre Channel Host Adapter Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 31 Memory at ef3ff000 (64-bit, non-prefetchable) [size=4K] Memory at ef3fec00 (64-bit, non-prefetchable) [size=256] I/O ports at a000 [size=256] [virtual] Expansion ROM at 88040000 [disabled] [size=256K] Capabilities: [5c] Power Management version 2 Capabilities: [64] Message Signalled Interrupts: Mask- 64bit+ Queue=0/4 Enable- Capabilities: [74] Vital Product Data <?> Capabilities: [44] PCI-X non-bridge device Kernel driver in use: lpfc Kernel modules: lpfc 09:06.1 Fibre Channel: Emulex Corporation Helios-X LightPulse Fibre Channel Host Adapter (rev 01) Subsystem: Emulex Corporation Helios-X LightPulse Fibre Channel Host Adapter Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 34 Memory at ef3fd000 (64-bit, non-prefetchable) [size=4K] Memory at ef3fe800 (64-bit, non-prefetchable) [size=256] I/O ports at a100 [size=256] [virtual] Expansion ROM at 88100000 [disabled] [size=256K] Capabilities: [5c] Power Management version 2 Capabilities: [64] Message Signalled Interrupts: Mask- 64bit+ Queue=0/4 Enable- Capabilities: [74] Vital Product Data <?> Capabilities: [44] PCI-X non-bridge device Kernel driver in use: lpfc Kernel modules: lpfc I'll try to update firmware then....under debian somehow Kristjan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c4 --- Comment #4 from James Smart <james.smart@emulex.com> 2009-01-23 07:46:54 MST --- OK. The link for firmware for the 11002 is : http://www.emulex.com/support/hardware/lpe11002/lpe11002.jsp F/W update is more difficult as the tools are paired with the driver rev, and we only ship tools for the major distros (SUSE, Red Hat). (yeah, I know, I'd like this to be different too). You'll likely have to move it to another system with say SLES10 SP2, and the tools/latest driver kits are on the emulex web page: http://www.emulex.com/support/linux/index.jsp keep me posted if I can help further. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c5 --- Comment #5 from James Smart <james.smart@emulex.com> 2009-01-23 08:15:48 MST --- One other idea - as this is mucking with the PCI read data size, and the adapter is actually built with a bridge chip on it, perhaps there's something specific to this system that is getting confused or is mismatched. Try loading the driver with the following module parameter : "lpfc_pci_max_read=512" That's the smallest setting we allow to be set. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c6 --- Comment #6 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-26 05:32:38 MST --- Hey I upgraded the firmware and also loaded the module with the option lpfc_pci_max_read=512, problem is still there. Kristjan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c7 --- Comment #7 from James Smart <james.smart@emulex.com> 2009-01-26 08:37:49 MST --- ok - so is there any way to modify and recompile the driver to prove the error ? If the modified driver still fails, it's much more likely to be bad hardware. The modification would be: in lpfc_sli.c:lpfc_sli_set_dma_length() Comment out/delete all contents of the routine and add the single line "return 0;" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c8 --- Comment #8 from James Smart <james.smart@emulex.com> 2009-01-26 08:38:30 MST --- and double-checking - the new/updated firmware revision is ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c9 --- Comment #9 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-27 05:11:21 MST --- Created an attachment (id=267874) --> (https://bugzilla.novell.com/attachment.cgi?id=267874) 827 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c10 --- Comment #10 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-27 05:11:52 MST --- Created an attachment (id=267875) --> (https://bugzilla.novell.com/attachment.cgi?id=267875) 828 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c11 --- Comment #11 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-27 05:12:58 MST --- Hello new firmware version is 2.80a4 Made the changes in lpfc_sli.c, compiled the module and loaded it, it still failed, this time without "Adapter failed to set maximum DMA length mbxStatus"(because I removed this part) message so this problem is not related to lpfc_sli_set_dma_length Also took new lpfc driver from kernel 2.6.28.2(this is also without lpfc_sli_set_dma_length ) compiled it and during load time it also failed output of "insmod drivers/scsi/lpfc/lpfc.ko lpfc_log_verbose=0xffff" see attachment 828.txt Then I took the lpfc driver(v: 8.2.7) from kernel linux-2.6.27.5, compiled it and it loaded i can see the luns and mount the partitions compile warnings: CC [M] drivers/scsi/lpfc/lpfc_mem.o CC [M] drivers/scsi/lpfc/lpfc_sli.o drivers/scsi/lpfc/lpfc_sli.c: In function ‘lpfc_sli_poll_fcp_ring’: drivers/scsi/lpfc/lpfc_sli.c:1365: warning: array subscript is above array bounds drivers/scsi/lpfc/lpfc_sli.c:1365: warning: array subscript is above array bounds drivers/scsi/lpfc/lpfc_sli.c: In function ‘lpfc_sli_handle_fast_ring_event’: drivers/scsi/lpfc/lpfc_sli.c:1541: warning: array subscript is above array bounds drivers/scsi/lpfc/lpfc_sli.c:1541: warning: array subscript is above array bounds CC [M] drivers/scsi/lpfc/lpfc_ct.o CC [M] drivers/scsi/lpfc/lpfc_els.o CC [M] drivers/scsi/lpfc/lpfc_hbadisc.o CC [M] drivers/scsi/lpfc/lpfc_init.o CC [M] drivers/scsi/lpfc/lpfc_mbox.o CC [M] drivers/scsi/lpfc/lpfc_nportdisc.o CC [M] drivers/scsi/lpfc/lpfc_scsi.o drivers/scsi/lpfc/lpfc_scsi.c: In function ‘lpfc_bus_reset_handler’: drivers/scsi/lpfc/lpfc_scsi.c:1245: warning: ‘status’ may be used uninitialized in this function CC [M] drivers/scsi/lpfc/lpfc_attr.o CC [M] drivers/scsi/lpfc/lpfc_vport.o CC [M] drivers/scsi/lpfc/lpfc_debugfs.o LD [M] drivers/scsi/lpfc/lpfc.o Building modules, stage 2. MODPOST 1 modules CC drivers/scsi/lpfc/lpfc.mod.o LD [M] drivers/scsi/lpfc/lpfc.ko and then output of "insmod drivers/scsi/lpfc/lpfc.ko lpfc_log_verbose=0xffff" see attachment 827.txt I took the kernels from kernel.org Also I have similiar machine with the same HBA(fw version 2.10a10), I popped in the OpenSuse11.1 cd and during boot I saw the same errors when lpfc module was loading Kristjan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c12 --- Comment #12 from James Smart <james.smart@emulex.com> 2009-01-27 08:10:40 MST --- Thank you very much for the information. Let's try another thing. Please load the driver with the following module option "lpfc_use_msi=0". And if that works, can you then try it with "lpfc_use_msi=1" ? Also, can you describe the host system the adapter is in ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c13 --- Comment #13 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-27 10:42:20 MST --- hei with option lpfc_use_msi=0 it loads fine, with lpfc_use_msi=1 it fails (same errors as in first post) and the machine itself is an old ibm machine IBM 8671-7CG X235 cpu: Intel(R) Xeon(TM) CPU 2.80GHz BIOS Information Vendor: IBM Version: -[GRE158AUS-1.17]- (newest) Release Date: 01/09/2006 raid: IBM PCI ServeRAID 7.12.05 Build 761 <ServeRAID 6i> lspci -v output I already gave If I forgot something then let me know Kristjan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c14 --- Comment #14 from James Smart <james.smart@emulex.com> 2009-01-27 11:53:21 MST --- Thank You. So the problem is related to whether we come up with MSI enabled or not. This is one of the differences between 8.2.7 and 8.2.8.x. The later revisions attempt to come up MSI/MSI-X by default, rather than making it an admin option. There are a lot of broken MSI/MSIX chipsets/platforms that say they support MSI/MSI-X. So, in driver rev 8.2.8.6, we always validate we can have an interrupt delivered via MSI/MSIX before sticking with it. It appears that on this system, that indeed works as we stay MSI-based. What's interesting is - the place where this fails, the driver isn't depending on interrupts - it's polling for X amount of time, and only if the time expires does the failure path occur. I'm speculating, but I believe that there may be some platform post-processing of MSI interrupt that is locking up the cpu and disrupting the timer logic that the driver is depending on, thus it ends up failing the attachment. One thing we would like is for you to test our latest 8.2.8.x version. I will upload it shortly. If the latest revision is still not functional - the way I would recommend resolving this is to release note the failure, symptoms, and the "lpfc_use_msi=0" workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User james.smart@emulex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c15 --- Comment #15 from James Smart <james.smart@emulex.com> 2009-01-27 11:55:46 MST --- Created an attachment (id=268053) --> (https://bugzilla.novell.com/attachment.cgi?id=268053) 8.2.8.12 driver source -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User kristjan.eentsalu@err.ee added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c16 --- Comment #16 from Kristjan Eentsalu <kristjan.eentsalu@err.ee> 2009-01-27 12:37:06 MST --- Hey Big thanks for Your help but the latest driver still has the same problem. I'll use "lpfc_use_msi=0" workaround for now. Kristjan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User hare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c17 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |hare@novell.com Info Provider|james.smart@emulex.com | AssignedTo|hare@novell.com |coolo@novell.com --- Comment #17 from Hannes Reinecke <hare@novell.com> 2009-01-29 03:15:59 MST --- Coolo, can we get this documented on the OpenSUSE website somewhere? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=466431 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466431#c18 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com AssignedTo|coolo@novell.com |kristjan.eentsalu@err.ee --- Comment #18 from Stephan Kulow <coolo@novell.com> 2009-01-31 11:39:20 MST --- sure, it's a wiki. Everyone can add informations to it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com