Debug messages from commBind with "(22) Invalid argument"

Upgraded to squid 2.2STABLE5 yesterday on a Sparc machine
running Solaris 2.5.1. Generally it seems to be working OK, but there
are frequent debug messages in cache.log from commBind() - e.g.

1999/11/09 10:46:55| commBind: Cannot bind socket FD 75 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:55| commBind: Cannot bind socket FD 14 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:55| commBind: Cannot bind socket FD 14 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:55| commBind: Cannot bind socket FD 121 to 138.37.7.252:0: (22)
 Invalid argument
1999/11/09 10:46:55| commBind: Cannot bind socket FD 14 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:56| commBind: Cannot bind socket FD 14 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:56| commBind: Cannot bind socket FD 53 to 138.37.7.252:0: (22)
Invalid argument
1999/11/09 10:46:56| commBind: Cannot bind socket FD 53 to 138.37.7.252:0: (22)

138.37.7.252 is one of the IP addresses assigned to this machine
(not the primary one). squid.conf includes the following lines:

tcp_incoming_address 138.37.7.252
tcp_outgoing_address 138.37.7.252
#udp_incoming_address 0.0.0.0
udp_outgoing_address 138.37.7.252

Am I doing something wrong, or could this be a bug? These settings
seemed to work correctly with squid 1.1.22.

Thanks, John.

--
John Holman
QMW Computing Services
Tel: 0171-975 5323
------------------------