Your message dated Wed, 9 May 2012 18:15:05 +0200
with message-id <[email protected]>
and subject line Closing panic bug with Windows 7 printing
has caused the Debian Bug report #622673,
regarding panic-action segfault involving _spoolss_EnumPrinters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
622673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622673
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:3.5.8~dfsg-1
I'm seeing a Samba panic-action a couple times a day, just starting
recently. It appears to come from a computer running Windows 7. This
backtrace was generated after I installed samba-dbg and restarted smbd
but it doesn't look like any extra information was provided as a result.
Like the other poster, the core was not present in the given directory
after the crash occurred.
[2011/04/13 11:26:51.160760, 0] lib/fault.c:46(fault_report)
===============================================================
[2011/04/13 11:26:51.160815, 0] lib/fault.c:47(fault_report)
INTERNAL ERROR: Signal 11 in pid 10507 (3.5.8)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2011/04/13 11:26:51.160840, 0] lib/fault.c:49(fault_report)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2011/04/13 11:26:51.160863, 0] lib/fault.c:50(fault_report)
===============================================================
[2011/04/13 11:26:51.160881, 0] lib/util.c:1465(smb_panic)
PANIC (pid 10507): internal error
[2011/04/13 11:26:51.163986, 0] lib/util.c:1569(log_stack_trace)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x1a) [0x7f9ba54221fa]
#1 /usr/sbin/smbd(smb_panic+0x1f) [0x7f9ba54222bf]
#2 /usr/sbin/smbd(+0x377ae9) [0x7f9ba5411ae9]
#3 /lib/libc.so.6(+0x321e0) [0x7f9ba24ce1e0]
#4 /usr/sbin/smbd(_spoolss_EnumPrinters+0x54a) [0x7f9ba536443a]
#5 /usr/sbin/smbd(+0x2e653c) [0x7f9ba538053c]
#6 /usr/sbin/smbd(+0x3101ae) [0x7f9ba53aa1ae]
#7 /usr/sbin/smbd(api_pipe_request+0x1a8) [0x7f9ba53af098]
#8 /usr/sbin/smbd(np_write_send+0x174a) [0x7f9ba53a7c0a]
#9 /usr/sbin/smbd(+0x118a59) [0x7f9ba51b2a59]
#10 /usr/sbin/smbd(+0x118cd2) [0x7f9ba51b2cd2]
#11 /usr/sbin/smbd(reply_trans+0x637) [0x7f9ba51b35c7]
#12 /usr/sbin/smbd(+0x17a505) [0x7f9ba5214505]
#13 /usr/sbin/smbd(+0x17a8a7) [0x7f9ba52148a7]
#14 /usr/sbin/smbd(+0x17ad00) [0x7f9ba5214d00]
#15 /usr/sbin/smbd(run_events+0x1eb) [0x7f9ba543186b]
#16 /usr/sbin/smbd(smbd_process+0x7f5) [0x7f9ba5216305]
#17 /usr/sbin/smbd(+0x682bfa) [0x7f9ba571cbfa]
#18 /usr/sbin/smbd(run_events+0x1eb) [0x7f9ba543186b]
#19 /usr/sbin/smbd(+0x397a63) [0x7f9ba5431a63]
#20 /usr/sbin/smbd(_tevent_loop_once+0x90) [0x7f9ba5432500]
#21 /usr/sbin/smbd(main+0xad3) [0x7f9ba571d893]
#22 /lib/libc.so.6(__libc_start_main+0xfd) [0x7f9ba24bac4d]
#23 /usr/sbin/smbd(+0xfd2d9) [0x7f9ba51972d9]
[2011/04/13 11:26:51.164095, 0] lib/util.c:1470(smb_panic)
smb_panic(): calling panic action [/usr/share/samba/panic-action 10507]
[2011/04/13 11:26:52.211609, 0] lib/util.c:1478(smb_panic)
smb_panic(): action returned status 0
[2011/04/13 11:26:52.211680, 0] lib/fault.c:326(dump_core)
dumping core in /var/log/samba/cores/smbd
--
Joshua Kwan
--- End Message ---
--- Begin Message ---
Version: 2:3.6.1-1
Samba 3.6 fixes several problems involving printing from Windows 7
clients, some of which we even backported to squeeze.
I highly suspect these panics are among these and therefore I'm closing
this bug report with version tagging.
Please open a new bug if some panics still happen with Windows 7 printing.
--
signature.asc
Description: Digital signature
--- End Message ---
