Christian Richter schrieb:
Hi,
this is the only difference in hfc_pci.c between 1.1.2 and 1.1.3, this
only happens when the driver is loaded initially, so i can't understand
why this should result in a Kernel Panic after a few seconds.
[EMAIL PROTECTED]:/tmp/mISDN-1_1_2$ diff -u
drivers/isdn/hardware/mISDN/hfc_pci.c
../mISDN-1_1_3/drivers/isdn/hardware/mISDN/hfc_pci.c
--- drivers/isdn/hardware/mISDN/hfc_pci.c 2006-12-21
16:25:06.000000000 +0100
+++ ../mISDN-1_1_3/drivers/isdn/hardware/mISDN/hfc_pci.c
2007-05-09 11:53:28.000000000 +0200
@@ -1880,7 +1880,7 @@
hc->hw.cirm = 0;
hc->dch.state = 0;
while (id_list[i].vendor_id) {
- tmp_hfcpci = pci_find_device(id_list[i].vendor_id,
+ tmp_hfcpci = pci_get_device(id_list[i].vendor_id,
id_list[i].device_id, dev_hfcpci);
i++;
if (tmp_hfcpci) {
I can reproduce the panic with just unloading misdn with the misdn-init
script.
I opened an bug report on isdn4linux. As bug 100 ! ;)
https://www.isdn4linux.de/mantis/view.php?id=100
After changing the code back to
pci_find_device(...)
everything works fine.
Maybe there is a problem with this kernel function ?
Thx,
Jörg Esser
_______________________________________________
Misdn-asterisk mailing list
[email protected]
http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk
