Re: isdn4linux with Kernel 3.2

>
> No the old stuff is still here and not changed so much, so everything
> should work with the original configs. I did not test it by myself for
> about 2 years, but nothing was changed, if something doesn't work,
> it could be a side effect of some other changes in the network layer -
> but I'm not aware of anything.
>

Hi Karsten

Thanks for the infos. They made me try again and indeed
isdn4linux does still work on a 64bit machine running
kernel 3.2.47.

I only had to change two things in isdn4k-utils.v3.2p1

1) the lxdialog-Makefile searches for the ncurses library
in /lib und /usr/lib only. On my system it's in /usr/lib64

2) the following code in line 713 of libtool.c does not compile
anymore:

switch(...){
  case: ......
  case: ......
  default:
}

I just removed the default:-line

Now I have one final problem:

Once in a while the kernel display the following messages and
ISDN stops working:

isdn0: dialing 1 0123456789...
isdn_net: local hangup isdn0
isdn0: Chargesum is 0
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x131/0x1eb()
Hardware name: X8SIL
NETDEV WATCHDOG: isdn0 (): transmit queue 0 timed out
Pid: 0, comm: swapper/7 Not tainted 3.2.47-backup #2
Call Trace:
 <IRQ>  [<ffffffff81260264>] ? dev_watchdog+0x131/0x1eb
 [<ffffffff81025821>] ? warn_slowpath_common+0x71/0x85
 [<ffffffff81025896>] ? warn_slowpath_fmt+0x45/0x4a
 [<ffffffff81260264>] ? dev_watchdog+0x131/0x1eb
 [<ffffffff8102de5d>] ? cascade+0x5b/0x74
 [<ffffffff8102dfb5>] ? run_timer_softirq+0x13f/0x1cc
 [<ffffffff81260133>] ? noop_enqueue+0xd/0xd
 [<ffffffff81029acf>] ? __do_softirq+0x82/0x104
 [<ffffffff812b80ec>] ? call_softirq+0x1c/0x30
 [<ffffffff81002cfd>] ? do_softirq+0x2c/0x5f
 [<ffffffff81029cf2>] ? irq_exit+0x3e/0x59
 [<ffffffff81012187>] ? smp_apic_timer_interrupt+0x82/0x8f
 [<ffffffff812b768b>] ? apic_timer_interrupt+0x6b/0x70
 <EOI>  [<ffffffff81163b78>] ? acpi_idle_enter_bm+0x230/0x26e
 [<ffffffff81163b73>] ? acpi_idle_enter_bm+0x22b/0x26e
 [<ffffffff8122eaf2>] ? cpuidle_idle_call+0x6f/0xb6
 [<ffffffff81000662>] ? cpu_idle+0x47/0x86
---[ end trace cc1daf3e31834350 ]---

The net is full of similar messages. Mostly these problems are fixed
by using a newer version of the ethernet driver. And some people
suggest to disable acpi. That's what I did and I will let you know
wether that helped or not.

Peter

_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux