Package: samba Version: 3.0.21a-1 Severity: normal I did an upgrade yesterday, and since then I'm being bombarded with "Segfault in Samba" email messages.
>From smbd.log: [2006/02/03 12:25:51, 1] smbd/service.c:make_connection_snum(666) jop (192.168.170.196) connect to service data initially as user gpsshop (uid=1015, gid=100) (pid 24888) [2006/02/03 12:26:04, 2] smbd/open.c:open_file(369) gpsshop opened file firmware/Quest2/Quest2_250.exe read=Yes write=No (numopen= 2) [2006/02/03 12:26:04, 2] smbd/close.c:close_normal_file(281) gpsshop closed file firmware/Quest2/Quest2_250.exe (numopen=1) [2006/02/03 12:26:04, 2] smbd/open.c:open_file(369) gpsshop opened file firmware/Quest2/Quest2_250.exe read=Yes write=No (numopen= 2) [2006/02/03 12:26:06, 0] lib/fault.c:fault_report(36) =============================================================== [2006/02/03 12:26:06, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 10 in pid 24888 (3.0.21a-Debian) Please read the Trouble-Shooting section of the Samba3-HOWTO [2006/02/03 12:26:06, 0] lib/fault.c:fault_report(39) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2006/02/03 12:26:06, 0] lib/fault.c:fault_report(40) =============================================================== [2006/02/03 12:26:06, 0] lib/util.c:smb_panic2(1544) smb_panic(): calling panic action [/usr/share/samba/panic-action 24888] [2006/02/03 12:26:06, 0] lib/util.c:smb_panic2(1552) smb_panic(): action returned status 0 [2006/02/03 12:26:06, 0] lib/util.c:smb_panic2(1554) PANIC: internal error [2006/02/03 12:26:06, 0] lib/util.c:smb_panic2(1562) BACKTRACE: 0 stack frames: Note that the email subject is wrong: it's not a SIGSEGV, it's a SIGBUS. These are generally due to unaligned accesses to memory (e.g. accessing a 32-bit integer from an address where (address % 4) != 0 ). On sparc, unfortunately, I don't know how to track these down :-( I'll try to reproduce it on an alpha (the kernel there is helpful enough to report such accesses and to fix them up, although there's a significant speed penalty). In the meantime I've downgraded to 3.0.14a-sarge1; up to now no problems. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
