Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question
Let assume that the HCA has wrong FWR and/or other reason that cause driver load failure ? We have to check what's going on in this case. -> mstflint is one of our tools. Moshe. Moshe Katzir | +972-9971-8639 (o) | +972-52-860-6042 (m) Voltaire - The Grid Backbone www.voltaire.com -Original Message- From: Michael S. Tsirkin [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 4:25 PM To: Moshe Kazir Cc: Or Gerlitz; Roland Dreier; openib-general@openib.org; Yiftah Shahar; Tseng-hui Lin Subject: Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question Quoting r. Moshe Kazir <[EMAIL PROTECTED]>: > Is it time to create a work arround that opens /proc/bus/pci/ > And always work ? But why isn't the driver loaded? -- MST ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question
Quoting r. Moshe Kazir <[EMAIL PROTECTED]>: > Is it time to create a work arround that opens /proc/bus/pci/ And > always work ? But why isn't the driver loaded? -- MST ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question
I have tested the mstflint problem with two different ppc64 machines : - On sles 10 PPC64 PowerMac G5 -> mstflint -d 0001:07:00.0 qworks o.k. with and without the ib_mthca loaded - On s;es10 PPC64 IBM JS21 -> mstflint -d 0001:07:00.0 qDOESN'T work with and without the ib_mthca loaded and I have to use /proc/bus/pci/. Is it time to create a work arround that opens /proc/bus/pci/ And always work ? Moshe Moshe Katzir | +972-9971-8639 (o) | +972-52-860-6042 (m) Voltaire - The Grid Backbone www.voltaire.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael S. Tsirkin Sent: Tuesday, September 05, 2006 4:37 PM To: Or Gerlitz Cc: Roland Dreier; openib-general@openib.org Subject: Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question Quoting r. Or Gerlitz <[EMAIL PROTECTED]>: > Subject: Re: getting LOC_QP_OP_ERR with IPoIB - mstflint question > > Michael S. Tsirkin wrote: > > Donnu, it looks really weird. Could you try firmware 3.5.0 please? > > I just noted that you can not work with mstflint if the mthca driver > is > not loaded, i think it was not the case in the gen1 tools, am i correct. Yes, recent kernels disable device access once driver is unloaded: mstflint -d 08:00.0 q *** ERROR *** Read a corrupted device id (0x). Probably HW/PCI access problem *** ERROR *** Device type 65535 not supported. *** ERROR *** Can not get flash type using device 08:00.0 mstflint should work without driver using /proc: mstflint -d /proc/bus/pci/08/00.0 q Image type: Failsafe I.S. Version:1 Chip Revision: A0 In gen1 flint had a separate driver which you had to load. I am not sure whether this would work on 2.6.18 > Is this connected to this print > > ACPI: PCI interrupt for device :02:00.0 disabled > > i see once the mthca driver is unloaded? > > Or. Probably not. -- MST ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question
Quoting r. Or Gerlitz <[EMAIL PROTECTED]>: > Subject: Re: getting LOC_QP_OP_ERR with IPoIB - mstflint question > > Michael S. Tsirkin wrote: > > Donnu, it looks really weird. Could you try firmware 3.5.0 please? > > I just noted that you can not work with mstflint if the mthca driver is > not loaded, i think it was not the case in the gen1 tools, am i correct. Yes, recent kernels disable device access once driver is unloaded: mstflint -d 08:00.0 q *** ERROR *** Read a corrupted device id (0x). Probably HW/PCI access problem *** ERROR *** Device type 65535 not supported. *** ERROR *** Can not get flash type using device 08:00.0 mstflint should work without driver using /proc: mstflint -d /proc/bus/pci/08/00.0 q Image type: Failsafe I.S. Version:1 Chip Revision: A0 In gen1 flint had a separate driver which you had to load. I am not sure whether this would work on 2.6.18 > Is this connected to this print > > ACPI: PCI interrupt for device :02:00.0 disabled > > i see once the mthca driver is unloaded? > > Or. Probably not. -- MST ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] getting LOC_QP_OP_ERR with IPoIB - mstflint question
Michael S. Tsirkin wrote: > Donnu, it looks really weird. Could you try firmware 3.5.0 please? I just noted that you can not work with mstflint if the mthca driver is not loaded, i think it was not the case in the gen1 tools, am i correct. Is this connected to this print ACPI: PCI interrupt for device :02:00.0 disabled i see once the mthca driver is unloaded? Or. > dill:/tmp # modprobe -r ib_mthca > dill:/tmp # ./mstflint -d 00:02:00.0 q > *** ERROR *** Read a corrupted device id (0x). Probably HW/PCI access > problem > *** ERROR *** Device type 65535 not supported. > *** ERROR *** Can not get flash type using device 00:02:00.0 > dill:/tmp # modprobe ib_mthca > dill:/tmp # ./mstflint -d 00:02:00.0 q > Image type: Failsafe > I.S. Version:1 > Chip Revision: A1 > GUID Des:Node Port1Port2Sys image > GUIDs: 0008f104039651dc 0008f104039651dd 0008f104039651de > 0008f104039651df > Board ID: (VLT0010010001) > VSD: > PSID:VLT0010010001 > dill:/tmp # dmesg > ACPI: PCI interrupt for device :02:00.0 disabled > ib_mthca: Mellanox InfiniBand HCA driver v0.08 (February 14, 2006) > ib_mthca: Initializing :02:00.0 > PCI: Enabling device :02:00.0 (0110 -> 0112) > ACPI: PCI Interrupt :02:00.0[A] -> GSI 29 (level, low) -> IRQ 193 ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
