<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: cipe 1.5.2 with kernel 2.4.5 problem
From: Stephan von Krawczynski <skraw,AT,ithnet,DOT,com>
Date: Tue, 3 Jul 2001 11:52:57 +0200

Hello all,

I am using cipe 1.5.2 together with kernel 2.4.5 and ran across the following
problem.

I am starting:

Jul  2 17:37:16 gate ciped-cb[13247]: CIPE daemon vers 1.5.2 (c) Olaf Titz
1996-2000
Jul  2 17:37:16 gate kernel: cipcb: CIPE driver vers 1.5.2 (c) Olaf Titz
1996-2000, 2 channels, debug=0
Jul  2 17:37:16 gate kernel: cipcb: rtnl_lock() at ../cipe/device.c:625
Jul  2 17:37:16 gate kernel: cipcb: rtnl_unlock() at ../cipe/device.c:627    
Jul  2 17:37:16 gate kernel: cipcb: read_lock(&tasklist_lock) at
./cipe/device.c:216
Jul  2 17:37:16 gate kernel: cipcb: read_unlock(&tasklist_lock) at
./cipe/device.c:225

after a while the device vanishes from the routing table, so a watchdog stops 
it:

Jul  2 18:04:00 gate modprobe: modprobe: Can't locate module net-pf-10
Jul  2 18:04:00 gate ciped-cb[13247]: Terminated
Jul  2 18:04:00 gate ciped-cb[13247]: Interface stats      276       3    0   
0    0     0          0         0      336
Jul  2 18:04:00 gate ciped-cb[13247]: KX stats: rreq=0, req=0, ind=0, indb=0,
ack=0, ackb=0, unknown=0
Jul  2 18:04:00 gate ciped-cb[13247]: cipcb0: daemon exiting

and restarts it again:

Jul  2 18:04:00 gate kernel: cipcb: read_lock(&tasklist_lock) at
./cipe/device.c:216
Jul  2 18:04:00 gate kernel: cipcb: read_unlock(&tasklist_lock) at
./cipe/device.c:220

What does that mean? I have not seen anything the like with cipe 1.4.x and
kernel 2.2.19. Any ideas welcome.

Regards,
Stephan





<< | Thread Index | >> ]    [ << | Date Index | >> ]