Kernel oops

Patrick McHardy kaber at trash.net
Tue Jan 11 17:37:40 UTC 2011


Am 10.01.2011 09:27, schrieb Barry Myles:
> I'm using the linux-dect code and experimenting with dectmon and the libdect 
> examples. Mostly, I think they are working well. I have a com-on-air type II 
> card and it's in an aging P4 laptop. However, I'm having some kernel stability 
> problems. The machine runs stabily forever before the card is configured with 
> the netlink utilities. However, once the card is configured then a few minutes 
> later the kernel will oops.
> 
> I'm configuring the card something like:
> dect-cluster-add --name cluster0 --emc 0xABCD --fpn 0x12345 --mode PP
> dect-cell-add --name cell0 --cluster cluster0 --flags monitor
> dect-transceiver-bind --transceiver trx0 --cell cell0
> 
> Until the kernel oops then everything seems to work fine and dectmon, for 
> example will happily log what it sees.
> 
> I've attached two kernel logs which seem fairly typical of what is happening.
> 
> Can anyone help?
> 

> [  120.118216] BUG: unable to handle kernel NULL pointer dereference at 000003d0
> [  120.119021] IP: [<c148faea>] _raw_spin_lock+0x15/0x27

This looks odd, apparently the transceiver group vanished. Could you
send me your .config and the net/dect/transceiver.o files please?




More information about the linux-dect mailing list