Re: [Xenomai] analogy attach failed NI-6220

[Danilo De Lorenzo <danilo.delorenzo@mail.polimi.it>]

Disabling comedi drivers from the kernel configuration solved the problem.

Thanks a lot!

Danilo

On 06/21/2012 12:21 AM, Alexis Berlemont wrote:
> Hi,
>
> Sorry for the late answer.
>
> On Fri, Jun 15, 2012 at 8:06 PM, Danilo De Lorenzo
> <danilo.delorenzo@mail.polimi.it>  wrote:
>> - The driver is shown under /proc/analogy/drivers
>>
>> - Launching analogy_config without options gave me the same error
>>
>> - this is the part of  dmesg output related to mite and comedi (it seems the
>> board is detected by mite driver):
>>
>> [   29.141006]<30>udevd[365]: starting version 173
>> [   29.797061] lp: driver loaded but no devices found
>> [   29.832660] ni_tio: module is from the staging directory, the quality is
>> unknown, you have been warned.
>> [   29.849476] comedi: module is from the staging directory, the quality is
>> unknown, you have been warned.
>> [   29.853344] comedi: version 0.7.76 - http://www.comedi.org
>> [   29.882067] type=1400 audit(1339780810.462:2): apparmor="STATUS"
>> operation="profile_load" name="/sbin/dhclient" pid=604
>> comm="apparmor_parser"
>> [   29.882158] type=1400 audit(1339780810.462:3): apparmor="STATUS"
>> operation="profile_load"
>> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=604
>> comm="apparmor_parser"
>> [   29.882219] type=1400 audit(1339780810.462:4): apparmor="STATUS"
>> operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script"
>> pid=604 comm="apparmor_parser"
>> [   29.906386] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x8410,
>> revision 0
>> [   29.936592] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
>> [   29.936707] SP5100 TCO timer: mmio address 0xfec000f0 already in use
>> [   29.973252] tpm_tis 00:01: 1.2 TPM (device-id 0xB, rev-id 16)
>> [   30.019424] type=1400 audit(1339780810.592:5): apparmor="STATUS"
>> operation="profile_replace" name="/sbin/dhclient" pid=668
>> comm="apparmor_parser"
>> [   30.019521] type=1400 audit(1339780810.592:6): apparmor="STATUS"
>> operation="profile_replace"
>> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=668
>> comm="apparmor_parser"
>> [   30.019585] type=1400 audit(1339780810.592:7): apparmor="STATUS"
>> operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script"
>> pid=668 comm="apparmor_parser"
>> [   30.089668] 8255: module is from the staging directory, the quality is
>> unknown, you have been warned.
>> [   30.134451] mite: module is from the staging directory, the quality is
>> unknown, you have been warned.
>> [   30.137068] Available NI device IDs:
>> [   30.137071]  0x70b0
>> [   30.137073]
>> [   30.157559] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
>> [   30.171110] comedi_fc: module is from the staging directory, the quality
>> is unknown, you have been warned.
>> [   30.396292] ni_tiocmd: module is from the staging directory, the quality
>> is unknown, you have been warned.
>> [   30.398776] ni_pcimio: module is from the staging directory, the quality
>> is unknown, you have been warned.
>> [   30.402314] comedi0: ni_pcimio: pci-6220
>> [   30.402370] ni_pcimio 0000:0c:05.0: PCI INT A ->  GSI 20 (level, low) ->
>> IRQ 20
>> [   30.402399] MITE:0xd2001000 mapped to ffffc9000035e000
>> [   30.402405] DAQ:0xd2000000 mapped to ffffc90000368000
>> [   30.402412] mite: version = 1, type = 4, mite mode = 1,interface mode = 3
>> [   30.402414] mite: num channels = 8, write post fifo depth = 1,wins = 0,
>> iowins = 2
>> [   30.402424] mite: fifo size is 64.
>> [   30.426067]  ( irq = 20 )
>> [   30.570182] usb 1-6: usbfs: USBDEVFS_CONTROL failed cmd mtp-probe rqt 128
>> rq 6 len 255 ret -110
>> [   30.733353] Analogy: MITE: Available NI device IDs:
>> [   31.103558] nvidia: module license 'NVIDIA' taints kernel.
>> [   31.103565] Disabling lock debugging due to kernel tai
>>
>>
>> Also, looking at the kernel.log when trying several options I found this:
>>
>> Jun  6 15:04:08 .............. kernel: [12804.406688] Analogy:
>> a4l_assign_driver: call(drv->attach) failed (ret=-22)
>> Jun  6 15:11:07 .............. kernel: [13222.826688] Analogy:
>> a4l_assign_driver: call(alloc) failed
>> Jun  6 15:11:16 .............. kernel: [13232.266499] Analogy:
>> a4l_assign_driver: call(alloc) failed
>> Jun  6 15:11:54 .............. kernel: [13269.486717] BUG: unable to handle
>> kernel NULL pointer dereference at 000000000000000c
>> Jun  6 15:11:54 .............. kernel: [13269.486725] IP:
>> [<ffffffff810fe0fb>] get_free_range+0x5b/0x170
>> Jun  6 15:11:54 .............. kernel: [13269.486735] PGD 47bfe067 PUD
>> 47bf6067 PMD 0
>> Jun  6 15:11:54 .............. kernel: [13269.486741] Oops: 0000 [#1]
>> PREEMPT SMP
>> Jun  6 15:11:54 .............. kernel: [13269.486746] last sysfs file:
>> /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
>> Jun  6 15:11:54 .............. kernel: [13269.486751] CPU 1
>> Jun  6 15:11:54 .............. kernel: [13269.486753] Modules linked in: sco
>> rfcomm bnep l2cap bluetooth parport_pc ppdev dm_crypt nvidia(P)
>> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm
>> snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq analogy_ni_pcimio
>> analogy_ni_mio analogy_ni_tio analogy_8255 analogy_ni_mite xeno_analogy
>> ni_pcimio(C) ni_tiocmd(C) comedi_fc(C) mite(C) snd_timer snd_seq_device
>> 8255(C) snd tpm_infineon sp5100_tco i2c_piix4 soundcore snd_page_alloc
>> psmouse comedi(C) ni_tio(C) tpm_tis tpm serio_raw tpm_bios lp parport usbhid
>> hid r8169 floppy ahci pata_atiixp libahci
>> Jun  6 15:11:54 .............. kernel: [13269.486813]
>> Jun  6 15:11:54 .............. kernel: [13269.486816] Pid: 2118, comm:
>> analogy_config Tainted: P         C  2.6.38.8-xenomai #1 FUJITSU SIEMENS
>> ESPRIMO P           /D2451-A3
>> Jun  6 15:11:54 .............. kernel: [13269.486824] RIP:
>> 0010:[<ffffffff810fe0fb>]  [<ffffffff810fe0fb>] get_free_range+0x5b/0x170
>> Jun  6 15:11:54 .............. kernel: [13269.486830] RSP:
>> 0018:ffff880035147bd0  EFLAGS: 00010206
>> Jun  6 15:11:54 .............. kernel: [13269.486833] RAX: 000000000000000c
>> RBX: ffffc90001509200 RCX: 000000000000000c
>> Jun  6 15:11:54 .............. kernel: [13269.486836] RDX: 0000000000000000
>> RSI: 0000000000005000 RDI: ffffffff821ac3c0
>> Jun  6 15:11:54 .............. kernel: [13269.486839] RBP: ffff880035147bf8
>> R08: ffffc90001508000 R09: 000000000000000c
>> Jun  6 15:11:54 .............. kernel: [13269.486842] R10: 0000000000000200
>> R11: 0000000000000200 R12: 0000000000000400
>> Jun  6 15:11:54 .............. kernel: [13269.486845] R13: ffffc90001509000
>> R14: ffffc90001509000 R15: ffffffff821ac408
>> Jun  6 15:11:54 .............. kernel: [13269.486849] FS:
>>   00007f2246a9f720(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
>> Jun  6 15:11:54 .............. kernel: [13269.486852] CS:  0010 DS: 0000 ES:
>> 0000 CR0: 0000000080050033
>> Jun  6 15:11:54 .............. kernel: [13269.486855] CR2: 000000000000000c
>> CR3: 0000000035216000 CR4: 00000000000006e0
>> Jun  6 15:11:54 .............. kernel: [13269.486858] DR0: 0000000000000000
>> DR1: 0000000000000000 DR2: 0000000000000000
>> Jun  6 15:11:54 .............. kernel: [13269.486861] DR3: 0000000000000000
>> DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> Jun  6 15:11:54 .............. kernel: [13269.486864] Process analogy_config
>> (pid: 2118, threadinfo ffff880035144000, task ffff8800353c0000)
>> Jun  6 15:11:54 .............. kernel: [13269.486867] Stack:
>> Jun  6 15:11:54 .............. kernel: [13269.486869]  00001d08949cb57b
>> 0000000000000001 ffff880035147cd0 ffffffff821ac3c0
>> Jun  6 15:11:54 .............. kernel: [13269.486876]  0000000000005000
>> ffff880035147c68 ffffffff810ff9e9 ffff880035147c28
>> Jun  6 15:11:54 .............. kernel: [13269.486882]  0000000000000001
>> ffff880035147c88 ffffffff810ff793 000000000000eb20
>> Jun  6 15:11:54 .............. kernel: [13269.486888] Call Trace:
>> Jun  6 15:11:54 .............. kernel: [13269.486894]  [<ffffffff810ff9e9>]
>> xnheap_alloc+0x4b9/0x4e0
>> Jun  6 15:11:54 .............. kernel: [13269.486899]  [<ffffffff810ff793>]
>> ? xnheap_alloc+0x263/0x4e0
>> Jun  6 15:11:54 .............. kernel: [13269.486910]  [<ffffffffa013e238>]
>> a4l_assign_driver+0x58/0x220 [xeno_analogy]
>> Jun  6 15:11:54 .............. kernel: [13269.486916]  [<ffffffffa013e534>]
>> a4l_device_attach+0x74/0x90 [xeno_analogy]
>> Jun  6 15:11:54 .............. kernel: [13269.486922]  [<ffffffffa013e5eb>]
>> a4l_ioctl_devcfg+0x6b/0x150 [xeno_analogy]
>> Jun  6 15:11:54 .............. kernel: [13269.486928]  [<ffffffffa01407de>]
>> a4l_ioctl+0x1e/0x20 [xeno_analogy]
>> Jun  6 15:11:54 .............. kernel: [13269.486935]  [<ffffffff811776eb>]
>> __rt_dev_ioctl+0x12b/0x160
>> Jun  6 15:11:54 .............. kernel: [13269.486940]  [<ffffffff811a3eee>]
>> ? handle_mm_fault+0x13e/0x240
>> Jun  6 15:11:54 .............. kernel: [13269.486945]  [<ffffffff8117d878>]
>> sys_rtdm_ioctl+0x28/0x30
>> Jun  6 15:11:54 .............. kernel: [13269.486949]  [<ffffffff81118a31>]
>> losyscall_event+0xd1/0x260
>> Jun  6 15:11:54 .............. kernel: [13269.486954]  [<ffffffff810cd2ac>]
>> __ipipe_dispatch_event+0x11c/0x1e0
>> Jun  6 15:11:54 .............. kernel: [13269.486960]  [<ffffffff8101f90c>]
>> __ipipe_syscall_root+0x5c/0x130
>> Jun  6 15:11:54 .............. kernel: [13269.486970]  [<ffffffff8161d521>]
>> __ipipe_syscall_root_thunk+0x35/0x6a
>> Jun  6 15:11:54 .............. kernel: [13269.486977]  [<ffffffff81002f04>]
>> ? system_call_after_swapgs+0x54/0x79
>> Jun  6 15:11:54 .............. kernel: [13269.486980] Code: 74 4b 4c 8b 5f
>> 18 4d 89 f1 0f 1f 80 00 00 00 00 4d 89 da 4c 89 c8 eb 13 0f 1f 84 00 00 00
>> 00 00 49 39 f2 73 16 4d 89 e2 48 89 c8<48>  8b 08 4a 8d 1c 18 4f 8d 24 1a 48
>> 39 d9 74 e5 4c 39 d6 76 30
>> Jun  6 15:11:54 .............. kernel: [13269.487035] RIP
>>   [<ffffffff810fe0fb>] get_free_range+0x5b/0x170
>> Jun  6 15:11:54 .............. kernel: [13269.487040]  RSP
>> <ffff880035147bd0>
>> Jun  6 15:11:54 .............. kernel: [13269.487042] CR2: 000000000000000c
>>
>>
>> Any clues on the causes of the problem?
>>
> It seems that, in your kernel configuration, you have enabled both
> comedi and analogy. I saw comedi messages in your kernel logs.
> Could you try to disable comedi? there are two mite drivers loaded.
>
> Are you sure the analogy mite driver detected your board? I only saw:
> [   30.733353] Analogy: MITE: Available NI device IDs:
> No device ID is listed.
>
> Could you enable XENO_DRIVERS_ANALOGY_DEBUG and set
> XENO_DRIVERS_ANALOGY_DEBUG_LEVEL to 5 in your kernel configuration?
> You are supposed to see messages like
> "mio_common: registering AI subdevice...\n",
> "mio_common: registering AO subdevice...\n"
> With more verbosity, we might be able to locate the code which
> triggers the kernel oops.
>
> Alexis.
>
>> Thanks a lot.
>>
>>
>> Danilo De Lorenzo, PhD
>> NearLab - Bioengineering Department
>> Politecnico di Milano, via Colombo 40, 20133 Milan, Italy
>> www.nearlab.polimi.it
>>
>> email: danilo.delorenzo@mail.polimi.it
>> phone: +39 02-2399-9013
>> fax: +39 02-2399-9003
>>
>>
>> On 06/07/2012 09:07 AM, Alexis Berlemont wrote:
>>> Hi,
>>>
>>> On Wed, Jun 6, 2012 at 8:25 PM, Danilo De Lorenzo
>>> <danilo.delorenzo@mail.polimi.it>    wrote:
>>>> Anyone else has any suggestions? At least a hint on how to find where is
>>>> the problem?
>>>>
>>> The error code -2 means -ENOENT; so
>>> - either the driver is not available inside the kernel (according to
>>> your former mail, it is not the case; you can ensure this point by
>>> checking the content of /proc/analogy/drivers)
>>> -or the card is not detected, could you look in the kernel logs for a
>>> message stating that the card was detected by the mite driver (maybe
>>> verbose log should be activated)?
>>> - could you launch analogy_config without the optional arguments? just
>>> type:
>>> /usr/xenomai/sbin/analogy_config analogy0 analogy_ni_pcimio
>>>
>>>> Thanks
>>>> Il giorno 06/giu/2012 11:13, "Danilo De Lorenzo"<
>>>> danilo.delorenzo@mail.polimi.it>    ha scritto:
>>>>
>>> Alexis.