[Samba] internal error: signal 11

Frank Matthieß fm+samba at Microdata-POS.de
Thu Oct 31 09:34:00 GMT 2002


On Wed, Oct 30, 2002 at 11:35:42AM +0000, Gerhard Vögel wrote:
> Hello,
> 
> we got the following error in the samba logs:
> 
> Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] 
> lib/fault.c:fault_report(38) 
> Oct 30 06:29:01 hornbill smbd[12783]:   
> =============================================================== 
> Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] 
> lib/fault.c:fault_report(39) 
> Oct 30 06:29:01 hornbill smbd[12783]:   INTERNAL ERROR: Signal 11 in pid 
> 12783 (2.2.6-SuSE) 
> Oct 30 06:29:01 hornbill smbd[12783]:   Please read the file BUGS.txt in 
> the distribution 
> Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] 
> lib/fault.c:fault_report(41) 
> Oct 30 06:29:01 hornbill smbd[12783]:   
> =============================================================== 
> Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] 
> lib/util.c:smb_panic(1094) 
> Oct 30 06:29:01 hornbill smbd[12783]:   PANIC: internal error 
> Oct 30 06:29:01 hornbill smbd[12783]: 
> 
> The error is continuously repeated with increased pids until the machine 
> will be rebooted. Restart of smbd, nmbd and winbind has no effect.
> 
> Clients can connect to samba but they cannot access files. File access on 
> NT clients is aborted with different messages. 
> 
> Samba version is 2.2.6 (Suse RPM) and linux kernel is 2.4.19, but it 
> already happened with 2.2.4 and kernel 2.4.16. I cannot reproduce the 
> error, but it happens once in a week.
> 
> I found similar errors discussed in the list archives but no explanation 
> or solution.
> 
> Can anybody help.


The last timer i got this type of error, it was an hardware problem.
Some years ago i compiled e kernel on an 'stable' System, which runs
novell netware 3.1 for years. The gcc failes with "internal error:
signal 11".

This was an hardware with PS/2 RAM. One module has another speed (70ns)
than the other (60ns), so this was an timing issue of the hardware and
not the os or software.

Take a look to the memory sub system. More than one module? Same Timing?

-- 
Frank Matthieß                                    fm+samba at Microdata-pos.de




More information about the samba mailing list