Has anyone had any problems with the slackware-current package "samba-3.0.3-i486-1.tgz"?

I updated from "samba-3.0.2a-i486-1.tgz" which was working fine and started having errors connecting from a Win98se machine and some share names wouldn't appear.

Excerpt from samba log...

**************************************************************************************************** ****
[2004/05/07 07:58:58, 0] lib/fault.c:fault_report(36)
===============================================================
[2004/05/07 07:58:58, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 25128 (3.0.3)
Please read the appendix Bugs of the Samba HOWTO collection
[2004/05/07 07:58:58, 0] lib/fault.c:fault_report(39)
===============================================================
[2004/05/07 07:58:58, 0] lib/util.c:smb_panic2(1398)
PANIC: internal error
[2004/05/07 07:58:58, 0] lib/util.c:smb_panic2(1406)
BACKTRACE: 18 stack frames:
#0 /usr/sbin/smbd(smb_panic2+0x111) [0x81c43e1]
#1 /usr/sbin/smbd(smb_panic+0x1a) [0x81c42ca]
#2 /usr/sbin/smbd [0x81b1ec8]
#3 /lib/libc.so.6 [0x40202078]
#4 /usr/sbin/smbd(authorise_login+0x24) [0x8085ad4]
#5 /usr/sbin/smbd [0x80cd164]
#6 /usr/sbin/smbd(make_connection+0x12f) [0x80cd68f]
#7 /usr/sbin/smbd(reply_tcon_and_X+0x1ac) [0x809af7c]
#8 /usr/sbin/smbd [0x80ca400]
#9 /usr/sbin/smbd(chain_reply+0x17a) [0x80cad2a]
#10 /usr/sbin/smbd(reply_sesssetup_and_X+0x4fc) [0x80a882c]
#11 /usr/sbin/smbd [0x80ca400]
#12 /usr/sbin/smbd [0x80ca660]
#13 /usr/sbin/smbd(process_smb+0x8c) [0x80ca86c]
#14 /usr/sbin/smbd(smbd_process+0x168) [0x80cb4e8]
#15 /usr/sbin/smbd(main+0x4d6) [0x82206b6]
#16 /lib/libc.so.6(__libc_start_main+0xc6) [0x401ee936]
#17 /usr/sbin/smbd [0x8075001]
**************************************************************************************************** ****

I've gone back to 3.0.2a and everything is back to normal but what happened?

I have the same problem on LM 10 running Samba 3.0.2a.
It's on my live school server so samba is not the only thing in panic.
I've discovered it today. No solutions on the official samba site.
It only seems to happen with MS Office XP, 2003, products on Win XP
It does not happen with Office 2000 on Win98

Slackware Samba is up to 3.0.6 now, some of the changes were bug fixes and some essential security fixes, so you should upgrade