ip -details link fails

ip -details link fails

[Ssagarr Patil]

Hi,

I am currently using the following version of can driver 
# cat /proc/net/can/version
rev 20120528 abi 9

But when I do the following it fails,

# ip -details link show can0
RTNETLINK answers: Invalid argument
Cannot send link get request: Invalid argument

Transmitting and reciving of can frames works.

I want to get the current bitrate of the CAN interface using the above command,
can anyone point me to what exactly is missing ? Or is there any alternative to get
the current bitrate of the CAN interface (ioctl/ sysfs entry..)

Thanks,
Sagar
 		 	   		  

Re: ip -details link fails

[Oliver Hartkopp]

On 05/27/2015 06:38 PM, Ssagarr Patil wrote:
> I am currently using the following version of can driver 
> # cat /proc/net/can/version
> rev 20120528 abi 9
> 

This is network layer stuff.
It does not tell you anything about CAN network interfaces.

> But when I do the following it fails,
> 
> # ip -details link show can0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument
> 
> Transmitting and reciving of can frames works.

Oh.

I assume you use a CAN driver with is not in Linux mainline, e.g. the PEAK
driver. The PEAK driver is configured differently (see its documentation).

Can you send the output of

	cat /proc/net/dev

	uname -a

	dmesg | grep -C 5 can0

Regards,
Oliver


> 
> I want to get the current bitrate of the CAN interface using the above command,
> can anyone point me to what exactly is missing ? Or is there any alternative to get
> the current bitrate of the CAN interface (ioctl/ sysfs entry..)
> 
> Thanks,
> Sagar
>  		 	   		  --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

RE: ip -details link fails

[Ssagarr Patil]

Hi Oliver,

Thanks for the response.

> On 05/27/2015 06:38 PM, Ssagarr Patil wrote:
>> I am currently using the following version of can driver
>> # cat /proc/net/can/version
>> rev 20120528 abi 9
>>
>
> This is network layer stuff.
> It does not tell you anything about CAN network interfaces.
>
OK
>> But when I do the following it fails,
>>
>> # ip -details link show can0
>> RTNETLINK answers: Invalid argument
>> Cannot send link get request: Invalid argument
>>
>> Transmitting and reciving of can frames works.
>
> Oh.
>
> I assume you use a CAN driver with is not in Linux mainline, e.g. the PEAK
> driver. The PEAK driver is configured differently (see its documentation).
>
> Can you send the output of
>
> cat /proc/net/dev
>
> uname -a
>
> dmesg | grep -C 5 can0
>
Following is the log:

# ip -details link show wlan0
RTNETLINK answers: Invalid argument
Cannot send link get request: Invalid argument
# cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 teql0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  eth0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  can0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  can1:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
#  uname -a
Linux evm 2.6.37 #1 Wed May 6 10:43:07 BST 2015 armv7l ARMv7 Processor rev 2 (v7l) ti8148evm GNU/Linux
# dmesg | grep -C 5 can0
[    8.320000] CAN device driver interface
[    8.380000] <30>systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
[    8.410000] <30>systemd[1]: Found device /dev/ttyO0.
[    8.420000] <30>systemd[1]: Started Recreate Volatile Files and Directories.
[    8.420000] <30>systemd[1]: Starting System Initialization.
[    8.440000] PM: Adding info for No Bus:can0
[    8.440000] c_can_platform d_can.0: c_can_platform device registered (regs=fa1cc000, irq=52)
[    8.440000] PM: Adding info for No Bus:can1
[    8.440000] c_can_platform d_can.1: c_can_platform device registered (regs=fa1d0000, irq=55)
[    8.440000] <30>systemd[1]: Reached target System Initialization.
[    8.440000] <30>systemd[1]: Starting OpenSSH Socket.
--
[   38.570000] can: raw protocol (rev 20120528)
[   38.570000] hci0: type 1 len 36
[   38.580000] hci0: type 1 len 245
[   38.590000] hci0: type 1 len 7
[   38.600000] hci0: type 1 len 5
[   38.620000] c_can_platform d_can.0: can0: setting BTR=0504 BRPE=0000
[   38.630000] c_can_platform d_can.1: can1: setting BTR=0504 BRPE=0000
[ 1953.040000] sit: Unknown symbol xfrm4_tunnel_register (err 0)
[ 1953.050000] sit: Unknown symbol xfrm4_tunnel_deregister (err 0)
[ 1980.800000] ipcomp: Unknown symbol ipcomp_input (err 0)

Note: The Linux version is 2.6.37 but the network stack & CAN drivers are from 3.14 kernel backports.

Thanks,
-Sagar

 		 	   		  

Re: ip -details link fails

[Oliver Hartkopp]

On 05/27/2015 07:11 PM, Ssagarr Patil wrote:

Your backports from 3.14 are looking to work properly ..

E.g. the output from
# cat /proc/net/dev
and
# dmesg | grep -C 5 can0

look sane.

BUT:

> # ip -details link show wlan0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument

The fact that your 'ip' tool doesn't work with wlan0 too your problem is
probably not CAN related.

Can you update the 'ip' tool to a recent version from iproute2:

http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/

What does your

	ip -V

tells your about the ip version?

Regards,
Oliver


> # cat /proc/net/dev
> Inter-|   Receive                                                |  Transmit
>  face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
>     lo:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>  teql0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>   eth0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>   can0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>   can1:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>  wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>   sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
> #  uname -a
> Linux evm 2.6.37 #1 Wed May 6 10:43:07 BST 2015 armv7l ARMv7 Processor rev 2 (v7l) ti8148evm GNU/Linux
> # dmesg | grep -C 5 can0
> [    8.320000] CAN device driver interface
> [    8.380000] <30>systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
> [    8.410000] <30>systemd[1]: Found device /dev/ttyO0.
> [    8.420000] <30>systemd[1]: Started Recreate Volatile Files and Directories.
> [    8.420000] <30>systemd[1]: Starting System Initialization.
> [    8.440000] PM: Adding info for No Bus:can0
> [    8.440000] c_can_platform d_can.0: c_can_platform device registered (regs=fa1cc000, irq=52)
> [    8.440000] PM: Adding info for No Bus:can1
> [    8.440000] c_can_platform d_can.1: c_can_platform device registered (regs=fa1d0000, irq=55)
> [    8.440000] <30>systemd[1]: Reached target System Initialization.
> [    8.440000] <30>systemd[1]: Starting OpenSSH Socket.
> --
> [   38.570000] can: raw protocol (rev 20120528)
> [   38.570000] hci0: type 1 len 36
> [   38.580000] hci0: type 1 len 245
> [   38.590000] hci0: type 1 len 7
> [   38.600000] hci0: type 1 len 5
> [   38.620000] c_can_platform d_can.0: can0: setting BTR=0504 BRPE=0000
> [   38.630000] c_can_platform d_can.1: can1: setting BTR=0504 BRPE=0000
> [ 1953.040000] sit: Unknown symbol xfrm4_tunnel_register (err 0)
> [ 1953.050000] sit: Unknown symbol xfrm4_tunnel_deregister (err 0)
> [ 1980.800000] ipcomp: Unknown symbol ipcomp_input (err 0)
> 
> Note: The Linux version is 2.6.37 but the network stack & CAN drivers are from 3.14 kernel backports.
> 
> Thanks,
> -Sagar
> 
>  		 	   		  
> 

Re: ip -details link fails

[Marc Kleine-Budde]

[-- Attachment #1: Type: text/plain, Size: 619 bytes --]

On 05/27/2015 07:24 PM, Oliver Hartkopp wrote:
>> # ip -details link show wlan0
>> RTNETLINK answers: Invalid argument
>> Cannot send link get request: Invalid argument
> 
> The fact that your 'ip' tool doesn't work with wlan0 too your problem is
> probably not CAN related.

BTW: the busybox version of ip doesn't talk can.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

Re: ip -details link fails

[Tom Evans]

On 28/05/15 02:38, Ssagarr Patil wrote:
> Hi,
>
> I am currently using the following version of can driver
> # cat /proc/net/can/version
> rev 20120528 abi 9
>
> But when I do the following it fails,
>
> # ip -details link show can0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument

There's also "canutils" and "can-utils" (they're different). We use one of 
these to configure our CAN ports. If you want to stick with Busybox then one 
of these may be your best option.

Best detailed here:

http://thread.gmane.org/gmane.linux.can/7164/focus=7221

From:

 > https://gitorious.org/linux-can/can-utils/
 > http://www.pengutronix.de/software/socket-can/download/canutils/v4.0/

Tom

RE: ip -details link fails

[Ssagarr Patil]

Hi Oliver,

>
> On 05/27/2015 07:24 PM, Oliver Hartkopp wrote:
>>> # ip -details link show wlan0
>>> RTNETLINK answers: Invalid argument
>>> Cannot send link get request: Invalid argument
>>
>> The fact that your 'ip' tool doesn't work with wlan0 too your problem is
>> probably not CAN related.
>
> BTW: the busybox version of ip doesn't talk can.
>
I am not using the ip from the busybox, 
I am using the release version from [1] (# ip -V
ip utility, iproute2-ss150413)


# ip -details link show can0
RTNETLINK answers: Invalid argument
Cannot send link get request: Invalid argument
# 

#  dmesg | grep -C 5 can0
[    6.510000] <30>systemd[1]: Found device /dev/ttyO0.
[    6.530000] <30>systemd[1]: Started Recreate Volatile Files and Directories.
[    6.530000] <30>systemd[1]: Starting System Initialization.
[    6.540000] <30>systemd[1]: Reached target System Initialization.
[    6.540000] <30>systemd[1]: Starting OpenSSH Socket.
[    6.560000] PM: Adding info for No Bus:can0
[    6.560000] c_can_platform d_can.0: c_can_platform device registered (regs=fa1cc000, irq=52)
[    6.560000] PM: Adding info for No Bus:can1
[    6.560000] c_can_platform d_can.1: c_can_platform device registered (regs=fa1d0000, irq=55)
[    6.720000] PM: Adding info for platform:wl18xx
[    6.840000] <30>systemd[1]: Listening on OpenSSH Socket.
--
[    8.750000] (stk) : debugfs entries created kim_probe Exit
[    8.780000] can: controller area network core (rev 20120528 abi 9)
[    8.780000] NET: Registered protocol family 29
[    8.810000] can: broadcast manager protocol (rev 20120528 t)
[    8.840000] can: raw protocol (rev 20120528)
[    8.900000] c_can_platform d_can.0: can0: setting BTR=0504 BRPE=0000
[    8.910000] c_can_platform d_can.1: can1: setting BTR=0504 BRPE=0000
[    9.600000] SysLink version : 2.21.03.11
[    9.600000] SysLink module created on Date:May  6 2015 Time:12:25:37
[    9.610000] PM: Adding info for No Bus:syslinkipc_Osal
[    9.610000] PM: Adding info for No Bus:syslinkipc_Ipc
# 

[1] https://www.kernel.org/pub/linux/utils/net/iproute2/

Or is that I am missing something in the kernel defconfig do I need to enable some via
doing menuconfig to get it working

Thanks,
Sagar
 		 	   		  

Re: ip -details link fails

[Oliver Hartkopp]

On 28.05.2015 11:48, Ssagarr Patil wrote:
> Hi Oliver,
>
>>
>> On 05/27/2015 07:24 PM, Oliver Hartkopp wrote:
>>>> # ip -details link show wlan0
>>>> RTNETLINK answers: Invalid argument
>>>> Cannot send link get request: Invalid argument
>>>
>>> The fact that your 'ip' tool doesn't work with wlan0 too your problem is
>>> probably not CAN related.
>>
>> BTW: the busybox version of ip doesn't talk can.
>>
> I am not using the ip from the busybox,
> I am using the release version from [1] (# ip -V
> ip utility, iproute2-ss150413)
>

Looks good.

>
> # ip -details link show can0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument
> #
>


>
> [1] https://www.kernel.org/pub/linux/utils/net/iproute2/
>
> Or is that I am missing something in the kernel defconfig do I need to enable some via
> doing menuconfig to get it working

Hm.

Can you post the output of

	strace ip -details link show can0

Maybe there"s really something missing in the kernel config to run the netlink 
configuration.

Regards,
Oliver

RE: ip -details link fails

[Ssagarr Patil]

Hi Oliver,
>
> On 28.05.2015 11:48, Ssagarr Patil wrote:
>> Hi Oliver,
>>
>>>
>>> On 05/27/2015 07:24 PM, Oliver Hartkopp wrote:
>>>>> # ip -details link show wlan0
>>>>> RTNETLINK answers: Invalid argument
>>>>> Cannot send link get request: Invalid argument
>>>>
>>>> The fact that your 'ip' tool doesn't work with wlan0 too your problem is
>>>> probably not CAN related.
>>>
>>> BTW: the busybox version of ip doesn't talk can.
>>>
>> I am not using the ip from the busybox,
>> I am using the release version from [1] (# ip -V
>> ip utility, iproute2-ss150413)
>>
>
> Looks good.
>
>>
>> # ip -details link show can0
>> RTNETLINK answers: Invalid argument
>> Cannot send link get request: Invalid argument
>> #
>>
>
>
>>
>> [1] https://www.kernel.org/pub/linux/utils/net/iproute2/
>>
>> Or is that I am missing something in the kernel defconfig do I need to enable some via
>> doing menuconfig to get it working
>
> Hm.
>
> Can you post the output of
>
> strace ip -details link show can0
>
> Maybe there"s really something missing in the kernel config to run the netlink
> configuration.
>

execve("/sbin/ip", ["ip", "-details", "link", "show", "can0"], [/* 20 vars */]) = 0
brk(0)                                  = 0x57000
uname({sysname="Linux", nodename="evm", ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x400ec000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/tls/v7l/neon/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/v7l/neon/vfp", 0xbec4b3f0) = -1 ENOENT (No such file or directory)
open("/lib/tls/v7l/neon/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/v7l/neon", 0xbec4b3f0) = -1 ENOENT (No such file or directory)
open("/lib/tls/v7l/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/v7l/vfp", 0xbec4b3f0)  = -1 ENOENT (No such file or directory)
open("/lib/tls/v7l/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/v7l", 0xbec4b3f0)      = -1 ENOENT (No such file or directory)
open("/lib/tls/neon/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/neon/vfp", 0xbec4b3f0) = -1 ENOENT (No such file or directory)
open("/lib/tls/neon/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/neon", 0xbec4b3f0)     = -1 ENOENT (No such file or directory)
open("/lib/tls/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/vfp", 0xbec4b3f0)      = -1 ENOENT (No such file or directory)
open("/lib/tls/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/tls", 0xbec4b3f0)          = -1 ENOENT (No such file or directory)
open("/lib/v7l/neon/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/v7l/neon/vfp", 0xbec4b3f0) = -1 ENOENT (No such file or directory)
open("/lib/v7l/neon/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/v7l/neon", 0xbec4b3f0)     = -1 ENOENT (No such file or directory)
open("/lib/v7l/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/v7l/vfp", 0xbec4b3f0)      = -1 ENOENT (No such file or directory)
open("/lib/v7l/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/v7l", 0xbec4b3f0)          = -1 ENOENT (No such file or directory)
open("/lib/neon/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/neon/vfp", 0xbec4b3f0)     = -1 ENOENT (No such file or directory)
open("/lib/neon/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/neon", 0xbec4b3f0)         = -1 ENOENT (No such file or directory)
open("/lib/vfp/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/lib/vfp", 0xbec4b3f0)          = -1 ENOENT (No such file or directory)
open("/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0l\t\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=15193, ...}) = 0
mmap2(NULL, 41144, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4015e000
mprotect(0x40160000, 28672, PROT_NONE)  = 0
mmap2(0x40167000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x40167000
close(3)                                = 0
open("/lib/libgcc_s.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\340\315\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1532904, ...}) = 0
mmap2(NULL, 152480, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x400ad000
mprotect(0x400cb000, 28672, PROT_NONE)  = 0
mmap2(0x400d2000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d000) = 0x400d2000
close(3)                                = 0
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0H\205\1\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1545368, ...}) = 0
mmap2(NULL, 1242504, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x40169000
mprotect(0x4028c000, 28672, PROT_NONE)  = 0
mmap2(0x40293000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x122000) = 0x40293000
mmap2(0x40296000, 9608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40296000
close(3)                                = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x400d3000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4010e000
set_tls(0x4010e4c0, 0x4010eba8, 0x400ac050, 0x4010e4c0, 0x400ac050) = 0
mprotect(0x40293000, 8192, PROT_READ)   = 0
mprotect(0x40167000, 4096, PROT_READ)   = 0
mprotect(0x400ab000, 4096, PROT_READ)   = 0
socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 3
setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
setsockopt(3, SOL_SOCKET, SO_RCVBUF, [1048576], 4) = 0
bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=236, groups=00000000}, [12]) = 0
gettimeofday({946684864, 166689}, NULL) = 0
send(3, " \0\0\0\20\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 32, 0) = 32
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"4\0\0\0\2\0\0\0\0\0\0\0\354\0\0\0\355\377\377\377 \0\0\0\20\0\5\0\2
access("/proc/net", R_OK)               = 0
access("/proc/net/unix", R_OK)          = 0
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
ioctl(4, SIOCGIFINDEX, {ifr_name="can0", ifr_index=4}) = 0
close(4)                                = 0
send(3, "(\0\0\0\22\0\1\3\301Cm8\0\0\0\0\21\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 40, 0) = 40
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\254\1\0\0\20\0\2\0\301Cm8\354\0\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0
brk(0)                                  = 0x57000
brk(0x78000)                            = 0x78000
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\301Cm8\354\0\0\0\0\0\0\0", 16384}], msg_controll0
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 0), ...}) = 0
ioctl(1, TCGETS, {B115200 opost isig icanon echo ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40299000
write(1, "4: can0: <NOARP,UP,LOWER_UP,ECHO"..., 934: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 10
) = 93
write(1, "    link/can \n", 14    link/can 
)         = 14
open("/usr/lib/ip/link_can.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(1, "    can <TRIPLE-SAMPLING> state "..., 84    can <TRIPLE-SAMPLING> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0 
) = 84
write(1, "\t  bitrate 500000 sample-point 0"..., 38       bitrate 500000 sample-point 0.875 
) = 38
write(1, "\t  tq 250 prop-seg 3 phase-seg1 "..., 53       tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
) = 53
write(1, "\t  c_can: tseg1 2..16 tseg2 1..8"..., 64       c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
) = 64
write(1, "\t  clock 20000000\n", 18       clock 20000000
)    = 18
exit_group(0)                           = ?
+++ exited with 0 +++
# 


But I got it working with iproute2 release 3.15.0 (ip utility, iproute2-ss140610) from [1]
Not sure Why it fails with 4.0.0.

[1] https://www.kernel.org/pub/linux/utils/net/iproute2/

Thanks,
Sagar

 		 	   		  

Re: ip -details link fails

[Oliver Hartkopp]

On 28.05.2015 18:28, Ssagarr Patil wrote:
>
> write(1, "    can <TRIPLE-SAMPLING> state "..., 84    can <TRIPLE-SAMPLING> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
> ) = 84
> write(1, "\t  bitrate 500000 sample-point 0"..., 38       bitrate 500000 sample-point 0.875
> ) = 38
> write(1, "\t  tq 250 prop-seg 3 phase-seg1 "..., 53       tq 250 prop-seg 3 phase-seg1 3 phase-seg2 1 sjw 1
> ) = 53
> write(1, "\t  c_can: tseg1 2..16 tseg2 1..8"..., 64       c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
> ) = 64
> write(1, "\t  clock 20000000\n", 18       clock 20000000
> )    = 18
> exit_group(0)                           = ?
> +++ exited with 0 +++
> #

Ah, it works :-)

> But I got it working with iproute2 release 3.15.0 (ip utility, iproute2-ss140610) from [1]
> Not sure Why it fails with 4.0.0.

Ok.

Don't know either. But good to see you have a working environment now.

Regards,
Oliver

>
> [1] https://www.kernel.org/pub/linux/utils/net/iproute2/
>