Hi Ricardo,
> I tried with the cvs version of the module (modinfo says it's version 1.8)
> and have the same output after running pppoeconf.
> Here it is:
>
> without configuring nas0 with an ip:
>
> KERNEL: assertion (!atomic_read(&sk->sk_wmem_alloc)) failed at
> net/packet/af_packet.c (200)
> Attempt to release alive packet socket: df6cba80
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000004
>
> Call Trace:
> qdisc_restart
> net_tx_action
> do_softirq
> local_bh_enable
> datagram_poll
> packet_poll
> sock_poll
> do_select
> __pollwait
> Sys_select
> syscall_call
>
> Kernel panic: Fatal exception in interrupt
> In interrupt handler - not synsing
This call trace is unfortunately (and inevitably) useless: socket destruction
is being done in a softirq which is run at an essentially random time. So the
back trace doesn't help because the functions you see don't have anything
to do with the socket.
> Do you think it could be something else not directly related with the
> module? Perhaps with br2684ctl?
That's perfectly possible. One thing that may help is to look at the contents of
/proc/net/atm/vc
On my machine I see:
Address Itf VPI VCI Fam Flags Reply Send buffer Recv buffer
dae85e00 0 8 36 PVC 0047 0 0/ 65535 0/ 65535
The "Send buffer" field shows the value of sk_wmem_alloc. Is it non-zero?
Does it's value change? When does it first become non-zero?
All the best,
Duncan.
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se d�sinscrire : mailto:[EMAIL PROTECTED]
