Benoit Audouard wrote:
Hi,
new version including latest BNM
http://baud123.free.fr/eagle-usb/eagle-usb-2.0.0/eagle-usb-2.0.0_20041026_snapshot.tar.bz2
- CMV files are not (yet) copied automatically.
- still uses (by default) eagle-usb.conf...
- for testing (regression mostly on "older" modems...)
=> works for me, fast800E3, no reproducible Oops on Mdk10.1
kernel-2.6.8.1-12mdk
hello,
I've tried this snapshot, but ... mmmhh ... ooopps :(
("hard oops" : only sysrq keys work after it)
The oops seem to appear at connection startup, or during the connection
(unless my scripts rmmod the module during boot sequence ...
but I don't think so)
My config :
debian testing
linux vanilla 2.6.8.1
eagle-usb-2.0.0_20041026
gcc-3.4
oops (manually typed -- I hope there are not too many typing mistakes ;)
output :
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Process swapper (pid: 0, threadinfo=c03ae000 task=c0333a40)
Stack: [...]
Call Trace:
[<c02d19a9>] ip_nat_fn+0xc9/0x4a0
~ ing_hook+0x40/0x70 [sch_ingress]
~ nf_iterate
~ ip_rcv_finish
~ ip_rcv_finish
~ nf_hook_slow
~ ip_rcv_finish
~ ip_rcv
~ ip_rcv_finish
~ netif_receive
~ process_backlog
~ net_rx_action
~ __do_softirq
~ do_IRQ+0x10d/0x130
[<c0104138>] common_interrupt+0x18/0x20
Code: 8b 43 0c 39 f0 74 39 3d 00 03 00 00 [...]
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Is it related too eagle-usb, or is it a bug from kernel (ip_nat ???) ?
Thib.
ps : what data from the oops output is needed ? are the names in
the call trace enough, are do you need other info ?
