Bug#444003: capi4hylafax: After running perfectly for a whilec2faxsend/c2faxrecv processes freezes.
Hi Lionel, Thank you for answering my bug report. Quoting Lionel Elie Mamane [EMAIL PROTECTED]: On Mon, Oct 01, 2007 at 10:31:50PM +0200, Stig Even Larsen wrote: Today the faxserver had another failure. Se attached info for specifics. Thank you for your bug report, and sorry it took me so long to react to it. I think you have found a bug in the kernel CAPI layer and/or AVM C2 driver. Might be related to http://bugzilla.kernel.org/show_bug.cgi?id=5064 or not. There was a time where I was forwarding that kind of bug reports to AVM, and getting successful resolutions from them, but they have gone silent on me; stopped reacting to me emails. So there is not much I can do. If/when linux kernel bug #5064 gets addressed you still get that kind of problem, we can file a separate kernel bug. Check you are using the latest firmware for your AVM C2; that was always the first question AVM asked me :) We are using the follwing file ftp://ftp.in-berlin.de/pub/capi4linux/firmware/c2/3-11-06/c2.bin Since this file has the latest timestamp I'm assuming that this is the latest firmware. Can you confirm this? -- Lionel Best regards, Stig Even Larsen CTO Nimra Norge AS
Bug#444003: Info received (Bug#444003: Acknowledgement (capi4hylafax: After running perfectly for a while c2faxsend/c2faxrecv processes freezes.))
Today the faxserver had another failure. Se attached info for specifics. Do you need more info? faxserver-ny:~# uptime 22:30:13 up 6 days, 10:27, 2 users, load average: 3.00, 3.01, 2.59 faxserver-ny:~# ps aux|grep c2 uucp 2630 0.0 0.2 71304 2572 ?Ssl Sep25 0:00 /usr/bin/c2faxrecv uucp 17767 0.0 0.1 11856 1564 ?S21:54 0:00 c2faxsend -m faxCAPI11 sendq/q562 uucp 17962 0.0 0.1 3560 1496 ?D21:55 0:00 c2faxsend -m faxCAPI22 sendq/q563 uucp 17996 0.0 0.1 3564 1504 ?D21:57 0:00 c2faxsend -m faxCAPI12 sendq/q560 uucp 18067 0.0 0.1 3564 1496 ?D22:01 0:00 c2faxsend -m faxCAPI21 sendq/q564 root 18168 0.0 0.0 2852 716 pts/1S+ 22:06 0:00 grep c2 From /var/log/syslog Oct 1 21:55:42 faxserver-ny kernel: BUG: unable to handle kernel paging request at virtual address 00100104 Oct 1 21:55:42 faxserver-ny kernel: printing eip: Oct 1 21:55:42 faxserver-ny kernel: f89a1439 Oct 1 21:55:42 faxserver-ny kernel: *pde = Oct 1 21:55:42 faxserver-ny kernel: Oops: 0002 [#1] Oct 1 21:55:42 faxserver-ny kernel: SMP Oct 1 21:55:42 faxserver-ny kernel: Modules linked in: ipv6 ppdev parport_pc lp parport button ac battery capi capifs dm_snapshot dm_mirror dm_mod loop tsdev rtc c4 b1 i2c_i801 floppy kernelcapi i2c_core serio_raw pcspkr psmouse shpchp pci_hotplug e752x_edac edac_mc evdev sg ext3 jbd mbcache ide_cd cdrom sd_mod generic ips scsi_mod piix ide_core i2o_core ehci_hcd uhci_hcd tg3 usbcore thermal processor fan Oct 1 21:55:42 faxserver-ny kernel: CPU:1 Oct 1 21:55:42 faxserver-ny kernel: EIP:0060:[f89a1439]Not tainted VLI Oct 1 21:55:42 faxserver-ny kernel: EFLAGS: 00010296 (2.6.18-4-686 #1) Oct 1 21:55:42 faxserver-ny kernel: EIP is at capilib_release_appl+0x28/0x53 [kernelcapi] Oct 1 21:55:42 faxserver-ny kernel: eax: 00200200 ebx: f60802c0 ecx: 0092 edx: 00100100 Oct 1 21:55:42 faxserver-ny kernel: esi: dffd164c edi: 000a ebp: dffd164c esp: e6553f48 Oct 1 21:55:42 faxserver-ny kernel: ds: 007b es: 007b ss: 0068 Oct 1 21:55:42 faxserver-ny kernel: Process c2faxsend (pid: 17768, ti=e6552000 task=e911c000 task.ti=e6552000) Oct 1 21:55:42 faxserver-ny kernel: Stack: f89a3821 000a 00020201 dffd14c8 000a c192c000 dfb4c114 f89acef0 Oct 1 21:55:42 faxserver-ny kernel:dffd14c8 c19f3dc8 f899f699 c19f3dc0 dff6bf00 dfcc70a0 f89992aa Oct 1 21:55:42 faxserver-ny kernel:0008 dff6bf00 c015ae41 c18dcac0 dff6bf00 dffbf980 e6552000 Oct 1 21:55:42 faxserver-ny kernel: Call Trace: Oct 1 21:55:42 faxserver-ny kernel: [f89acef0] c4_release_appl+0x1d/0xea [c4] Oct 1 21:55:42 faxserver-ny kernel: [f899f699] capi20_release+0x5c/0xc4 [kernelcapi] Oct 1 21:55:42 faxserver-ny kernel: [f89992aa] capi_release+0x16/0x8b [capi] Oct 1 21:55:42 faxserver-ny kernel: [c015ae41] __fput+0x8a/0x13f Oct 1 21:55:42 faxserver-ny kernel: [c01589aa] filp_close+0x4e/0x54 Oct 1 21:55:42 faxserver-ny kernel: [c0102c11] sysenter_past_esp+0x56/0x79 Oct 1 21:55:42 faxserver-ny kernel: Code: 5b 5e c3 55 89 c5 57 0f b7 fa 56 53 8b 18 8b 33 eb 39 66 39 7b 08 75 2f ff 73 0c 57 68 21 38 9a f8 e8 36 c5 77 c7 8b 43 04 8b 13 89 42 04 89 10 89 d8 c7 03 00 01 10 00 c7 43 04 00 02 20 00 e8 Oct 1 21:55:42 faxserver-ny kernel: EIP: [f89a1439] capilib_release_appl+0x28/0x53 [kernelcapi] SS:ESP 0068:e6553f48 Oct 1 22:01:22 faxserver-ny FaxQueuer[2729]: No devices available Regards, Stig Even Larsen Nimra Norge AS email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444003: capi4hylafax: After running perfectly for a while c2faxsend/c2faxrecv processes freezes.
Package: capi4hylafax Version: 1:01.03.00.99.svn.300-4 Severity: important -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages capi4hylafax depends on: ii capiutils 1:3.9.20060704-3 Utilities for CAPI-capable ISDN ca ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libcapi20-31:3.9.20060704-3 libraries for CAPI support ii libgcc11:4.1.1-21GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages capi4hylafax recommends: pn hylafax-servernone (no description available) pn isdnactivecards none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444003: Acknowledgement (capi4hylafax: After running perfectly for a while c2faxsend/c2faxrecv processes freezes.)
Hi, I suppose you will be needing some additional info regarding this incident. The capi4hylafax packages it configured to work witch the AVM C2 ISDN card in a IBM xSeries 346, and is a fax-server which sends approximately 100 faxes a day. After some time (perhaps 2 weeks) the c2sendfax/c2faxrecv stops responding. If the c2sendfax/c2faxrecv process is i 'D' status I need to reboot the system to get it operational, otherwise I will be able to stop hylafax and c2sendfax/c2faxrecv processes and restart the capiutils (e.g removing and inserting kernel modules). This time I was actually monitoring syslog and tried immediatly to resolv this by stopping hylafax, capi4hylafax and capiutils, but with no success. c2sendfax/c2faxrecv prosesses could not be killed, thus had to restart the server. The following was found in /var/log/syslog Sep 25 11:42:50 faxserver-ny kernel: BUG: unable to handle kernel paging request at virtual address 00100104 Sep 25 11:42:50 faxserver-ny kernel: printing eip: Sep 25 11:42:50 faxserver-ny kernel: f89b3439 Sep 25 11:42:50 faxserver-ny kernel: *pde = Sep 25 11:42:50 faxserver-ny kernel: Oops: 0002 [#1] Sep 25 11:42:50 faxserver-ny kernel: SMP Sep 25 11:42:50 faxserver-ny kernel: Modules linked in: c4 b1 tcp_diag inet_diag iptable_filter ip_tables x_tables ipv6 ppdev parport_pc lp parport button ac battery capi capifs dm_snapshot dm_mirror dm_mod loop tsdev kernelcapi floppy rtc serio_raw pcspkr shpchp pci_hotplug i2c_i801 i2c_core psmouse e752x_edac edac_mc evdev sg ext3 jbd mbcache ide_cd cdrom sd_mod generic piix ide_core ips scsi_mod3kcapi: handle_message: applid 10 state released (LISTEN_CONFID=010 #0x LEN=0014 Sep 25 11:42:50 faxserver-ny kernel: Controller/PLCI/NCCI= 0x1 Sep 25 11:42:50 faxserver-ny kernel: Info= 0x0 Sep 25 11:42:50 faxserver-ny kernel: ) Sep 25 11:42:50 faxserver-ny kernel: ehci_hcd uhci_hcd i2o_core tg3 usbcore thermal processor fan Sep 25 11:42:50 faxserver-ny kernel: CPU:1 Sep 25 11:42:50 faxserver-ny kernel: EIP:0060:[f89b3439]Not tainted VLI Sep 25 11:42:50 faxserver-ny kernel: EFLAGS: 00010296 (2.6.18-4-686 #1) Sep 25 11:42:50 faxserver-ny kernel: EIP is at capilib_release_appl+0x28/0x53 [kernelcapi] Sep 25 11:42:50 faxserver-ny kernel: eax: 00200200 ebx: f7cd2540 ecx: 0092 edx: 00100100 Sep 25 11:42:50 faxserver-ny kernel: esi: e6ccfca0 edi: 000a ebp: e6ccfca0 esp: e5d35f48 Sep 25 11:42:50 faxserver-ny kernel: ds: 007b es: 007b ss: 0068 Sep 25 11:42:50 faxserver-ny kernel: Process c2faxsend (pid: 24527, ti=e5d34000 task=e137e000 task.ti=e5d34000) Sep 25 11:42:50 faxserver-ny kernel: Stack: f89b5821 000a 00010102 e6ccfb1c 000a e0abb000 c191f42c f8955ef0 Sep 25 11:42:50 faxserver-ny kernel:e6ccfb1c e6878cc8 0001 f89b1699 e6878cc0 f7d9fa80 c1911260 f89982aa Sep 25 11:42:50 faxserver-ny kernel:0008 f7d9fa80 c015ae41 c18dcb40 f7d9fa80 e4b90480 e5d34000 Sep 25 11:42:50 faxserver-ny kernel: Call Trace: Sep 25 11:42:50 faxserver-ny kernel: [f8955ef0] c4_release_appl+0x1d/0xea [c4] Sep 25 11:42:50 faxserver-ny kernel: [f89b1699] capi20_release+0x5c/0xc4 [kernelcapi] Sep 25 11:42:50 faxserver-ny kernel: [f89982aa] capi_release+0x16/0x8b [capi] Sep 25 11:42:50 faxserver-ny kernel: [c015ae41] __fput+0x8a/0x13f Sep 25 11:42:50 faxserver-ny kernel: [c01589aa] filp_close+0x4e/0x54 Sep 25 11:42:50 faxserver-ny kernel: [c0102c11] sysenter_past_esp+0x56/0x79 Sep 25 11:42:50 faxserver-ny kernel: Code: 5b 5e c3 55 89 c5 57 0f b7 fa 56 53 8b 18 8b 33 eb 39 66 39 7b 08 75 2f ff 73 0c 57 68 21 58 9b f8 e8 36 a5 76 c7 8b 43 04 8b 13 89 42 04 89 10 89 d8 c7 03 00 01 10 00 c7 43 04 00 02 20 00 e8 Sep 25 11:42:50 faxserver-ny kernel: EIP: [f89b3439] capilib_release_appl+0x28/0x53 [kernelcapi] SS:ESP 0068:e5d35f48 Sep 25 11:45:35 faxserver-ny FaxQueuer[8134]: DEST (0x8076b50: 0 ready, 1 batches, 0 sleeping:) Picking next job Sep 25 11:45:35 faxserver-ny FaxQueuer[8134]: DEST (0x8076b50: 0 ready, 1 batches, 0 sleeping:) Empty - removing Sep 25 11:45:44 faxserver-ny kernel: 7capilib_new_ncci: kcapi: appl 1 ncci 0x10101 up Sep 25 11:46:05 faxserver-ny FaxQueuer[8134]: QUIT Regards, Stig Even Larsen Nimra Norge AS phone: +47 70 111 500 email: [EMAIL PROTECTED] Debian Bug Tracking System wrote: Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to [EMAIL PROTECTED] (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Lionel Elie Mamane [EMAIL PROTECTED] If you wish to submit further
