So I've got a PBX running with one Fritz card with the fcpci module and that works fine, but add another one and... kersplat... Kernel Panic. It boots fine with two cards, but panics as soon as the first fcpci.ko module is 'modprobe'd - I don't even get as far as modprobing the second. Any ideas on what's going on? Should I just back-up to an older version of the fcpci module or is this something I can get sorted with a few tweaks? Distro: Slackware 10 Kernel: 2.6.7 Fritz driver: fcpci-suse9.1-3.11-02.tar.gz CAPI utils: capi4k-utils-2004-06-14.tar.gz Chan CAPI: chan_capi.0.3.4a.tar.gz Thanks in advance of your help. Nick. -- BCN Information Technology Tel: 01676-530540 Fax: 01676-530541 VoIP (H323): 81.187.178.52 http://www.bcn-it.co.uk/ -- This message is intended only for the use of the intended recipient(s) to whom it is addressed. It may contain information which is privileged and confidential within the meaning of applicable law. If you are not the intended recipient, please contact the sender as soon as possible. The views expressed in this communication (including, but not limited to, any attachments) may not necessarily be the views held by BCN. Prices, recommendations or advice be they implied or otherwise, E&OE. This e-mail message has been swept for the presence of computer viruses, however no responsibility is accepted or implied for damage caused by any virus contained within it.
Hi,> It boots fine with two cards, but panics as soon as the first fcpci.ko > module is 'modprobe'd - I don't even get as far as modprobing the second.Are you sure that you compiled the module with exactly the same gcc as the kernel? Thomas
Hi,> Are you sure that you compiled the module with exactly the > same gcc as the kernel?Yup - I did the kernel compile, rebooted and then did the module compilation (and then asterisk and then chan_capi etc.). No other changes were made to the system. Cheers, Nick. -- BCN Information Technology Tel: 01676-530540 Fax: 01676-530541 VoIP (H323): 81.187.178.52 http://www.bcn-it.co.uk/ -- This message is intended only for the use of the intended recipient(s) to whom it is addressed. It may contain information which is privileged and confidential within the meaning of applicable law. If you are not the intended recipient, please contact the sender as soon as possible. The views expressed in this communication (including, but not limited to, any attachments) may not necessarily be the views held by BCN. Prices, recommendations or advice be they implied or otherwise, E&OE. This e-mail message has been swept for the presence of computer viruses, however no responsibility is accepted or implied for damage caused by any virus contained within it.
Hi, possible IRQ conflict? Do you see the binary (in the panic dump) which caused the kernel panic? Thomas
Thomas Karcher:> possible IRQ conflict?Ah, no. I finally worked out what it was... "All my fault" is the short answer! I was using kernel 2.6 with the SuSe 9.1 fcpci drivers. I dropped back to 2.4 and used the SuSe 8.2 drivers and it all appears to be working fine. Ho hum. Nick.