Capi hangs kernel? -- debugging hints?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,


since I'm desperate now I hope someone could provide me a hint:

I'm using 2.4.19 (although the problem is the same in 2.4.10 and 2.4.18)
and AVM's passive ISDN card Fritz!PCI. The card works fine under i4l but
since I would need fax services I'm trying to use the capi drivers
(fcpci.o and so on) provided by them.

I'm able to successfully load all the CAPI modules, like:


Oct 22 21:07:01 buffy kernel: CAPI-driver Rev 1.1.4.1: loaded
Oct 22 21:07:01 buffy kernel: capifs: Rev 1.1.4.1
Oct 22 21:07:01 buffy kernel: capi20: started up with major 68
Oct 22 21:07:01 buffy kernel: kcapi: capi20 attached
Oct 22 21:07:01 buffy kernel: capi20: Rev 1.1.4.2: started up with major 68 (middleware+capifs)
Oct 22 21:07:01 buffy kernel: fcpci: AVM FRITZ!Card PCI driver, revision 0.2
Oct 22 21:07:01 buffy kernel: fcpci: (fcpci built on Oct 22 2002 at 20:41:35)
Oct 22 21:07:01 buffy kernel: fcpci: Loading...
Oct 22 21:07:01 buffy kernel: fcpci: Driver 'fcpci' attached to stack
Oct 22 21:07:01 buffy kernel: kcapi: driver fcpci attached
Oct 22 21:07:01 buffy kernel: fcpci: Auto-attaching...
Oct 22 21:07:01 buffy kernel: PCI: Found IRQ 5 for device 00:12.0
Oct 22 21:07:01 buffy kernel: fcpci: Stack version 3.09-10
Oct 22 21:07:01 buffy kernel: kcapi: Controller 1: fritz-pci attached
Oct 22 21:07:01 buffy kernel: kcapi: card 1 "fritz-pci" ready.
Oct 22 21:07:01 buffy kernel: fcpci: Loaded.
Oct 22 21:07:01 buffy kernel: kcapi: notify up contr 1
Oct 22 21:07:01 buffy kernel: capi: controller 1 up
Oct 22 21:07:08 buffy kernel: ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded


(sorry don't have a lsmod output at hand right now) -- but as soon as an
application like hylafax tries to use the CAPI interface the system locks
up and (new in 2.4.19) the 'Scroll' and 'Caps Lock' Leds blink.

I thought it might be something about irq sharing but my ISDN card seems
to be happy & alone on #5 (although I'm not absolutely sure) and I
disabled all mysterious BIOS options that might trigger bugs in my
motherboard (DFI K6BV3+) concerning irq sharing.

Any ideas how to investigate further?


\Urs
+-----------------------------------------------------------------------+
| sitb - IT Beratung                                                    |
|                                       Phone mobile:   +49 179 2945681 |
| Urs J. Schürer                        Phone office:   +49 89 72430265 |
| Boschetsrieder Str. 8                          Fax:   +49 89 72430266 |
| 81379 München, Germany                       Email:   urs@sitb.de     |
+-----------------------------------------------------------------------+

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux