WARNING: couldn't allocate FBT table for module vxio
WARNING: couldn't allocate SDT table for module vxfs
Certain modules, such as vxio and vxfs are large kernel modules with .text data that is greater than 2 MB. The dtrace probe cannot handle modules with a text region larger than 2 MB which is represented in hexadecimal:
2MB == 2097152 Bytes == 0x200000
For example, the vxio driver is 0x2c7d28 in size which is significantly larger than the 0x200000 limit imposed on FBT/SDT dtrace probes:
# modinfo | sort -k 3,3 | tail -10
212 7b2c0000 79d58 106 1 nfs (NFS syscall, client, and common)
199 7b336000 8cd20 - 1 kmdbmod (kmdb 1.0 Proto)
45 134a4e8 bac78 269 1 jnic146x (JNIC v5.3.1.1 (04062800))
0 1000000 c6ec8 - 0 unix ()
52 7bebe000 cdff8 183 1 qlc (SunFC Qlogic FCA v20060630-2.16)
56 7ba00000 122188 - 1 ip (IP STREAMS module 1.47)
56 7ba00000 122188 3 1 ip (IP STREAMS driver 1.47)
2 10933b0 1af170 - 0 genunix ()
204 7ae00000 1bc8a0 20 1 vxfs
27 7c002000 33ff70 271 1 vxio
Human-readable text size of this vxio module (3.4 MB total):
# echo 0x33ff70=D | adb
3407728
This 2MB .text limitation of dtrace probes may be reviewed in future releases of Solaris and/or Veritas may choose to reduce the size of the vxio driver's .text segment in future releases. In the meantime the warning messages can be safely ignored.