[cpia] webcamII + USB + vic : kernel BUG at cpia.c:245!

[Nicolas FAIVRET]

First of all, Many thanks to Peter Pregler and to Thomas Davis.

I get the cpia-0.7.3 drivers, at http://home.eunet.no/~jtotland/vision/. 
During the installation, I encounter some problems of unresolved symbol 
because my kernel was compiled with the option version information on module

symbols. 
And now everything seem to work fine, 

# dmesg
V4L-Driver for Vision CPiA based cameras v0.7.3
usb.c: registered new driver cpia
USB CPiA camera found
cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00
cpia.c(30419):goto_high_power(2300):camera now in HIGH power state
cpia.c(30421):goto_low_power(2314):camera now in LOW power state
cpia.c(30430):goto_high_power(2300):camera now in HIGH power state
cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1
cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1
cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0
cpia.c(30448):save_camera_state(2338):32/6/92
  CPiA Version: 1.20 (2.0)
  CPiA PnP-ID: 0553:0002:0100
  VP-Version: 1.0 0100
usb.c: cpia driver claimed interface c3a191e0  


but when I try 
# vic localhost/8000 
V4l: trying /dev/video0... Segmentation fault    
# dmesg
V4L-Driver for Vision CPiA based cameras v0.7.3
usb.c: registered new driver cpia
USB CPiA camera found
cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00
cpia.c(30419):goto_high_power(2300):camera now in HIGH power state
cpia.c(30421):goto_low_power(2314):camera now in LOW power state
cpia.c(30430):goto_high_power(2300):camera now in HIGH power state
cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1
cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1
cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0
cpia.c(30448):save_camera_state(2338):32/6/92
  CPiA Version: 1.20 (2.0)
  CPiA PnP-ID: 0553:0002:0100
  VP-Version: 1.0 0100
usb.c: cpia driver claimed interface c3a191e0
kernel BUG at cpia.c:245!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c482610c>]
EFLAGS: 00010292
eax: 0000001a   ebx: 00026000   ecx: 00000019   edx: 00000031
esi: 000e53c8   edi: c4972000   ebp: c4966000   esp: c33bff10
ds: 0018   es: 0018   ss: 0018
Process vic (pid: 527, stackpage=c33bf000)
Stack: c1d26600 00000000 c033d6e0 c3a3e6c0 000005c8 c482e2b0 00031ba5
c1d266d8
       00000000 c01ba3b7 c1d266d8 00000000 00000000 c0b7a140 c3d8ccc0
00000051
       00000000 000000ff c02392e1 c028dec0 c013b47a c3d8ccc0 c0b7a140
c0b7a140
Call Trace: [<c482e2b0>] [<c01ba3b7>] [<c02392e1>] [<c013b47a>] [<c0139df7>]
[<c013a0a3>] [<c010a544>]
Code: 0f 0b 8b 15 2c c5 28 c0 89 f9 81 e1 ff 0f 00 00 0b 4c 32 40          

Is there anyone who solve this problem ?

Nicolas.