samba - Jun 2007 - Error in logs, is it a bug or a misconfiguration?

I have a samba installation that's been running since 1997 or so.  
Over that time we've upgraded samba a few times, upgraded hardware,  
and changed operating systems from RHEL to Fedora Core 6.  The Fedora  
Core 6 migration happened a couple of weeks ago, including running  
samba from RPM available from 'yum update', and things seemed to be  
going OK, but today I see some ominous messages.

So this is:

Fedora Core 6 with recent updates
smbd -V reports: Version 3.0.24-5.fc6

I'll be happy to provide samba.conf file, or whatever, but maybe it's  
unnecessary.  Have I bumped into a bug in the samba code?

First of all I get a lot of these:

Jun  1 17:16:58 server smbd[17051]:   read_socket_with_timeout:  
timeout read. select error = Invalid argument.
Jun  1 17:17:18 server smbd[17051]: [2007/06/01 17:17:18, 0] lib/ 
fault.c:fault_report(41)

And then this fun stuff:

Jun  1 17:17:18 server smbd[17051]:    
==============================================================Jun  1 17:17:18
server smbd[17051]: [2007/06/01 17:17:18, 0] lib/
fault.c:fault_report(42)
Jun  1 17:17:18 server smbd[17051]:   INTERNAL ERROR: Signal 11 in  
pid 17051 (3.0.24-5.fc6)
Jun  1 17:17:18 server smbd[17051]:   Please read the Trouble- 
Shooting section of the Samba3-HOWTO
Jun  1 17:17:18 server smbd[17051]: [2007/06/01 17:17:18, 0] lib/ 
fault.c:fault_report(44)
Jun  1 17:17:18 server smbd[17051]:
Jun  1 17:17:18 server smbd[17051]:   From: http://www.samba.org/ 
samba/docs/Samba3-HOWTO.pdf
Jun  1 17:17:18 server smbd[17051]: [2007/06/01 17:17:18, 0] lib/ 
fault.c:fault_report(45)
Jun  1 17:17:18 server smbd[17051]:    
==============================================================Jun  1 17:17:18
server smbd[17051]: [2007/06/01 17:17:18, 0] lib/
util.c:smb_panic(1621)
Jun  1 17:17:18 server smbd[17051]:   PANIC (pid 17051): internal error
Jun  1 17:17:18 server smbd[17051]: [2007/06/01 17:17:18, 0] lib/ 
util.c:log_stack_trace(1728)
Jun  1 17:17:18 server smbd[17051]:   BACKTRACE: 25 stack frames:
Jun  1 17:17:18 server smbd[17051]:    #0 smbd(log_stack_trace+0x2d)  
[0x802253fd]
Jun  1 17:17:18 server smbd[17051]:    #1 smbd(smb_panic+0x5d)  
[0x8022552d]
Jun  1 17:17:18 server smbd[17051]:    #2 smbd [0x802109ca]
Jun  1 17:17:18 server smbd[17051]:    #3 [0xb9a420]
Jun  1 17:17:18 server smbd[17051]:    #4 smbd [0x80229e3a]
Jun  1 17:17:18 server smbd[17051]:    #5 smbd(receive_smb_raw+0x34)  
[0x80229f44]
Jun  1 17:17:18 server smbd[17051]:    #6 smbd(cli_receive_smb+0x53)  
[0x800cac43]
Jun  1 17:17:18 server smbd[17051]:    #7 smbd(cli_session_request 
+0x121) [0x800cb7f1]
Jun  1 17:17:18 server smbd[17051]:    #8 smbd(cli_start_connection 
+0x1d4) [0x800cc704]
Jun  1 17:17:18 server smbd[17051]:    #9 smbd(cli_full_connection 
+0x70) [0x800cfa40]
Jun  1 17:17:18 server smbd[17051]:    #10 smbd(_spoolss_rffpcnex 
+0x2ce) [0x80142f0e]
Jun  1 17:17:18 server smbd[17051]:    #11 smbd [0x8012df84]
Jun  1 17:17:18 server smbd[17051]:    #12 smbd(api_rpcTNP+0x1dd)  
[0x8016c73d]
Jun  1 17:17:18 server smbd[17051]:    #13 smbd(api_pipe_request 
+0x19e) [0x8016cdbe]
Jun  1 17:17:18 server smbd[17051]:    #14 smbd [0x80168703]
Jun  1 17:17:18 server smbd[17051]:    #15 smbd [0x80168c4c]
Jun  1 17:17:18 server smbd[17051]:    #16 smbd(write_to_pipe+0x71)  
[0x80167431]
Jun  1 17:17:18 server smbd[17051]:    #17 smbd [0x8005ffca]
Jun  1 17:17:18 server smbd[17051]:    #18 smbd [0x800604d6]
Jun  1 17:17:18 server smbd[17051]:    #19 smbd(reply_trans+0x5de)  
[0x80060dde]
Jun  1 17:17:18 server smbd[17051]:    #20 smbd [0x800b7f70]
Jun  1 17:17:18 server smbd[17051]:    #21 smbd(smbd_process+0x7ab)  
[0x800b909b]
Jun  1 17:17:18 server smbd[17051]:    #22 smbd(main+0xbd0) [0x802d4150]
Jun  1 17:17:18 server smbd[17051]:    #23 /lib/libc.so.6 
(__libc_start_main+0xdc) [0x503f2c]
Jun  1 17:17:18 server smbd[17051]:    #24 smbd [0x80043051]
Jun  1 17:17:18 server smbd[17051]: [2007/06/01 17:17:18, 0] lib/ 
fault.c:dump_core(168)
Jun  1 17:17:18 server smbd[17051]:   unable to change to /var/log/ 
samba/cores/smbdrefusing to dump core
Jun  1 19:08:58 server smbd[18848]: [2007/06/01 19:08:58, 0] lib/ 
util_sock.c:read_data(534)
Jun  1 19:08:58 server smbd[18848]:   read_data: read failure for 4  
bytes to client 192.168.192.220. Error = No route to host

I restarted samba, and it's not complaining now-- but it's the  
weekend so I don't expect to see much traffic until Monday.

Thanks