64 bit devfsadm error

Question

Hi,
I?m developing a 64 bit Solaris 9 device driver for a PCI fibre channel board. Add_drv exits with the dreaded error 11, in spite of the fact that the driver attaches successfully, and is recognized by the system. I?ve tried everything listed in this forum, but can?t resolve the issue. The sequence of events:
#add_drv -m"* 0666 root sys" -i'"pci4ddc,e05"' -v fcd
exit status = 0
devfsadm: driver failed to attach: fcd
exit status = 11
Warning: Driver (fc) successfully added to system but failed to attach
Driver (fcd) installed
I?ve tried all variations on the "-i" flag, but the results don?t change.
As the driver is installed, prtconf recognizes the device, indicating the driver attach was successful:
#prtconf -vD
System Configuration: Sun Microsystems sun4u
Memory size: 1280 Megabytes
System Peripherals (Software Nodes):
pci, instance #1 (driver name: pcipsy)
Driver properties:
name='interrupt-priorities' type=int items=6 dev=none
value=0000000e.0000000e.0000000e.0000000e.0000000e.0000000e
Register Specifications:
Bus Type=0x1fe, Address=0x2000, Size=0x2000
Bus Type=0x1fe, Address=0x1800000, Size=0x100
Bus Type=0x1fe, Address=0x0, Size=0xd000
pci4ddc,e05
And all of this information is correct. Modinfo also shows the driver loads. The problem appears to be that devfsadm isn?t getting the right info somehow, as traced by truss:
461: 0.2847 open("/kernel/drv/sparcv9/fcd", O_RDONLY) = 3
461: 0.2850 lseek(3, 0, SEEK_END) = 212440
461: 0.2852 mmap(0x00000000, 212440, PROT_READ, MAP_PRIVATE, 3, 0) = 0xFF200
000
461: 0.2855 munmap(0xFF200000, 212440) = 0
461: 0.2856 close(3) = 0
461: 0.2858 open("/kernel/drv/sparcv9/fcd", O_RDONLY) = 3
461: 0.2861 lseek(3, 0, SEEK_END) = 212440
461: 0.2862 mmap(0x00000000, 212440, PROT_READ, MAP_PRIVATE, 3, 0) = 0xFF200
000
461: 0.2865 munmap(0xFF200000, 212440) = 0
461: 0.2867 close(3) = 0
461: 0.2870 sysconfig(_CONFIG_PAGESIZE) = 8192
461: 0.2873 open("/devices/pseudo/devinfo@0:devinfo", O_RDONLY) = 3
I suspect the problem is that it's trying to open /devices/pseudo, instead of /devices/pci@1f, 2000.
The call to create the minor node is:
ddi_create_minor_node(dip, "fcd", S_IFCHR, instance, "pci4ddc,e05", 0)
I?ve played with various values for "fcd" and "pci4ddc", no noticeable differences. I've tried some of the predefined def's for create_minor_node, like DDI_NT_NET and others, but it doesn't seem to make a difference. This is a character driver, not a network driver. Of course, ddi_create_minor_node returns with no error.
Other notes:
I've tried various location for the 64 bit driver, such as /platform, etc. As long as the driver is in a valid 64 bit directory location, the results are the same.
This is a 64 bit kernel on an Ultra-60:
#isainfo -kv
64-bit sparcv9 kernel modules
Any ideas or insights are appreciated. I suspect I've got something setup or defined wrong. The driver is stable and well behaved, and does not cause any type of error when loading.
Thanks
Ed

Answer 1

Well, this forum is an activity of useful information isn't it :-).
I finally developed a work around for this, but I still don't understand the cause of the problem. Any suggestions to the root cause are appreciated.
As noted above, the failure appears to be related to trying to open /devices/pseudo, instead of /devices/pci1f@2000 (64 bit pci device). This open is called by devfsadm.
If, after executing the add_drv, I manually run devfsadm, as in:
#devfsadm -v -i fcd
devfsadm works properly, and the properly entry is created in /devices/pci@1f,2000. I then can manually create the link between /dev and /devices, and everything works properly.
Possible timing problem with add_drv, devfsadm, and my driver? Not sure why running devfsadm manually after add_drv works, especially when I issue the exact same devfsadm as add_drv. The driver attach completes successfully well before devfsadm is called. This work around is ok for now, but we'd like to understand the problem so we don't encounter any problems in the future.
Anybody have any ideas?
Ed