Re: Kernel Oops with: ip link set can0 type can

[ajneu <ajneu1@gmail.com>]

Oliver Hartkopp <socketcan <at> hartkopp.net> writes:

> 
> 
> On 06/21/2016 10:55 AM, ajneu wrote:
> > ajneu <ajneu1 <at> gmail.com> writes:
> >
> >>
> >> Hi,
> >>
> >> issuing the command
> >>    sudo ip link set can0 type can
> >> I get Kernel Oops (NULL pointer dereference)
> >> Command line prints: "Killed".
> >>
> >> [...]
> >>
> >> dmesg shows
> >> [...]
> >
> >
> > Question:
> > How should one add and set a can device???
> 
> You do can not add a CAN device.
> 
> A 'real' CAN netdevice is detected and initialized automatically.

Well ok, I hear you.

But how is the netdevice detected and initialized automatically?
Is this from udev somewhere? Where? Can you point me to where that is?
What if I want to issue commands myself -- that possible?


Note also:
I can still do this:
   sudo ip link delete can0   ## also removes /sys/class/net/can0

Is this "legal"??
As mentioned in another post -- If I still have the can0 interface
connected, and remove it from the PC AFTER that 'ip link delete' command,
then the whole system hangs.


Thanks.
ajneu

> You only can add 'virtual' CAN devices:
> 
> ip link add dev vcan0 type vcan
> 
> But the OOPS should no occur due to your ip usage anyway 
> This has to be fixed ...
> 
> Regards,
> Oliver
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
>