Incorrect driver getting loaded for Qlogic FC-HBA

DISCUSSION Rajat Jain 3 participants 7 messages Jul 25, 2005 – Jul 28, 2005 SCSI

lore

Share & tools

lore

Rajat Jain

author

2005-07-25 02:02 UTC #0 lore raw

Hi,

I do not know which list to put this problem on. And hence ...

I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my system. I selected all the Qlogic SCSI drivers while buiding the kernel. Now the problem is that every time I reboot, I have to MANUALLY modprobe the qla2322.ko module in the kernel and only then my HBA works. By default, the kernel loads qla2300.ko, which is not the correct driver for the card, and hence the HBA does not work. Here is the lspci output:

-----------------------------------------------------------------
0d:07.1 Fibre Channel: QLogic Corp.: Unknown device 2322 (rev 03)
Subsystem: QLogic Corp.: Unknown device 0118
Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 185 I/O ports at 6400 [size=256]
Memory at d0401000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Capabilities: [4c] PCI-X non-bridge device.
Capabilities: [54] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
-------------------------------------------------------------------

Here is the relevant extract from modules.pcimap:
-------------------------------------------------------------------
#module vendor device subvendor subdevice class
class_mask driver_data

qla2300  0x00001077 0x00002300 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla2300  0x00001077 0x00002312 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla2322  0x00001077 0x00002322 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

-------------------------------------------------------------------

As can be seen from above, qla2322 is the correct driver for device 2322 (My QLE2362 HBA has a device no 2322, as seen in lspci output). But for some reason the kernel always loads qla2300 instead on qla2322. I even tried putting the "qla2322" line on top of the two "qla2300" lines in the modules.pcimap file. But with no result.

TIA,

Rajat
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Greg KH

2005-07-26 00:06 UTC #1 lore raw

Quoted 7 lines · Rajat Jain

I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my system. I selected all the Qlogic SCSI drivers while buiding the kernel. Now the problem is that every time I reboot, I have to MANUALLY modprobe the qla2322.ko module in the kernel and only then my HBA works. By default, the kernel loads qla2300.ko, which is not the correct driver for the card, and hence the HBA does not work. Here is the lspci output:

"by default" the kernel does not load any modules. That's up to the hotplug system, or some other package.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Rajat Jain

author

2005-07-26 04:16 UTC #2 lore raw

Quoted 9 lines · Greg KH

Quoted 7 lines · Rajat Jain
I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my system. I selected all the Qlogic SCSI drivers while buiding the kernel. Now the problem is that every time I reboot, I have to MANUALLY modprobe the qla2322.ko module in the kernel and only then my HBA works. By default, the kernel loads qla2300.ko, which is not the correct driver for the card, and hence the HBA does not work. Here is the lspci output:

Quoted 7 lines

"by default" the kernel does not load any modules. That's up to the hotplug system, or some other package.
thanks,
greg k-h

Thanks. I just checked .. that is right. So let me put it this way. When ever I hot-plug my HBA into the system, the driver "qla2300" gets loaded. Where as the correct driver is "qla2322". This evident from the output of "modules.pcimap" file and "lspci". The PCI device number of HBA is 2322. and in modules.pcimap file, qla2322 is supposed to be loaded when this HBA is hot-plugged. But module qla2300 is getting loaded.

Any pointers on where could the problem be? Or how should I approach this problem?

Thanks a lot.

Rajat

PS: For reference I am attaching the modules.pcimap file and lspci output here again:

Here is the relevant extract from modules.pcimap:
-------------------------------------------------------------------
#module vendor device subvendor subdevice class
class_mask driver_data

qla2300  0x00001077 0x00002300 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla2300  0x00001077 0x00002312 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla2322  0x00001077 0x00002322 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

-------------------------------------------------------------------

Andrew Vasquez

2005-07-26 15:52 UTC #3 lore raw

Quoted 26 lines · Rajat Jain

Quoted 9 lines · Greg KH
Quoted 7 lines · Rajat Jain
I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my system. I selected all the Qlogic SCSI drivers while buiding the kernel. Now the problem is that every time I reboot, I have to MANUALLY modprobe the qla2322.ko module in the kernel and only then my HBA works. By default, the kernel loads qla2300.ko, which is not the correct driver for the card, and hence the HBA does not work. Here is the lspci output:
Quoted 7 lines
"by default" the kernel does not load any modules. That's up to the hotplug system, or some other package.
thanks,
greg k-h
Thanks. I just checked .. that is right. So let me put it this way. When ever I hot-plug my HBA into the system, the driver "qla2300" gets loaded. Where as the correct driver is "qla2322". This evident from the output of "modules.pcimap" file and "lspci". The PCI device number of HBA is 2322. and in modules.pcimap file, qla2322 is supposed to be loaded when this HBA is hot-plugged. But module qla2300 is getting loaded.

Quoted 2 lines

Any pointers on where could the problem be? Or how should I approach this problem?

A similar problem was noted with RHEL4, it seems the modules.pcimap and pci.ids file were correct, but the pcitable file contained entries for all ql[ae]23xx based HBAs to load qla2300.ko.

It's my understanding that this was fixed for RHEL4 U1. Which distro are you using? If you are using RHEL, and are still having problems, I'd suggest you file a report with Redhat.

Regards,
Andrew Vasquez

Rajat Jain

author

2005-07-27 06:01 UTC #4 lore raw

Quoted 34 lines · Andrew Vasquez

Quoted 26 lines · Rajat Jain
Quoted 9 lines · Greg KH
Quoted 7 lines · Rajat Jain
I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my system. I selected all the Qlogic SCSI drivers while buiding the kernel. Now the problem is that every time I reboot, I have to MANUALLY modprobe the qla2322.ko module in the kernel and only then my HBA works. By default, the kernel loads qla2300.ko, which is not the correct driver for the card, and hence the HBA does not work. Here is the lspci output:
Quoted 7 lines
"by default" the kernel does not load any modules. That's up to the hotplug system, or some other package.
thanks,
greg k-h
Thanks. I just checked .. that is right. So let me put it this way. When ever I hot-plug my HBA into the system, the driver "qla2300" gets loaded. Where as the correct driver is "qla2322". This evident from the output of "modules.pcimap" file and "lspci". The PCI device number of HBA is 2322. and in modules.pcimap file, qla2322 is supposed to be loaded when this HBA is hot-plugged. But module qla2300 is getting loaded.
Quoted 2 lines
Any pointers on where could the problem be? Or how should I approach this problem?
A similar problem was noted with RHEL4, it seems the modules.pcimap and pci.ids file were correct, but the pcitable file contained entries for all ql[ae]23xx based HBAs to load qla2300.ko.

Quoted 7 lines

It's my understanding that this was fixed for RHEL4 U1. Which distro are you using? If you are using RHEL, and are still having problems, I'd suggest you file a report with Redhat.
Regards,
Andrew Vasquez

BINGO! I AM using RHEL 4. So does that mean I can rectify the problem by making appropriate changes to "pcitable" file?

Thanks a Ton !

Rajat

Andrew Vasquez

2005-07-27 18:11 UTC #5 lore raw

Quoted 10 lines · Rajat Jain

Quoted 9 lines · Andrew Vasquez
A similar problem was noted with RHEL4, it seems the modules.pcimap and pci.ids file were correct, but the pcitable file contained entries for all ql[ae]23xx based HBAs to load qla2300.ko.
It's my understanding that this was fixed for RHEL4 U1. Which distro are you using? If you are using RHEL, and are still having problems, I'd suggest you file a report with Redhat.

Quoted 6 lines

Quoted 3 lines
Regards,
Andrew Vasquez
BINGO! I AM using RHEL 4. So does that mean I can rectify the problem by making appropriate changes to "pcitable" file?

I'm trying to get a firm answer from the folks who originally discvoered the problem some time back, it seems you have two options:

- during installation of RHEL4 (and not RHEL4U1), load with the 'noprobe' option:

linux noprobe

and manually select the appropriate drivers to load.

- (post installation) modify the /etc/modprobe.conf to and rename the qla2300 entry to qla2322 (i.e.):

alias scsi_hostadapter1 qla2322

modify the modules.pcimap table to load qla2322 for the 2322 device-id:

	qla2300		0x00001077	0x00002322	...

to:

	qla2322		0x00001077	0x00002322	...

Beyond that, I'd suggest you log a report with Redhat, as that's the extent of the workaround knowledge without going to RHEL4U1.

Hope this helps,
Andrew Vasquez
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Rajat Jain

author

2005-07-28 10:36 UTC #6 lore raw

Quoted 12 lines

Quoted 12 lines
Quoted 11 lines
A similar problem was noted with RHEL4, it seems the modules.pcimap and pci.ids file were correct, but the pcitable file contained entries for all ql[ae]23xx based HBAs to load qla2300.ko.
It's my understanding that this was fixed for RHEL4 U1. Which distro are you using? If you are using RHEL, and are still having problems, I'd suggest you file a report with Redhat.
Regards,
Andrew Vasquez

Quoted 5 lines

Quoted 2 lines
BINGO! I AM using RHEL 4. So does that mean I can rectify the problem by making appropriate changes to "pcitable" file?
I'm trying to get a firm answer from the folks who originally discvoered the problem some time back, it seems you have two options:

Hey Thanks. I would really appreciate if you could update list/me on it IF you get any updates (I know its too much pain).

Quoted 12 lines

- (post installation) modify the /etc/modprobe.conf to and rename the qla2300 entry to qla2322 (i.e.):
alias scsi_hostadapter1 qla2322
modify the modules.pcimap table to load qla2322 for the 2322 device-id:
       qla2300         0x00001077      0x00002322      ...
to:

Quoted 9 lines

       qla2322         0x00001077      0x00002322      ...
Beyond that, I'd suggest you log a report with Redhat, as that's the extent of the workaround knowledge without going to RHEL4U1.
Hope this helps,
Andrew Vasquez

THANKS. It worked for me, for time being.
In the mean time, I plan to file report with RedHat and will update list as and when I get any response.

regards,