Re: problem whit optic fibre adapter (emulex LP952)
On Fri, Jan 22, 2010 at 07:49:53AM +0100, Marco Vaschetto wrote: [...] > >Sorry but I use Debian on our SAN, with QLogic and Emulex FC cards. > >I have no problems, but use different Emulex models... > >(Zephyr-X LightPulse Fibre Channel Host Adapter) > Hi, on your infrastructure have a optic fiber switch? > I read some think about that have some problem whit emulex card > connect point to point. Yes, we have brocade FC switchs in Fabric mode. So point to point, not loop mode. signature.asc Description: Digital signature
Re: problem whit optic fibre adapter (emulex LP952)
Gilles Mocellin ha scritto: On Wed, Jan 20, 2010 at 07:45:58PM -0600, Stan Hoeppner wrote: Marco Vaschetto put forth on 1/20/2010 2:36 PM: [...] Debian is not a "commercial" distribution. Fiber channel is only found in commercial environments. Thus, most of the people around the world using FC adapters with Linux are NOT using Debian Linux, but rather Red Hat Enterprise or SuSE Linux. Notice I am the only person on this list to try to help you? And as I previously stated, I've not actually used FC cards with Linux on bare metal. You need to be talking to an audience that actually has FC experience on bare metal Linux. You may even try a SuSE or Red Hat mailing list as well. Sorry but I use Debian on our SAN, with QLogic and Emulex FC cards. I have no problems, but use different Emulex models... (Zephyr-X LightPulse Fibre Channel Host Adapter) Hi, on your infrastructure have a optic fiber switch? I read some think about that have some problem whit emulex card connect point to point. You're right that with Debian, it is not easy to have the hardware vendor support you... There support Matirix is so restrictive about firmware and driver versions... (HP here) Tank's for answer. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
Marco Vaschetto put forth on 1/21/2010 4:49 PM: > yes, whit your expirience is a good way or have some is better? (the > testing time use the lp952 but when is coming the blade server is Qlogic > but the blade come later the test time) and on company have only a > LP952, and we will use w2k3 for iSCSI server (when is time I try to make > the iSCSI whit Debian and Qlogic) If I read that correctly, you're using Debian to test the FC SAN/iSCSI box, but in production you're going to install W2K3 instead of Debian? That doesn't make any sense. I must be reading this wrong. > if you have a chance , and time, do you can make a benchmark whit a > program the name is performantest7.0 have evaluation version is free to > download; Sorry. I'm no longer with that employer, and we don't have a SAN at my current place, so I'm unable to do any testing for you. To be completely honest you're probably better off going with an FC/iSCSI gateway appliance than with a home brew Linux or Windows box, something like a Nexsan 400i would probably suit your needs well. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
Stan Hoeppner ha scritto: Marco Vaschetto put forth on 1/21/2010 4:29 AM: I want say tank you for your time, You're welcome. Like I said, sorry I wasn't of more help. and I have just a question but this is about the ESX, in my company we do testing about virtualization solution the machine whit the optic fibre must do a iSCSI server, my question is how you feel about ESX and do you have try ESXi ? I mean about the performance, in my company have do the So, you want to connect to a FC SAN on the back end, and server iSCSI over GigE on the front end? yes, whit your expirience is a good way or have some is better? (the testing time use the lp952 but when is coming the blade server is Qlogic but the blade come later the test time) and on company have only a LP952, and we will use w2k3 for iSCSI server (when is time I try to make the iSCSI whit Debian and Qlogic) benchmark on the windows se 2k3 virtualized on xenserver but we wold like try ESXi and ESX witch one is better for you? I've not played with ESXi. My only experience is with ESX 2.5/3.0 on a IBM Blade environment with Qlogic HBAs and mixed IBM FasTt and Nexsan storage arrays. The performance was quite good. if you have a chance , and time, do you can make a benchmark whit a program the name is performantest7.0 have evaluation version is free to download; if you can do me this favor pleas attachment this information quantity host ram, host CPU, quantity guest ram, size of the virtual disk of the guest machine, the infrastructure of the storage and the log file of performance test. Of course if do this test don't give you some trouble. If you need I will send you back the benchmark of my test. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
Marco Vaschetto put forth on 1/21/2010 4:29 AM: > I want say tank you for your time, You're welcome. Like I said, sorry I wasn't of more help. > and I have just a question but this is about the ESX, in my company we > do testing about virtualization solution the machine whit the optic > fibre must > > do a iSCSI server, my question is how you feel about ESX and do you have > try ESXi ? I mean about the performance, in my company have do the So, you want to connect to a FC SAN on the back end, and server iSCSI over GigE on the front end? > benchmark on the windows se 2k3 virtualized on xenserver but we wold > like try ESXi and ESX witch one is better for you? I've not played with ESXi. My only experience is with ESX 2.5/3.0 on a IBM Blade environment with Qlogic HBAs and mixed IBM FasTt and Nexsan storage arrays. The performance was quite good. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
On Wed, Jan 20, 2010 at 07:45:58PM -0600, Stan Hoeppner wrote: > Marco Vaschetto put forth on 1/20/2010 2:36 PM: [...] > Debian is not a "commercial" distribution. Fiber channel is only found in > commercial environments. Thus, most of the people around the world using FC > adapters with Linux are NOT using Debian Linux, but rather Red Hat Enterprise > or > SuSE Linux. Notice I am the only person on this list to try to help you? And > as I previously stated, I've not actually used FC cards with Linux on bare > metal. You need to be talking to an audience that actually has FC experience > on > bare metal Linux. You may even try a SuSE or Red Hat mailing list as well. Sorry but I use Debian on our SAN, with QLogic and Emulex FC cards. I have no problems, but use different Emulex models... (Zephyr-X LightPulse Fibre Channel Host Adapter) You're right that with Debian, it is not easy to have the hardware vendor support you... There support Matirix is so restrictive about firmware and driver versions... (HP here) signature.asc Description: Digital signature
Re: problem whit optic fibre adapter (emulex LP952)
Stan Hoeppner ha scritto: Marco Vaschetto put forth on 1/20/2010 2:36 PM: Stan Hoeppner ha scritto: This may point you in the right direction: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1263982812391+28353475&threadId=760337 Looks like you might need to update the card's firmware, try it in another PCI-X slot, or remove all the other PCI/X cards to see if there is a conflict. I don't have any direct experience with FC cards and Linux, only VMware ESX. I have seen situations where drivers fail when the card is not attached to a switch. Way back in the day I've seen SCSI drivers fail during boot if there were no drives attached. Goofy stuff. I'm betting you're in a similar goofy situation. That card and driver combo appear to be finicky. I try to take out all the pci device, but infect I never try to take out the pci array controller I hope the machine can start whit ide controller on-board now I fix the problem of libfc before is missing now have in the new kernel but the problem still have. Later try whit out a array controller pci my idea is finish. anyone have some idea? Did you read the first post in the document linked above at hp.com? Have you updated the adapter firmware to the latest version? (Ignore the 2nd and 3rd posts as that driver kit is 6 years old now) Also, hardware drivers are kernel components. You're better off asking for help with this FC adapter on the Linux-scsi list or lkml than on debian-users. http://vger.kernel.org/vger-lists.html#linux-scsi Debian is not a "commercial" distribution. Fiber channel is only found in commercial environments. Thus, most of the people around the world using FC adapters with Linux are NOT using Debian Linux, but rather Red Hat Enterprise or SuSE Linux. Notice I am the only person on this list to try to help you? And as I previously stated, I've not actually used FC cards with Linux on bare metal. You need to be talking to an audience that actually has FC experience on bare metal Linux. You may even try a SuSE or Red Hat mailing list as well. Sorry I couldn't be or more help. I want say tank you for your time, and I have just a question but this is about the ESX, in my company we do testing about virtualization solution the machine whit the optic fibre must do a iSCSI server, my question is how you feel about ESX and do you have try ESXi ? I mean about the performance, in my company have do the benchmark on the windows se 2k3 virtualized on xenserver but we wold like try ESXi and ESX witch one is better for you? Tank's again for your time. Marco Vaschetto -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
Marco Vaschetto put forth on 1/20/2010 2:36 PM: > Stan Hoeppner ha scritto: >> This may point you in the right direction: >> http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1263982812391+28353475&threadId=760337 >> >> >> Looks like you might need to update the card's firmware, try it in >> another PCI-X >> slot, or remove all the other PCI/X cards to see if there is a >> conflict. I >> don't have any direct experience with FC cards and Linux, only VMware >> ESX. I >> have seen situations where drivers fail when the card is not attached >> to a >> switch. Way back in the day I've seen SCSI drivers fail during boot >> if there >> were no drives attached. Goofy stuff. >> >> I'm betting you're in a similar goofy situation. That card and driver >> combo >> appear to be finicky. >> >> > I try to take out all the pci device, but infect I never try to take out > the pci array controller I hope the machine can start whit ide > controller on-board > > now I fix the problem of libfc before is missing now have in the new > kernel but the problem still have. > > Later try whit out a array controller pci my idea is finish. > > anyone have some idea? Did you read the first post in the document linked above at hp.com? Have you updated the adapter firmware to the latest version? (Ignore the 2nd and 3rd posts as that driver kit is 6 years old now) Also, hardware drivers are kernel components. You're better off asking for help with this FC adapter on the Linux-scsi list or lkml than on debian-users. http://vger.kernel.org/vger-lists.html#linux-scsi Debian is not a "commercial" distribution. Fiber channel is only found in commercial environments. Thus, most of the people around the world using FC adapters with Linux are NOT using Debian Linux, but rather Red Hat Enterprise or SuSE Linux. Notice I am the only person on this list to try to help you? And as I previously stated, I've not actually used FC cards with Linux on bare metal. You need to be talking to an audience that actually has FC experience on bare metal Linux. You may even try a SuSE or Red Hat mailing list as well. Sorry I couldn't be or more help. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
Stan Hoeppner ha scritto: This may point you in the right direction: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1263982812391+28353475&threadId=760337 Looks like you might need to update the card's firmware, try it in another PCI-X slot, or remove all the other PCI/X cards to see if there is a conflict. I don't have any direct experience with FC cards and Linux, only VMware ESX. I have seen situations where drivers fail when the card is not attached to a switch. Way back in the day I've seen SCSI drivers fail during boot if there were no drives attached. Goofy stuff. I'm betting you're in a similar goofy situation. That card and driver combo appear to be finicky. I try to take out all the pci device, but infect I never try to take out the pci array controller I hope the machine can start whit ide controller on-board now I fix the problem of libfc before is missing now have in the new kernel but the problem still have. Later try whit out a array controller pci my idea is finish. anyone have some idea? Thank's Marco Vaschetto -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: problem whit optic fibre adapter (emulex LP952)
This may point you in the right direction: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1263982812391+28353475&threadId=760337 Looks like you might need to update the card's firmware, try it in another PCI-X slot, or remove all the other PCI/X cards to see if there is a conflict. I don't have any direct experience with FC cards and Linux, only VMware ESX. I have seen situations where drivers fail when the card is not attached to a switch. Way back in the day I've seen SCSI drivers fail during boot if there were no drives attached. Goofy stuff. I'm betting you're in a similar goofy situation. That card and driver combo appear to be finicky. -- Stan Marco Vaschetto put forth on 1/20/2010 2:36 AM: > Stan Hoeppner ha scritto: >> Can we get some relevant dmesg and /var/log/boot output? Also, are >> you loading >> libfc? You'll need it in addition to lpfc. >> >> Have you tried building a custom kernel with all the stuff built in, >> not as modules? >> >> > No, in fact I didn't try whit a compiled kernel but only precompiled > kernel, > > the version I have try is 2.6.26-2-686 and 2.6.32-trunk-686, but steal > now is not work > > now I will give you the output of a "clean" based system of Debian > Lenny kernel 2.6.26-2-686 and to day I will try your suggestion > > of use a recompiled kernel; and no, is without the libfc. I will try to > fix that. > > so this is the output on the bootstrap: > > the file log of boot is empty > > LSAXYZAEYY:~# cat /var/log/boot (Nothing has been logged yet.) > > this is the output of dmesg (complete)of a new installation: > > LSAXYZAEYY:/# dmesg > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2) > (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian > 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC 2009 > [0.00] BIOS-provided physical RAM map: > [0.00] BIOS-e820: - 0009f400 (usable) > [0.00] BIOS-e820: 0009f400 - 000a (reserved) > [0.00] BIOS-e820: 000f - 0010 (reserved) > [0.00] BIOS-e820: 0010 - 8fffa000 (usable) > [0.00] BIOS-e820: 8fffa000 - 9000 (ACPI data) > [0.00] BIOS-e820: fec0 - fec1 (reserved) > [0.00] BIOS-e820: fee0 - fee1 (reserved) > [0.00] BIOS-e820: ffc0 - 0001 (reserved) > [0.00] 1407MB HIGHMEM available. > [0.00] 896MB LOWMEM available. > [0.00] found SMP MP-table at [c00f4fd0] 000f4fd0 > [0.00] Entering add_active_range(0, 0, 589818) 0 entries of 256 > used > [0.00] Zone PFN ranges: > [0.00] DMA 0 -> 4096 > [0.00] Normal 4096 -> 229376 > [0.00] HighMem229376 -> 589818 > [0.00] Movable zone start PFN for each node > [0.00] early_node_map[1] active PFN ranges > [0.00] 0:0 -> 589818 > [0.00] On node 0 totalpages: 589818 > [0.00] DMA zone: 32 pages used for memmap > [0.00] DMA zone: 0 pages reserved > [0.00] DMA zone: 4064 pages, LIFO batch:0 > [0.00] Normal zone: 1760 pages used for memmap > [0.00] Normal zone: 223520 pages, LIFO batch:31 > [0.00] HighMem zone: 2816 pages used for memmap > [0.00] HighMem zone: 357626 pages, LIFO batch:31 > [0.00] Movable zone: 0 pages used for memmap > [0.00] DMI 2.3 present. > [0.00] ACPI: RSDP 000F4F70, 0014 (r0 COMPAQ) > [0.00] ACPI: RSDT 8FFFA000, 0030 (r1 COMPAQ D15 > 2 Ò 162E) > [0.00] ACPI: FACP 8FFFA040, 0074 (r1 COMPAQ D15 > 2 Ò 162E) > [0.00] ACPI: DSDT 8FFFA240, 22F1 (r1 COMPAQ DSDT1 > MSFT 10B) > [0.00] ACPI: FACS 8FFFA0C0, 0040 > [0.00] ACPI: APIC 8FFFA100, 00AC (r1 COMPAQ 0083 > 2 Ò 162E) > [0.00] ACPI: SPCR 8FFFA1C0, 0050 (r1 COMPAQ SPCRRBSU > 1 Ò 162E) > [0.00] ACPI: PM-Timer IO Port: 0x920 > [0.00] ACPI: Local APIC address 0xfee0 > [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) > [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled) > [0.00] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled) > [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) > [0.00] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled) > [0.00] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled) > [0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) > [0.00] ACPI: IOAPIC (id[0x02] address[0xfec
Re: problem whit optic fibre adapter (emulex LP952)
Stan Hoeppner ha scritto: Can we get some relevant dmesg and /var/log/boot output? Also, are you loading libfc? You'll need it in addition to lpfc. Have you tried building a custom kernel with all the stuff built in, not as modules? No, in fact I didn't try whit a compiled kernel but only precompiled kernel, the version I have try is 2.6.26-2-686 and 2.6.32-trunk-686, but steal now is not work now I will give you the output of a "clean" based system of Debian Lenny kernel 2.6.26-2-686 and to day I will try your suggestion of use a recompiled kernel; and no, is without the libfc. I will try to fix that. so this is the output on the bootstrap: the file log of boot is empty LSAXYZAEYY:~# cat /var/log/boot (Nothing has been logged yet.) this is the output of dmesg (complete)of a new installation: LSAXYZAEYY:/# dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC 2009 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f400 (usable) [0.00] BIOS-e820: 0009f400 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 8fffa000 (usable) [0.00] BIOS-e820: 8fffa000 - 9000 (ACPI data) [0.00] BIOS-e820: fec0 - fec1 (reserved) [0.00] BIOS-e820: fee0 - fee1 (reserved) [0.00] BIOS-e820: ffc0 - 0001 (reserved) [0.00] 1407MB HIGHMEM available. [0.00] 896MB LOWMEM available. [0.00] found SMP MP-table at [c00f4fd0] 000f4fd0 [0.00] Entering add_active_range(0, 0, 589818) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] Normal 4096 -> 229376 [0.00] HighMem229376 -> 589818 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 -> 589818 [0.00] On node 0 totalpages: 589818 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 1760 pages used for memmap [0.00] Normal zone: 223520 pages, LIFO batch:31 [0.00] HighMem zone: 2816 pages used for memmap [0.00] HighMem zone: 357626 pages, LIFO batch:31 [0.00] Movable zone: 0 pages used for memmap [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F4F70, 0014 (r0 COMPAQ) [0.00] ACPI: RSDT 8FFFA000, 0030 (r1 COMPAQ D15 2 Ò 162E) [0.00] ACPI: FACP 8FFFA040, 0074 (r1 COMPAQ D15 2 Ò 162E) [0.00] ACPI: DSDT 8FFFA240, 22F1 (r1 COMPAQ DSDT1 MSFT 10B) [0.00] ACPI: FACS 8FFFA0C0, 0040 [0.00] ACPI: APIC 8FFFA100, 00AC (r1 COMPAQ 0083 2 Ò 162E) [0.00] ACPI: SPCR 8FFFA1C0, 0050 (r1 COMPAQ SPCRRBSU 1 Ò 162E) [0.00] ACPI: PM-Timer IO Port: 0x920 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled) [0.00] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled) [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) [0.00] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled) [0.00] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-15 [0.00] ACPI: IOAPIC (id[0x03] address[0xfec01000] gsi_base[16]) [0.00] IOAPIC[1]: apic_id 3, version 17, address 0xfec01000, GSI 16-31 [0.00] ACPI: IOAPIC (id[0x04] address[0xfec02000] gsi_base[32]) [0.00] IOAPIC[2]: apic_id 4, version 17, address 0xfec02000, GSI 32-47 [0.00] ACPI: IOAPIC (id[0x05] address[0xfec03000] gsi_base[48]) [0.00] IOAPIC[3]: apic_id 5, version 17, address 0xfec03000, GSI 48-63 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [0.00] ACPI: IRQ0 used by override. [0.00] ACPI: IRQ2 used by override. [0.00] ACPI: IRQ9 used by override. [0.00] Enabling APIC mode: Flat. Using 4 I/O APICs [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Alloca
Re: problem whit optic fibre adapter (emulex LP952)
Can we get some relevant dmesg and /var/log/boot output? Also, are you loading libfc? You'll need it in addition to lpfc. Have you tried building a custom kernel with all the stuff built in, not as modules? -- Stan Marco Vaschetto put forth on 1/19/2010 2:35 AM: > Stan Hoeppner ha scritto: >> Marco Vaschetto put forth on 1/16/2010 6:38 PM: >> >> >>> Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter >>> failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0 >>> Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter >>> failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0" >>> >> >> This could be caused by any number of things. Send complete lspci (no >> switches) >> output and we'll go from there. >> >> > Hi, > > this is the complite output of lspci -vv > > 00:00.0 Host bridge: Broadcom GCNB-LE Host Bridge (rev 32) >Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- >Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Kernel modules: sworks-agp > > 00:00.1 Host bridge: Broadcom GCNB-LE Host Bridge >Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- >Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Kernel modules: sworks-agp > > 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) > (prog-if 00 [VGA controller]) >Subsystem: Compaq Computer Corporation Proliant Rage XL >Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping+ SERR- FastB2B- DisINTx- >Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 64 (2000ns min), Cache Line Size: 64 bytes >Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M] >Region 1: I/O ports at 2400 [size=256] >Region 2: Memory at f5ff (32-bit, non-prefetchable) [size=4K] >[virtual] Expansion ROM at 9804 [disabled] [size=128K] >Capabilities: [5c] Power Management version 2 >Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) >Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > 00:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X > Gigabit Ethernet (rev 02) >Subsystem: Compaq Computer Corporation NC7760 Gigabit Server > Adapter (PCI-X, 10/100/1000-T) >Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr+ Stepping- SERR+ FastB2B- DisINTx- >Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 64 (16000ns min), Cache Line Size: 64 bytes >Interrupt: pin A routed to IRQ 19 >Region 0: Memory at f5fe (64-bit, non-prefetchable) [size=64K] >[virtual] Expansion ROM at 9806 [disabled] [size=64K] >Capabilities: [40] PCI-X non-bridge device >Command: DPERE- ERO- RBC=512 OST=1 >Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple > DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- >Capabilities: [48] Power Management version 2 >Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot+,D3cold+) >Status: D0 PME-Enable+ DSel=0 DScale=1 PME- >Capabilities: [50] Vital Product Data >Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ > Queue=0/3 Enable- >Address: 084280808000409c Data: 14a6 >Kernel driver in use: tg3 >Kernel modules: tg3 > > 00:05.0 System peripheral: Compaq Computer Corporation Advanced System > Management Controller >Subsystem: Compaq Computer Corporation Device b0f3 >Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ > Stepping- SERR+ FastB2B- DisINTx- >Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > SERR- Interrupt: pin A routed to IRQ 11 >Region 0: I/O ports at 1800 [size=256] >Region 1: Memory at f5fd (32-bit, non-prefetchable) [size=256] > > 00:06.0 RAID bus controller: Compaq Computer Corporation Smart Array > 64xx (rev 01) >Subsystem: Compaq Computer Corporation Smart Array 641 >Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ > Stepping- SERR+ FastB2B- DisINTx- >Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 64, Cache Line Size: 64 bytes >Interrupt: pin A routed to IRQ 21 >Region 0: Memory at f5fc (64-bit, non-prefetchable) [size=8K] >Region 2: I/O ports at 2800 [size=256] >Region 3: Memory at f5f8 (64-bit, non-prefetchable) [size=256K] >[virtual] Expansion ROM at 9800 [disabled] [size=256K] >Capabilities: [d0] Power Management version 2 >Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) >Status: D0 PME-Enable- DSel=0 DScale=0 P
Re: problem whit optic fibre adapter (emulex LP952)
Stan Hoeppner ha scritto: Marco Vaschetto put forth on 1/16/2010 6:38 PM: Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0 Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0" This could be caused by any number of things. Send complete lspci (no switches) output and we'll go from there. Hi, this is the complite output of lspci -vv 00:00.0 Host bridge: Broadcom GCNB-LE Host Bridge (rev 32) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: sworks-agp 00:00.1 Host bridge: Broadcom GCNB-LE Host Bridge Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: sworks-agp 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation Proliant Rage XL Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M] Region 1: I/O ports at 2400 [size=256] Region 2: Memory at f5ff (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 9804 [disabled] [size=128K] Capabilities: [5c] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02) Subsystem: Compaq Computer Corporation NC7760 Gigabit Server Adapter (PCI-X, 10/100/1000-T) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (16000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f5fe (64-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at 9806 [disabled] [size=64K] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO- RBC=512 OST=1 Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable- Address: 084280808000409c Data: 14a6 Kernel driver in use: tg3 Kernel modules: tg3 00:05.0 System peripheral: Compaq Computer Corporation Advanced System Management Controller Subsystem: Compaq Computer Corporation Device b0f3 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at 1800 [size=256] Region 1: Memory at f5fd (32-bit, non-prefetchable) [size=256] 00:06.0 RAID bus controller: Compaq Computer Corporation Smart Array 64xx (rev 01) Subsystem: Compaq Computer Corporation Smart Array 641 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 21 Region 0: Memory at f5fc (64-bit, non-prefetchable) [size=8K] Region 2: I/O ports at 2800 [size=256] Region 3: Memory at f5f8 (64-bit, non-prefetchable) [size=256K] [virtual] Expansion ROM at 9800 [disabled] [size=256K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [dc] PCI-X non-bridge device Command: DPERE- ERO+ RBC=2048 OST=8 Status: Dev=fd:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=8 DMCRS=128 RSCEM- 266MHz- 533MHz- Capabilities: [f0] Vital Product Data Kernel driver in use: cciss Kernel modules: cciss 00:07.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ Spec
Re: problem whit optic fibre adapter (emulex LP952)
Marco Vaschetto put forth on 1/16/2010 6:38 PM: > Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter > failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0 > Jan 14 14:10:28 ssdsmb1tls kernel: lpfc :03:01.0: 0:0442 Adapter > failed to init, mbxCmd x88 CONFIG_PORT, mbxStatus x12 Data: x0" This could be caused by any number of things. Send complete lspci (no switches) output and we'll go from there. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
