Selon Frederick Ros <[EMAIL PROTECTED]>:
> Quoting "Thib G." <[EMAIL PROTECTED]>:
>
>
> > I've tried this snapshot, but ... mmmhh ... ooopps :(
> > ("hard oops" : only sysrq keys work after it)
> >
>
> Thanks for the test.
>
> > 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 ???) ?
>
> Well .. it seems more related to ip_nat (as it seems that there's no eagle
> functions in the dumped path), but this could also be a problem of eagle
> driver
> on top of ip NAT ..
>
> Anybody else get that one ?
>
>
> Frederick Ros aka Sleeper
>
I have sometime seen this sort of oops too and only when eagle-usb was running
Gilles
