samba - Apr 2000 - sig 11

Linux 2.2.13
Intel

samba-2.0.7pre2 will Sig11 and die on me right after processing
NetBIOS name = FOO in smb.conf.

Not always, but sometimes I have to start smbd 2 or 3 times.
It always fails there.

Any reason why 2.0.7pre2 would do this, and 2.0.6 (from rpm)
never did?
-- 
Edward Schernau			http://www.schernau.com
Network Architect		mailto:ed@schernau.com
Rational Computing		Providence, RI, USA

Edward Schernau wrote:
> 
> Linux 2.2.13
> Intel
> 
> samba-2.0.7pre2 will Sig11 and die on me right after processing
> NetBIOS name = FOO in smb.conf.
> 
> Not always, but sometimes I have to start smbd 2 or 3 times.
> It always fails there.
> 
> Any reason why 2.0.7pre2 would do this, and 2.0.6 (from rpm)
> never did?
Yes, it's a bug :-). I fixed this in 2.0.7pre3. Please
test it :-).

Regards,

	Jeremy Allison,
	Samba Team.

-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------

I have been having a similar problem. I have samba 2.0.6 running on suse 6.2
set up as a stand alone server. All of my shares are on the /home/
filesystem which is on a SCSI drive while the rest of the filesystems are on
/dev/hda. When I am transferring files to/from the samba server from any
client I will sometimes get a kernel panic, sometimes the machine will
spontaneously reboot. I've switched NIC's with no change. The crashes
happen
more often if the files being copied are nested in deep directories.

I suspect a SCSI problem but wanted to post here in case this is a known
samba problem.

Michael Martin

Thomas Heiligenmann wrote:
>Carsten Nordstr?m Jensen wrote:
>
>> ---------------------------------------------------------------------
>> An exception OE has appeared at 0028:C104311B in VxD ELNK3(01)+
>> 00000E4B. This was called from 0028:C004374B in VxD NDIS(01)+
>> 00006733. You may be able to continue as normal.
>> ---------------------------------------------------------------------
>> I am NOT able to continue, I am not even able to restart
>> the computer normally, have to use power off/power on
>> method....
>
>Looks like a NIC drivers problem. Have you downloaded the latest
>drivers from your NIC manufacturer? You should also install the
"newer"
>Win95 releases ("Win95b" or "Win95c") on your clients or
apply MS'
>Win95 service releases.
>
>--
>Thomas
>