* [Xenomai-help] Driver testing procedure ?! @ 2009-05-25 11:46 Cristian Axenie 2009-05-25 21:28 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-25 11:46 UTC (permalink / raw) To: xenomai [-- Attachment #1: Type: text/plain, Size: 5389 bytes --] Hello! I've took a snapshot of the git tree from Alexis's when he added the PCIMIO drivers. I've built my kernel and created an own usbflash filesystem. Now what should I do to begin testing the drivers ? The drivers are now kernel built-in and there is no comedi_config anymore. The outputs from cmd_read and cmd_write are the following, and it seems that is a problem with the file descriptors : /usr/xenomai/bin # ./cmd_read cmd_read: comedi_fill_desc failed (ret=-22) *** glibc detected *** ./cmd_read: free(): invalid next size (fast): 0x10046008 *** ======= Backtrace: ========= /lib/libc.so.6[0xfd7b1ac] /lib/libc.so.6[0xfd7cb8c] /lib/libc.so.6(cfree+0xfc)[0xfd7d280] ./cmd_read[0x100022a0] /lib/libc.so.6[0xfd22260] /lib/libc.so.6[0xfd223ec] ======= Memory map: ======== 00100000-00103000 r-xp 00100000 00:00 0 [vdso] 0fd04000-0fe40000 r-xp 00000000 08:01 16376 /lib/libc-2.6.so 0fe40000-0fe7f000 ---p 0013c000 08:01 16376 /lib/libc-2.6.so 0fe7f000-0fe81000 r--p 0013b000 08:01 16376 /lib/libc-2.6.so 0fe81000-0fe84000 rwxp 0013d000 08:01 16376 /lib/libc-2.6.so 0fe84000-0fe87000 rwxp 0fe84000 00:00 0 0fe97000-0feab000 r-xp 00000000 08:01 16499 /lib/libpthread-2.6.so 0feab000-0feeb000 ---p 00014000 08:01 16499 /lib/libpthread-2.6.so 0feeb000-0feec000 r--p 00014000 08:01 16499 /lib/libpthread-2.6.so 0feec000-0feed000 rwxp 00015000 08:01 16499 /lib/libpthread-2.6.so 0feed000-0feef000 rwxp 0feed000 00:00 0 0feff000-0ff02000 r-xp 00000000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff02000-0ff41000 ---p 00003000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff41000-0ff42000 rwxp 00002000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff52000-0ff5b000 r-xp 00000000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ff5b000-0ff9b000 ---p 00009000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ff9b000-0ff9c000 rwxp 00009000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ffac000-0ffb0000 r-xp 00000000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 0ffb0000-0ffef000 ---p 00004000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 0ffef000-0fff0000 rwxp 00003000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 10000000-10004000 r-xp 00000000 08:01 47292 /usr/xenomai/bin/cmd_read 10043000-10044000 rwxp 00003000 08:01 47292 /usr/xenomai/bin/cmd_read 10044000-10067000 rwxp 10044000 00:00 0 [heap] 48000000-4801d000 r-xp 00000000 08:01 16303 /lib/ld-2.6.so 4801d000-48020000 rw-p 4801d000 00:00 0 48020000-48023000 rw-s 00000000 08:01 31436 /dev/rtheap 48023000-48026000 rw-s 00000000 08:01 31436 /dev/rtheap 4805c000-4805d000 r--p 0001c000 08:01 16303 /lib/ld-2.6.so 4805d000-4805e000 rwxp 0001d000 08:01 16303 /lib/ld-2.6.so bfdda000-bfdef000 rw-p bffeb000 00:00 0 [stack] Aborted /usr/xenomai/bin # ./cmd_write cmd_write: comedi_get_desc failed (ret=-22) *** glibc detected *** ./cmd_write: free(): invalid next size (fast): 0x10046008 *** ======= Backtrace: ========= /lib/libc.so.6[0xfd7b1ac] /lib/libc.so.6[0xfd7cb8c] /lib/libc.so.6(cfree+0xfc)[0xfd7d280] ./cmd_write[0x100021a0] /lib/libc.so.6[0xfd22260] /lib/libc.so.6[0xfd223ec] ======= Memory map: ======== 00100000-00103000 r-xp 00100000 00:00 0 [vdso] 0fd04000-0fe40000 r-xp 00000000 08:01 16376 /lib/libc-2.6.so 0fe40000-0fe7f000 ---p 0013c000 08:01 16376 /lib/libc-2.6.so 0fe7f000-0fe81000 r--p 0013b000 08:01 16376 /lib/libc-2.6.so 0fe81000-0fe84000 rwxp 0013d000 08:01 16376 /lib/libc-2.6.so 0fe84000-0fe87000 rwxp 0fe84000 00:00 0 0fe97000-0feab000 r-xp 00000000 08:01 16499 /lib/libpthread-2.6.so 0feab000-0feeb000 ---p 00014000 08:01 16499 /lib/libpthread-2.6.so 0feeb000-0feec000 r--p 00014000 08:01 16499 /lib/libpthread-2.6.so 0feec000-0feed000 rwxp 00015000 08:01 16499 /lib/libpthread-2.6.so 0feed000-0feef000 rwxp 0feed000 00:00 0 0feff000-0ff02000 r-xp 00000000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff02000-0ff41000 ---p 00003000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff41000-0ff42000 rwxp 00002000 08:01 47615 /usr/xenomai/lib/librtdm.so.1.0.0 0ff52000-0ff5b000 r-xp 00000000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ff5b000-0ff9b000 ---p 00009000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ff9b000-0ff9c000 rwxp 00009000 08:01 47591 /usr/xenomai/lib/libnative.so.3.0.0 0ffac000-0ffb0000 r-xp 00000000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 0ffb0000-0ffef000 ---p 00004000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 0ffef000-0fff0000 rwxp 00003000 08:01 47586 /usr/xenomai/lib/libcomedi.so.0.0.0 10000000-10003000 r-xp 00000000 08:01 47293 /usr/xenomai/bin/cmd_write 10043000-10044000 rwxp 00003000 08:01 47293 /usr/xenomai/bin/cmd_write 10044000-10067000 rwxp 10044000 00:00 0 [heap] 48000000-4801d000 r-xp 00000000 08:01 16303 /lib/ld-2.6.so 4801d000-48020000 rw-p 4801d000 00:00 0 48020000-48023000 rw-s 00000000 08:01 31436 /dev/rtheap 48023000-48026000 rw-s 00000000 08:01 31436 /dev/rtheap 4805c000-4805d000 r--p 0001c000 08:01 16303 /lib/ld-2.6.so 4805d000-4805e000 rwxp 0001d000 08:01 16303 /lib/ld-2.6.so bfdbe000-bfdd3000 rw-p bffeb000 00:00 0 [stack] Aborted Some hints ? How should I test the validity of my solution? In fact how can I test that the NI drivers are working properly now that are Xenomai built-in? Best ! [-- Attachment #2: Type: text/html, Size: 7062 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-25 11:46 [Xenomai-help] Driver testing procedure ?! Cristian Axenie @ 2009-05-25 21:28 ` Alexis Berlemont 2009-05-25 21:35 ` Cristian Axenie 0 siblings, 1 reply; 21+ messages in thread From: Alexis Berlemont @ 2009-05-25 21:28 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, Cristian Axenie <cristian.axenie@domain.hid> writes: > Hello! > I've took a snapshot of the git tree from Alexis's when he added the PCIMIO drivers. I've built my kernel and created an own usbflash filesystem. Now what should I do to > begin testing the drivers ? > The drivers are now kernel built-in and there is no comedi_config anymore. That is not correct; even if the comedi driver is statically linked into the kernel does not mean the comedi layer automatically linked it to a specific device. Have a look at the proc file /proc/comedi/devices, you will see the devices are initialized unattached in any case. Nonetheless, you should have had a message, somewhere, telling you such thing. I will fix that as soon as possible. Regards. Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-25 21:28 ` Alexis Berlemont @ 2009-05-25 21:35 ` Cristian Axenie 2009-05-25 22:10 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-25 21:35 UTC (permalink / raw) To: Alexis Berlemont, xenomai [-- Attachment #1: Type: text/plain, Size: 2219 bytes --] Hi, I finally figured out this aspect but I still have one problem, residing in the fact that I have no comedi devices in my dev list and so I cannot ./comedi_config /dev/comedi0 nipcimio ! As I see it there are no comedi devices /usr/xenomai/sbin # cat /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 ttyS 5 /dev/tty 5 /dev/console 5 /dev/ptmx 10 misc 13 input 21 sg 128 ptm 136 pts 150 rtpipe 180 usb 189 usb_device 254 usb_endpoint Block devices: 1 ramdisk 7 loop 8 sd 31 mtdblock 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd and the list /usr/xenomai/sbin # cat /proc/comedi/devices -- Comedi devices -- | idx | status | driver | 00 | Unused | No driver | 01 | Unused | No driver | 02 | Unused | No driver | 03 | Unused | No driver | 04 | Unused | No driver | 05 | Unused | No driver | 06 | Unused | No driver | 07 | Unused | No driver | 08 | Unused | No driver | 09 | Unused | No driver /usr/xenomai/sbin # cat /proc/comedi/drivers comedi_config rtcanconfig rtps /usr/xenomai/sbin # cat /proc/comedi/drivers -- Comedi drivers -- | idx | driver name | 00 | pcimio | 01 | comedi_8255 | 02 | comedi_loop | 03 | comedi_fake Shouldn't the specific comedi devices be generated when installing Xenomai ? Best ! On Tue, May 26, 2009 at 12:28 AM, Alexis Berlemont <berlemont.hauw@domain.hid>wrote: > Hi, > > Cristian Axenie <cristian.axenie@domain.hid> writes: > > > Hello! > > I've took a snapshot of the git tree from Alexis's when he added the > PCIMIO drivers. I've built my kernel and created an own usbflash filesystem. > Now what should I do to > > begin testing the drivers ? > > The drivers are now kernel built-in and there is no comedi_config > anymore. > That is not correct; even if the comedi driver is statically linked into > the kernel does not mean the comedi layer automatically linked it to a > specific device. Have a look at the proc file /proc/comedi/devices, you > will see the devices are initialized unattached in any case. > > Nonetheless, you should have had a message, somewhere, telling you such > thing. I will fix that as soon as possible. > > Regards. > > Alexis. > [-- Attachment #2: Type: text/html, Size: 2919 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-25 21:35 ` Cristian Axenie @ 2009-05-25 22:10 ` Alexis Berlemont [not found] ` <9c789a000905251516j5272ae7bpc60aea8fdc17d50c@domain.hid> 0 siblings, 1 reply; 21+ messages in thread From: Alexis Berlemont @ 2009-05-25 22:10 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Cristian Axenie <cristian.axenie@domain.hid> writes: > Hi, > > I finally figured out this aspect but I still have one problem, residing in the fact that I have no comedi devices in my dev list > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! > > As I see it there are no comedi devices > > /usr/xenomai/sbin # cat /proc/devices You should not look at there. This proc file lists everything but RTDM devices. > > and the list > > /usr/xenomai/sbin # cat /proc/comedi/devices > -- Comedi devices -- > > | idx | status | driver > | 00 | Unused | No driver > | 01 | Unused | No driver > | 02 | Unused | No driver > | 03 | Unused | No driver > | 04 | Unused | No driver > | 05 | Unused | No driver > | 06 | Unused | No driver > | 07 | Unused | No driver > | 08 | Unused | No driver > | 09 | Unused | No driver > /usr/xenomai/sbin # cat /proc/comedi/drivers > comedi_config rtcanconfig rtps > /usr/xenomai/sbin # cat /proc/comedi/drivers > -- Comedi drivers -- > > | idx | driver name > | 00 | pcimio > | 01 | comedi_8255 > | 02 | comedi_loop > | 03 | comedi_fake > > Shouldn't the specific comedi devices be generated when installing Xenomai ? That is common comedi behaviour. So far, the comedi drivers are listed, they are available in the kernel. However, you have to attach them so as to make them reachable (thanks to comedi_config). Once the attach will be done, you will see your driver appear in /proc/comedi/devices. If the comedi_config did not work, the problem is here. In such case, could you send the traces? Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
[parent not found: <9c789a000905251516j5272ae7bpc60aea8fdc17d50c@domain.hid>]
* [Xenomai-help] Driver testing procedure ?! [not found] ` <9c789a000905251516j5272ae7bpc60aea8fdc17d50c@domain.hid> @ 2009-05-25 22:32 ` Cristian Axenie 2009-05-26 13:55 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-25 22:32 UTC (permalink / raw) To: xenomai [-- Attachment #1: Type: text/plain, Size: 2270 bytes --] ---------- Forwarded message ---------- From: Cristian Axenie <cristian.axenie@domain.hid> Date: Tue, May 26, 2009 at 1:16 AM Subject: Re: [Xenomai-help] Driver testing procedure ?! To: Alexis Berlemont <berlemont.hauw@domain.hid> On Tue, May 26, 2009 at 1:10 AM, Alexis Berlemont <berlemont.hauw@domain.hid>wrote: > Cristian Axenie <cristian.axenie@domain.hid> writes: > > > Hi, > > > > I finally figured out this aspect but I still have one problem, residing > in the fact that I have no comedi devices in my dev list > > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! > > > > As I see it there are no comedi devices > > > > /usr/xenomai/sbin # cat /proc/devices > > You should not look at there. This proc file lists everything but RTDM > devices. > > > > > and the list > > > > /usr/xenomai/sbin # cat /proc/comedi/devices > > -- Comedi devices -- > > > > | idx | status | driver > > | 00 | Unused | No driver > > | 01 | Unused | No driver > > | 02 | Unused | No driver > > | 03 | Unused | No driver > > | 04 | Unused | No driver > > | 05 | Unused | No driver > > | 06 | Unused | No driver > > | 07 | Unused | No driver > > | 08 | Unused | No driver > > | 09 | Unused | No driver > > /usr/xenomai/sbin # cat /proc/comedi/drivers > > comedi_config rtcanconfig rtps > > /usr/xenomai/sbin # cat /proc/comedi/drivers > > -- Comedi drivers -- > > > > | idx | driver name > > | 00 | pcimio > > | 01 | comedi_8255 > > | 02 | comedi_loop > > | 03 | comedi_fake > > > > Shouldn't the specific comedi devices be generated when installing > Xenomai ? > > That is common comedi behaviour. So far, the comedi drivers are listed, > they are available in the kernel. However, you have to attach them so as > to make them reachable (thanks to comedi_config). > > Once the attach will be done, you will see your driver appear in > /proc/comedi/devices. > > If the comedi_config did not work, the problem is here. In such case, > could you send the traces? The problem is that the comedi devs are not present in /dev and so when I run comedi config /usr/xenomai/sbin # ./comedi_config /dev/comedi0 pcimio comedi_config: comedi_open failed ret=-19 Shouldn't the comedi0, comedi1... devices be created when installing Xenomai ? > > > Alexis. > [-- Attachment #2: Type: text/html, Size: 3431 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-25 22:32 ` Cristian Axenie @ 2009-05-26 13:55 ` Alexis Berlemont 2009-05-26 14:36 ` Cristian Axenie 0 siblings, 1 reply; 21+ messages in thread From: Alexis Berlemont @ 2009-05-26 13:55 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, On Tue, May 26, 2009 at 12:32 AM, Cristian Axenie <cristian.axenie@domain.hid> wrote: > > > ---------- Forwarded message ---------- > From: Cristian Axenie <cristian.axenie@domain.hid> > Date: Tue, May 26, 2009 at 1:16 AM > Subject: Re: [Xenomai-help] Driver testing procedure ?! > To: Alexis Berlemont <berlemont.hauw@domain.hid> > > > > > On Tue, May 26, 2009 at 1:10 AM, Alexis Berlemont <berlemont.hauw@domain.hid> > wrote: >> >> Cristian Axenie <cristian.axenie@domain.hid> writes: >> >> > Hi, >> > >> > I finally figured out this aspect but I still have one problem, residing >> > in the fact that I have no comedi devices in my dev list >> > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! >> > >> > As I see it there are no comedi devices >> > >> > /usr/xenomai/sbin # cat /proc/devices >> >> You should not look at there. This proc file lists everything but RTDM >> devices. >> >> > >> > and the list >> > >> > /usr/xenomai/sbin # cat /proc/comedi/devices >> > -- Comedi devices -- >> > >> > | idx | status | driver >> > | 00 | Unused | No driver >> > | 01 | Unused | No driver >> > | 02 | Unused | No driver >> > | 03 | Unused | No driver >> > | 04 | Unused | No driver >> > | 05 | Unused | No driver >> > | 06 | Unused | No driver >> > | 07 | Unused | No driver >> > | 08 | Unused | No driver >> > | 09 | Unused | No driver >> > /usr/xenomai/sbin # cat /proc/comedi/drivers >> > comedi_config rtcanconfig rtps >> > /usr/xenomai/sbin # cat /proc/comedi/drivers >> > -- Comedi drivers -- >> > >> > | idx | driver name >> > | 00 | pcimio >> > | 01 | comedi_8255 >> > | 02 | comedi_loop >> > | 03 | comedi_fake >> > >> > Shouldn't the specific comedi devices be generated when installing >> > Xenomai ? >> >> That is common comedi behaviour. So far, the comedi drivers are listed, >> they are available in the kernel. However, you have to attach them so as >> to make them reachable (thanks to comedi_config). >> >> Once the attach will be done, you will see your driver appear in >> /proc/comedi/devices. >> >> If the comedi_config did not work, the problem is here. In such case, >> could you send the traces? > > The problem is that the comedi devs are not present in /dev and so when I > run comedi config > > /usr/xenomai/sbin # ./comedi_config /dev/comedi0 pcimio > comedi_config: comedi_open failed ret=-19 > > Shouldn't the comedi0, comedi1... devices be created when installing Xenomai > ? Here, we are talking about RTDM devices not common Linux /dev files. Have a look at /proc/xenomai/rtdm/comediXX. Consequently, your comedi_config command line should be "comedi_config comedi0 pcimio". Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-26 13:55 ` Alexis Berlemont @ 2009-05-26 14:36 ` Cristian Axenie 2009-05-26 15:19 ` Cristian Axenie 2009-05-26 21:48 ` Philippe Gerum 0 siblings, 2 replies; 21+ messages in thread From: Cristian Axenie @ 2009-05-26 14:36 UTC (permalink / raw) To: Alexis Berlemont, xenomai [-- Attachment #1: Type: text/plain, Size: 4634 bytes --] On Tue, May 26, 2009 at 4:55 PM, Alexis Berlemont <berlemont.hauw@domain.hid>wrote: > Hi, > > On Tue, May 26, 2009 at 12:32 AM, Cristian Axenie > <cristian.axenie@domain.hid> wrote: > > > > > > ---------- Forwarded message ---------- > > From: Cristian Axenie <cristian.axenie@domain.hid> > > Date: Tue, May 26, 2009 at 1:16 AM > > Subject: Re: [Xenomai-help] Driver testing procedure ?! > > To: Alexis Berlemont <berlemont.hauw@domain.hid> > > > > > > > > > > On Tue, May 26, 2009 at 1:10 AM, Alexis Berlemont < > berlemont.hauw@domain.hid> > > wrote: > >> > >> Cristian Axenie <cristian.axenie@domain.hid> writes: > >> > >> > Hi, > >> > > >> > I finally figured out this aspect but I still have one problem, > residing > >> > in the fact that I have no comedi devices in my dev list > >> > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! > >> > > >> > As I see it there are no comedi devices > >> > > >> > /usr/xenomai/sbin # cat /proc/devices > >> > >> You should not look at there. This proc file lists everything but RTDM > >> devices. > >> > >> > > >> > and the list > >> > > >> > /usr/xenomai/sbin # cat /proc/comedi/devices > >> > -- Comedi devices -- > >> > > >> > | idx | status | driver > >> > | 00 | Unused | No driver > >> > | 01 | Unused | No driver > >> > | 02 | Unused | No driver > >> > | 03 | Unused | No driver > >> > | 04 | Unused | No driver > >> > | 05 | Unused | No driver > >> > | 06 | Unused | No driver > >> > | 07 | Unused | No driver > >> > | 08 | Unused | No driver > >> > | 09 | Unused | No driver > >> > /usr/xenomai/sbin # cat /proc/comedi/drivers > >> > comedi_config rtcanconfig rtps > >> > /usr/xenomai/sbin # cat /proc/comedi/drivers > >> > -- Comedi drivers -- > >> > > >> > | idx | driver name > >> > | 00 | pcimio > >> > | 01 | comedi_8255 > >> > | 02 | comedi_loop > >> > | 03 | comedi_fake > >> > > >> > Shouldn't the specific comedi devices be generated when installing > >> > Xenomai ? > >> > >> That is common comedi behaviour. So far, the comedi drivers are listed, > >> they are available in the kernel. However, you have to attach them so as > >> to make them reachable (thanks to comedi_config). > >> > >> Once the attach will be done, you will see your driver appear in > >> /proc/comedi/devices. > >> > >> If the comedi_config did not work, the problem is here. In such case, > >> could you send the traces? > > > > The problem is that the comedi devs are not present in /dev and so when I > > run comedi config > > > > /usr/xenomai/sbin # ./comedi_config /dev/comedi0 pcimio > > comedi_config: comedi_open failed ret=-19 > > > > Shouldn't the comedi0, comedi1... devices be created when installing > Xenomai > > ? > > Here, we are talking about RTDM devices not common Linux /dev files. > Have a look at /proc/xenomai/rtdm/comediXX. Thanks for making it clear to me. I've tested with the comedi0 RTDM device and a (sad) SEGFAULT emerged here the oops /usr/xenomai/sbin # ./comedi_config comedi0 pcimio pcimio_attach: found pci-6024e board MITE: 0x90000000 mapped to c907a000 DAQ: 0x90001000 mapped to c907c000 MITE: version = 2, type = 1, mite mode = 1, interface mode = 3 MITE: num channels = 1, write post fifo depth = 1, wins = 0, iowins = 2 pcimio_attach: found irq 48 Unable to handle kernel paging request for data at address 0x0000001c Faulting instruction address: 0xc023923c Oops: Kernel access of bad area, sig: 11 [#1] MPC831x RDB Modules linked in: NIP: c023923c LR: c0249c2c CTR: c01bd8b4 REGS: c7a37cd0 TRAP: 0300 Not tainted (2.6.24.2) MSR: 00009032 <EE,ME,IR,DR> CR: 24008422 XER: 00000000 DAR: 0000001c, DSISR: 20000000 TASK = c78957f0[890] 'comedi_config' THREAD: c7a36000 GPR00: 0000ffff c7a37d80 c78957f0 c03ee0c0 00000030 c0246df4 00000001 c03ee0c0 GPR08: 00000001 00000000 00000000 00000000 24008422 1004a5b8 c031bf40 c03b0000 GPR16: c03b62ac c03cda00 fffffff0 c7a37f50 c03cda00 00000040 c7a37e48 c03ee0c0 GPR24: c03b0f98 c03b0bd8 00000000 c03d6608 c7900810 c7900c10 fffffff0 c03ee0c0 Call Trace: [c7a37d80] [00000001] (unreliable) [c7a37da0] [c0249c2c] [c7a37dd0] [c0236c94] [c7a37df0] [c0236dcc] [c7a37e30] [c02371dc] [c7a37e40] [c0239c78] [c7a37e70] [c0089588] [c7a37eb0] [c008b7b8] [c7a37ec0] [c0057db0] [c7a37ee0] [c0049158] [c7a37f30] [c0009644] [c7a37f40] [c0010ca4] --- Exception: c01Instruction dump: 38210010 7c0803a6 4e800020 9421ffe0 7c0802a6 bf61000c 7c7f1b78 3bc0fff0 90010024 38000000 6000ffff 81230008 <8169001c> 7f8b0000 419e001c 80010024 ---[ end trace 31c77e297a2e6a3e ]--- Any ideas ? > > > Consequently, your comedi_config command line should be "comedi_config > comedi0 pcimio". > > Alexis. > [-- Attachment #2: Type: text/html, Size: 6383 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-26 14:36 ` Cristian Axenie @ 2009-05-26 15:19 ` Cristian Axenie 2009-05-26 14:29 ` Alexis Berlemont 2009-05-26 21:48 ` Philippe Gerum 1 sibling, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-26 15:19 UTC (permalink / raw) To: Alexis Berlemont, xenomai [-- Attachment #1: Type: text/plain, Size: 5080 bytes --] On Tue, May 26, 2009 at 5:36 PM, Cristian Axenie <cristian.axenie@domain.hid>wrote: > > > On Tue, May 26, 2009 at 4:55 PM, Alexis Berlemont <berlemont.hauw@domain.hid>wrote: > >> Hi, >> >> On Tue, May 26, 2009 at 12:32 AM, Cristian Axenie >> <cristian.axenie@domain.hid> wrote: >> > >> > >> > ---------- Forwarded message ---------- >> > From: Cristian Axenie <cristian.axenie@domain.hid> >> > Date: Tue, May 26, 2009 at 1:16 AM >> > Subject: Re: [Xenomai-help] Driver testing procedure ?! >> > To: Alexis Berlemont <berlemont.hauw@domain.hid> >> > >> > >> > >> > >> > On Tue, May 26, 2009 at 1:10 AM, Alexis Berlemont < >> berlemont.hauw@domain.hid> >> > wrote: >> >> >> >> Cristian Axenie <cristian.axenie@domain.hid> writes: >> >> >> >> > Hi, >> >> > >> >> > I finally figured out this aspect but I still have one problem, >> residing >> >> > in the fact that I have no comedi devices in my dev list >> >> > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! >> >> > >> >> > As I see it there are no comedi devices >> >> > >> >> > /usr/xenomai/sbin # cat /proc/devices >> >> >> >> You should not look at there. This proc file lists everything but RTDM >> >> devices. >> >> >> >> > >> >> > and the list >> >> > >> >> > /usr/xenomai/sbin # cat /proc/comedi/devices >> >> > -- Comedi devices -- >> >> > >> >> > | idx | status | driver >> >> > | 00 | Unused | No driver >> >> > | 01 | Unused | No driver >> >> > | 02 | Unused | No driver >> >> > | 03 | Unused | No driver >> >> > | 04 | Unused | No driver >> >> > | 05 | Unused | No driver >> >> > | 06 | Unused | No driver >> >> > | 07 | Unused | No driver >> >> > | 08 | Unused | No driver >> >> > | 09 | Unused | No driver >> >> > /usr/xenomai/sbin # cat /proc/comedi/drivers >> >> > comedi_config rtcanconfig rtps >> >> > /usr/xenomai/sbin # cat /proc/comedi/drivers >> >> > -- Comedi drivers -- >> >> > >> >> > | idx | driver name >> >> > | 00 | pcimio >> >> > | 01 | comedi_8255 >> >> > | 02 | comedi_loop >> >> > | 03 | comedi_fake >> >> > >> >> > Shouldn't the specific comedi devices be generated when installing >> >> > Xenomai ? >> >> >> >> That is common comedi behaviour. So far, the comedi drivers are listed, >> >> they are available in the kernel. However, you have to attach them so >> as >> >> to make them reachable (thanks to comedi_config). >> >> >> >> Once the attach will be done, you will see your driver appear in >> >> /proc/comedi/devices. >> >> >> >> If the comedi_config did not work, the problem is here. In such case, >> >> could you send the traces? >> > >> > The problem is that the comedi devs are not present in /dev and so when >> I >> > run comedi config >> > >> > /usr/xenomai/sbin # ./comedi_config /dev/comedi0 pcimio >> > comedi_config: comedi_open failed ret=-19 >> > >> > Shouldn't the comedi0, comedi1... devices be created when installing >> Xenomai >> > ? >> >> Here, we are talking about RTDM devices not common Linux /dev files. >> Have a look at /proc/xenomai/rtdm/comediXX. > > > Thanks for making it clear to me. I've tested with the comedi0 RTDM > device and a (sad) SEGFAULT emerged > here the oops > > /usr/xenomai/sbin # ./comedi_config comedi0 pcimio > pcimio_attach: found pci-6024e board > MITE: 0x90000000 mapped to c907a000 DAQ: 0x90001000 mapped to c907c000 > MITE: version = 2, type = 1, mite mode = 1, interface mode = 3 > MITE: num channels = 1, write post fifo depth = 1, wins = 0, iowins = 2 > pcimio_attach: found irq 48 > Unable to handle kernel paging request for data at address 0x0000001c > Faulting instruction address: 0xc023923c > Oops: Kernel access of bad area, sig: 11 [#1] > MPC831x RDB > Modules linked in: > NIP: c023923c LR: c0249c2c CTR: c01bd8b4 > REGS: c7a37cd0 TRAP: 0300 Not tainted (2.6.24.2) > MSR: 00009032 <EE,ME,IR,DR> CR: 24008422 XER: 00000000 > DAR: 0000001c, DSISR: 20000000 > TASK = c78957f0[890] 'comedi_config' THREAD: c7a36000 > GPR00: 0000ffff c7a37d80 c78957f0 c03ee0c0 00000030 c0246df4 00000001 > c03ee0c0 > GPR08: 00000001 00000000 00000000 00000000 24008422 1004a5b8 c031bf40 > c03b0000 > GPR16: c03b62ac c03cda00 fffffff0 c7a37f50 c03cda00 00000040 c7a37e48 > c03ee0c0 > GPR24: c03b0f98 c03b0bd8 00000000 c03d6608 c7900810 c7900c10 fffffff0 > c03ee0c0 > Call Trace: > [c7a37d80] [00000001] (unreliable) > [c7a37da0] [c0249c2c] > [c7a37dd0] [c0236c94] > [c7a37df0] [c0236dcc] > [c7a37e30] [c02371dc] > [c7a37e40] [c0239c78] > [c7a37e70] [c0089588] > [c7a37eb0] [c008b7b8] > [c7a37ec0] [c0057db0] > [c7a37ee0] [c0049158] > [c7a37f30] [c0009644] > [c7a37f40] [c0010ca4] > --- Exception: c01Instruction dump: > 38210010 7c0803a6 4e800020 9421ffe0 7c0802a6 bf61000c 7c7f1b78 3bc0fff0 > 90010024 38000000 6000ffff 81230008 <8169001c> 7f8b0000 419e001c 80010024 > ---[ end trace 31c77e297a2e6a3e ]--- > > Any ideas ? > One thing ! This behaviour only appears when loading the pcimio driver . It not reproduces for comedi_fake or comedi_loop that are linked just fine. > > >> >> >> Consequently, your comedi_config command line should be "comedi_config >> comedi0 pcimio". >> >> Alexis. >> > > [-- Attachment #2: Type: text/html, Size: 7266 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-26 15:19 ` Cristian Axenie @ 2009-05-26 14:29 ` Alexis Berlemont 0 siblings, 0 replies; 21+ messages in thread From: Alexis Berlemont @ 2009-05-26 14:29 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Cristian Axenie <cristian.axenie@domain.hid> writes: > On Tue, May 26, 2009 at 5:36 PM, Cristian Axenie <cristian.axenie@domain.hidom> wrote: > > On Tue, May 26, 2009 at 4:55 PM, Alexis Berlemont <berlemont.hauw@domain.hide.fr> wrote: > > Hi, > > On Tue, May 26, 2009 at 12:32 AM, Cristian Axenie > <cristian.axenie@domain.hid> wrote: > > > > > > ---------- Forwarded message ---------- > > From: Cristian Axenie <cristian.axenie@domain.hid> > > Date: Tue, May 26, 2009 at 1:16 AM > > Subject: Re: [Xenomai-help] Driver testing procedure ?! > > To: Alexis Berlemont <berlemont.hauw@domain.hid> > > > > > > > > > > On Tue, May 26, 2009 at 1:10 AM, Alexis Berlemont <berlemont.hauw@domain.hid> > > wrote: > >> > >> Cristian Axenie <cristian.axenie@domain.hid> writes: > >> > >> > Hi, > >> > > >> > I finally figured out this aspect but I still have one problem, residing > >> > in the fact that I have no comedi devices in my dev list > >> > and so I cannot ./comedi_config /dev/comedi0 nipcimio ! > >> > > >> > As I see it there are no comedi devices > >> > > >> > /usr/xenomai/sbin # cat /proc/devices > >> > >> You should not look at there. This proc file lists everything but RTDM > >> devices. > >> > >> > > >> > and the list > >> > > >> > /usr/xenomai/sbin # cat /proc/comedi/devices > >> > -- Comedi devices -- > >> > > >> > | idx | status | driver > >> > | 00 | Unused | No driver > >> > | 01 | Unused | No driver > >> > | 02 | Unused | No driver > >> > | 03 | Unused | No driver > >> > | 04 | Unused | No driver > >> > | 05 | Unused | No driver > >> > | 06 | Unused | No driver > >> > | 07 | Unused | No driver > >> > | 08 | Unused | No driver > >> > | 09 | Unused | No driver > >> > /usr/xenomai/sbin # cat /proc/comedi/drivers > >> > comedi_config rtcanconfig rtps > >> > /usr/xenomai/sbin # cat /proc/comedi/drivers > >> > -- Comedi drivers -- > >> > > >> > | idx | driver name > >> > | 00 | pcimio > >> > | 01 | comedi_8255 > >> > | 02 | comedi_loop > >> > | 03 | comedi_fake > >> > > >> > Shouldn't the specific comedi devices be generated when installing > >> > Xenomai ? > >> > >> That is common comedi behaviour. So far, the comedi drivers are listed, > >> they are available in the kernel. However, you have to attach them so as > >> to make them reachable (thanks to comedi_config). > >> > >> Once the attach will be done, you will see your driver appear in > >> /proc/comedi/devices. > >> > >> If the comedi_config did not work, the problem is here. In such case, > >> could you send the traces? > > > > The problem is that the comedi devs are not present in /dev and so when I > > run comedi config > > > > /usr/xenomai/sbin # ./comedi_config /dev/comedi0 pcimio > > comedi_config: comedi_open failed ret=-19 > > > > Shouldn't the comedi0, comedi1... devices be created when installing Xenomai > > ? > > Here, we are talking about RTDM devices not common Linux /dev files. > Have a look at /proc/xenomai/rtdm/comediXX. > > Thanks for making it clear to me. I've tested with the comedi0 RTDM device and a (sad) SEGFAULT emerged > here the oops That was expected considering the amount of code. We need to locate the segfault origin inside the driver. According to your description, it must be in the attach procedure (in the function pcimio_attach()). It is even bound to be located in the function ni_E_init() which is quite big. A simple method would be to use dichotomy to find out the faulting line thanks to traces (rtdm_printk()). Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-26 14:36 ` Cristian Axenie 2009-05-26 15:19 ` Cristian Axenie @ 2009-05-26 21:48 ` Philippe Gerum [not found] ` <9c789a000905261525q45cbaa3ag25855befde1cb130@domain.hid> 1 sibling, 1 reply; 21+ messages in thread From: Philippe Gerum @ 2009-05-26 21:48 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai On Tue, 2009-05-26 at 17:36 +0300, Cristian Axenie wrote: > Unable to handle kernel paging request for data at address 0x0000001c > Faulting instruction address: 0xc023923c > Oops: Kernel access of bad area, sig: 11 [#1] > MPC831x RDB > Modules linked in: > NIP: c023923c LR: c0249c2c CTR: c01bd8b4 Please compile your kernel with CONFIG_DEBUG_INFO enabled. Then, from the root of your kernel tree, get a disassembly of the entire kernel: # ppc_6xx-objdump -dl vmlinux > foo.s (this may take a while) NIP is the code location your ppc kernel was attempting to execute from before jumping out of the window, so find the assembly line the NIP register value points at (leftmost field of the output), and post back the disassembly of the entire enclosing function. TIA, -- Philippe. ^ permalink raw reply [flat|nested] 21+ messages in thread
[parent not found: <9c789a000905261525q45cbaa3ag25855befde1cb130@domain.hid>]
* [Xenomai-help] Fwd: Driver testing procedure ?! [not found] ` <9c789a000905261525q45cbaa3ag25855befde1cb130@domain.hid> @ 2009-05-26 22:31 ` Cristian Axenie 2009-05-26 22:35 ` [Xenomai-help] " Cristian Axenie 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-26 22:31 UTC (permalink / raw) To: xenomai, Alexis Berlemont [-- Attachment #1: Type: text/plain, Size: 1461 bytes --] So I've managed to spot the location c023923c <comedi_ioctl_chaninfo>: comedi_ioctl_chaninfo(): /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:216 c023923c: 94 21 ff d0 stwu r1,-48(r1) c0239240: 7c 08 02 a6 mflr r0 c0239244: bf 81 00 20 stmw r28,32(r1) c0239248: 90 01 00 34 stw r0,52(r1) /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:218 c023924c: 83 e3 00 00 lwz r31,0(r3) And now ? On Wed, May 27, 2009 at 12:48 AM, Philippe Gerum <rpm@xenomai.org> wrote: > On Tue, 2009-05-26 at 17:36 +0300, Cristian Axenie wrote: > > > Unable to handle kernel paging request for data at address 0x0000001c > > Faulting instruction address: 0xc023923c > > Oops: Kernel access of bad area, sig: 11 [#1] > > MPC831x RDB > > Modules linked in: > > NIP: c023923c LR: c0249c2c CTR: c01bd8b4 > > Please compile your kernel with CONFIG_DEBUG_INFO enabled. Then, from > the root of your kernel tree, get a disassembly of the entire kernel: > > # ppc_6xx-objdump -dl vmlinux > foo.s > (this may take a while) > > NIP is the code location your ppc kernel was attempting to execute from > before jumping out of the window, so find the assembly line the NIP > register value points at (leftmost field of the output), and post back > the disassembly of the entire enclosing function. TIA, > > -- > Philippe. > > > [-- Attachment #2: Type: text/html, Size: 2010 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* [Xenomai-help] Driver testing procedure ?! 2009-05-26 22:31 ` [Xenomai-help] Fwd: " Cristian Axenie @ 2009-05-26 22:35 ` Cristian Axenie 2009-05-27 21:47 ` Cristian Axenie 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-26 22:35 UTC (permalink / raw) To: xenomai [-- Attachment #1: Type: text/plain, Size: 1461 bytes --] So I've managed to spot the location c023923c <comedi_ioctl_chaninfo>: comedi_ioctl_chaninfo(): /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:216 c023923c: 94 21 ff d0 stwu r1,-48(r1) c0239240: 7c 08 02 a6 mflr r0 c0239244: bf 81 00 20 stmw r28,32(r1) c0239248: 90 01 00 34 stw r0,52(r1) /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:218 c023924c: 83 e3 00 00 lwz r31,0(r3) And now ? On Wed, May 27, 2009 at 12:48 AM, Philippe Gerum <rpm@xenomai.org> wrote: > On Tue, 2009-05-26 at 17:36 +0300, Cristian Axenie wrote: > > > Unable to handle kernel paging request for data at address 0x0000001c > > Faulting instruction address: 0xc023923c > > Oops: Kernel access of bad area, sig: 11 [#1] > > MPC831x RDB > > Modules linked in: > > NIP: c023923c LR: c0249c2c CTR: c01bd8b4 > > Please compile your kernel with CONFIG_DEBUG_INFO enabled. Then, from > the root of your kernel tree, get a disassembly of the entire kernel: > > # ppc_6xx-objdump -dl vmlinux > foo.s > (this may take a while) > > NIP is the code location your ppc kernel was attempting to execute from > before jumping out of the window, so find the assembly line the NIP > register value points at (leftmost field of the output), and post back > the disassembly of the entire enclosing function. TIA, > > -- > Philippe. > > > [-- Attachment #2: Type: text/html, Size: 2086 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-26 22:35 ` [Xenomai-help] " Cristian Axenie @ 2009-05-27 21:47 ` Cristian Axenie 2009-05-28 6:38 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-05-27 21:47 UTC (permalink / raw) To: xenomai, Alexis Berlemont [-- Attachment #1: Type: text/plain, Size: 4467 bytes --] Hi! Without no modiffications (just some printks) I've got a new trace pointing that the problem is at another location : /usr/xenomai/sbin # gdb comedi_config GNU gdb Red Hat Linux (6.7-1rh) Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "ppc-linux"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run comedi0 pcimio Starting program: /usr/xenomai/sbin/comedi_config comedi0 pcimio [Thread debugging using libthread_db enabled] [New Thread 0x4801ea60 (LWP 907)] pcimio_attach: found pci-6024e board MITE: 0x90000000 mapped to c907a000 DAQ: 0x90001000 mapped to c907c000 MITE: version = 2, type = 1, mite mode = 1, interface mode = 3 MITE: num channels = 1, write post fifo depth = 1, wins = 0, iowins = 2 pcimio_attach: found irq 48 Unable to handle kernel paging request for data at address 0x0000001c Faulting instruction address: 0xc02399e4 Oops: Kernel access of bad area, sig: 11 [#1] MPC831x RDB Modules linked in: *NIP: c02399e4* LR: c024a4d8 CTR: c003218c REGS: c7ad3cd0 TRAP: 0300 Not tainted (2.6.24.2) MSR: 00009032 <EE,ME,IR,DR> CR: 24008422 XER: 00000000 DAR: 0000001c, DSISR: 20000000 TASK = c7889430[907] 'comedi_config' THREAD: c7ad2000 GPR00: 0000ffff c7ad3d80 c7889430 c03ee0e0 00000030 c024759c 00000001 c03ee0e0 GPR08: 0d293884 00000000 00000003 c039fd20 24008424 1004a5b8 00000000 c03b0000 GPR16: c03b72ac c03cda00 fffffff0 c7ad3f50 c03cda00 00000040 c7ad3e48 c03ee0e0 GPR24: c03b1f98 c03b1bd8 00000000 c03d6628 c7900810 c7900c10 fffffff0 c03ee0e0 Call Trace: [c7ad3d80] [00000001] (unreliable) [c7ad3da0] [c024a4d8] [c7ad3dd0] [c0237410] [c7ad3df0] [c0237548] [c7ad3e30] [c0237958] [c7ad3e40] [c023a420] [c7ad3e70] [c00895b8] [c7ad3eb0] [c008b7e8] [c7ad3ec0] [c0057de0] [c7ad3ee0] [c0049188] [c7ad3f30] [c0009644] [c7ad3f40] [c0010ca4] --- Exception: c01Instruction dump: 38210010 7c0803a6 4e800020 9421ffe0 7c0802a6 bf61000c 7c7f1b78 3bc0fff0 90010024 38000000 6000ffff 81230008 <8169001c> 7f8b0000 419e001c 80010024 ---[ end trace fed837f399783f24 ]--- and the location from the kernel dissasembly points to : /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/transfer.c:317 c02399d8: 38 00 00 00 li r0,0 c02399dc: 60 00 ff ff ori r0,r0,65535 c02399e0: 81 23 00 08 lwz r9,8(r3) *c02399e4: 81 69 00 1c lwz r11,28(r9)* c02399e8: 7f 8b 00 00 cmpw cr7,r11,r0 c02399ec: 41 9e 00 1c beq- cr7,c0239a08 <comedi_request_irq+0x48> Do you have any idea what is the source for this random erroneous behaviour ? Best ! On Wed, May 27, 2009 at 1:35 AM, Cristian Axenie <cristian.axenie@domain.hid>wrote: > > So I've managed to spot the location > > c023923c <comedi_ioctl_chaninfo>: > comedi_ioctl_chaninfo(): > > /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:216 > c023923c: 94 21 ff d0 stwu r1,-48(r1) > c0239240: 7c 08 02 a6 mflr r0 > c0239244: bf 81 00 20 stmw r28,32(r1) > c0239248: 90 01 00 34 stw r0,52(r1) > > /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/subdevice.c:218 > c023924c: 83 e3 00 00 lwz r31,0(r3) > > And now ? > > > On Wed, May 27, 2009 at 12:48 AM, Philippe Gerum <rpm@xenomai.org> wrote: > >> On Tue, 2009-05-26 at 17:36 +0300, Cristian Axenie wrote: >> >> > Unable to handle kernel paging request for data at address 0x0000001c >> > Faulting instruction address: 0xc023923c >> > Oops: Kernel access of bad area, sig: 11 [#1] >> > MPC831x RDB >> > Modules linked in: >> > NIP: c023923c LR: c0249c2c CTR: c01bd8b4 >> >> Please compile your kernel with CONFIG_DEBUG_INFO enabled. Then, from >> the root of your kernel tree, get a disassembly of the entire kernel: >> >> # ppc_6xx-objdump -dl vmlinux > foo.s >> (this may take a while) >> >> NIP is the code location your ppc kernel was attempting to execute from >> before jumping out of the window, so find the assembly line the NIP >> register value points at (leftmost field of the output), and post back >> the disassembly of the entire enclosing function. TIA, >> >> -- >> Philippe. >> >> >> > > > [-- Attachment #2: Type: text/html, Size: 5707 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-27 21:47 ` Cristian Axenie @ 2009-05-28 6:38 ` Alexis Berlemont 2009-06-04 0:23 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Alexis Berlemont @ 2009-05-28 6:38 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, On Wed, May 27, 2009 at 11:47 PM, Cristian Axenie <cristian.axenie@domain.hid> wrote: > Hi! > > Without no modiffications (just some printks) I've got a new trace pointing > that the problem is at another location : > > and the location from the kernel dissasembly points to : > > /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/transfer.c:317 > c02399d8: 38 00 00 00 li r0,0 > c02399dc: 60 00 ff ff ori r0,r0,65535 > c02399e0: 81 23 00 08 lwz r9,8(r3) > c02399e4: 81 69 00 1c lwz r11,28(r9) > c02399e8: 7f 8b 00 00 cmpw cr7,r11,r0 > c02399ec: 41 9e 00 1c beq- cr7,c0239a08 <comedi_request_irq+0x48> > > > Do you have any idea what is the source for this random erroneous behaviour > ? Ok. Thanks, I will have a look at that location. By the way, I think there was another mistake (I made) in the attach procedure (comedi_init_drv() called twice). But do not expect any git update today, I am unavailable until tonight. Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-05-28 6:38 ` Alexis Berlemont @ 2009-06-04 0:23 ` Alexis Berlemont 2009-06-04 8:20 ` Cristian Axenie 0 siblings, 1 reply; 21+ messages in thread From: Alexis Berlemont @ 2009-06-04 0:23 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, Alexis Berlemont <berlemont.hauw@domain.hid> writes: > Hi, > > On Wed, May 27, 2009 at 11:47 PM, Cristian Axenie > <cristian.axenie@domain.hid> wrote: >> Hi! >> >> Without no modiffications (just some printks) I've got a new trace pointing >> that the problem is at another location : >> >> and the location from the kernel dissasembly points to : >> >> /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/transfer.c:317 >> c02399d8: 38 00 00 00 li r0,0 >> c02399dc: 60 00 ff ff ori r0,r0,65535 >> c02399e0: 81 23 00 08 lwz r9,8(r3) >> c02399e4: 81 69 00 1c lwz r11,28(r9) >> c02399e8: 7f 8b 00 00 cmpw cr7,r11,r0 >> c02399ec: 41 9e 00 1c beq- cr7,c0239a08 <comedi_request_irq+0x48> >> >> >> Do you have any idea what is the source for this random erroneous behaviour >> ? > > Ok. Thanks, I will have a look at that location. By the way, I think > there was another mistake (I made) in the attach procedure > (comedi_init_drv() called twice). > > But do not expect any git update today, I am unavailable until tonight. I updated my git repository (comedi branch). Could you test it? Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-06-04 0:23 ` Alexis Berlemont @ 2009-06-04 8:20 ` Cristian Axenie 2009-06-04 9:00 ` Alexis Berlemont 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-06-04 8:20 UTC (permalink / raw) To: Alexis Berlemont, xenomai [-- Attachment #1: Type: text/plain, Size: 3205 bytes --] Hy I,ve tested the new git update and failed /usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio Unable to handle kernel paging request for data at address 0x0000001c Faulting instruction address: 0xc0239c5c Oops: Kernel access of bad area, sig: 11 [#1] MPC831x RDB Modules linked in: *NIP: c0239c5c* LR: c024aaf8 CTR: 00000000 REGS: c7affcd0 TRAP: 0300 Not tainted (2.6.24.2) MSR: 00009032 <EE,ME,IR,DR> CR: 24008424 XER: 00000000 DAR: 0000001c, DSISR: 20000000 TASK = c7889430[1536] 'comedi_config' THREAD: c7afe000 GPR00: 0000ffff c7affd80 c7889430 c03f00e0 00000030 c0247d44 00000001 c03f00e0 GPR08: c907a000 00000000 00000001 c7810400 c7900a00 1004a5b8 c033c200 c03c0000 GPR16: c03b83c4 c03cfa00 fffffff0 c7afff50 c03cfa00 00000040 00000010 c03a0ca0 GPR24: c03f00e0 c03b2cf0 00000000 00000000 c7900800 c03d8628 fffffff0 c03f00e0 Call Trace: [c7affd80] [c023c2d4] (unreliable) [c7affda0] [c024aaf8] [c7affdd0] [c02376f8] [c7affdf0] [c0237830] [c7affe30] [c0237c50] [c7affe40] [c023a5e8] [c7affe70] [c0089820] [c7affeb0] [c008ba50] [c7affec0] [c00582d0] [c7affee0] [c0049188] [c7afff30] [c0009644] [c7afff40] [c0010ca4] --- Exception: c01Instruction dump: 38210010 7c0803a6 4e800020 9421ffe0 7c0802a6 bf61000c 7c7f1b78 3bc0fff0 90010024 38000000 6000ffff 81230010 <8169001c> 7f8b0000 419e001c 80010024 ---[ end trace 78f6932e4d494a5a ]--- and I've managed to trace the fault /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-integration/drivers/xenomai/comedi/transfer.c:295 c0239c50: 38 00 00 00 li r0,0 c0239c54: 60 00 ff ff ori r0,r0,65535 c0239c58: 81 23 00 10 lwz r9,16(r3) *c0239c5c: 81 69 00 1c lwz r11,28(r9)* c0239c60: 7f 8b 00 00 cmpw cr7,r11,r0 c0239c64: 41 9e 00 1c beq- cr7,c0239c80 <comedi_request_irq+0x48> What do you think ? On Thu, Jun 4, 2009 at 3:23 AM, Alexis Berlemont <berlemont.hauw@domain.hid>wrote: > Hi, > > Alexis Berlemont <berlemont.hauw@domain.hid> writes: > > > Hi, > > > > On Wed, May 27, 2009 at 11:47 PM, Cristian Axenie > > <cristian.axenie@domain.hid> wrote: > >> Hi! > >> > >> Without no modiffications (just some printks) I've got a new trace > pointing > >> that the problem is at another location : > >> > >> and the location from the kernel dissasembly points to : > >> > >> > /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-prepared/drivers/xenomai/comedi/transfer.c:317 > >> c02399d8: 38 00 00 00 li r0,0 > >> c02399dc: 60 00 ff ff ori r0,r0,65535 > >> c02399e0: 81 23 00 08 lwz r9,8(r3) > >> c02399e4: 81 69 00 1c lwz r11,28(r9) > >> c02399e8: 7f 8b 00 00 cmpw cr7,r11,r0 > >> c02399ec: 41 9e 00 1c beq- cr7,c0239a08 > <comedi_request_irq+0x48> > >> > >> > >> Do you have any idea what is the source for this random erroneous > behaviour > >> ? > > > > Ok. Thanks, I will have a look at that location. By the way, I think > > there was another mistake (I made) in the attach procedure > > (comedi_init_drv() called twice). > > > > But do not expect any git update today, I am unavailable until tonight. > > I updated my git repository (comedi branch). Could you test it? > > Alexis. > [-- Attachment #2: Type: text/html, Size: 4120 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [Xenomai-help] Driver testing procedure ?! 2009-06-04 8:20 ` Cristian Axenie @ 2009-06-04 9:00 ` Alexis Berlemont 0 siblings, 0 replies; 21+ messages in thread From: Alexis Berlemont @ 2009-06-04 9:00 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, On Thu, Jun 4, 2009 at 10:20 AM, Cristian Axenie <cristian.axenie@domain.hid> wrote: > Hy I,ve tested the new git update and failed > > /usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio > Unable to handle kernel paging request for data at address 0x0000001c > Faulting instruction address: 0xc0239c5c > Oops: Kernel access of bad area, sig: 11 [#1] > MPC831x RDB > Modules linked in: > NIP: c0239c5c LR: c024aaf8 CTR: 00000000 > REGS: c7affcd0 TRAP: 0300 Not tainted (2.6.24.2) > MSR: 00009032 <EE,ME,IR,DR> CR: 24008424 XER: 00000000 > DAR: 0000001c, DSISR: 20000000 > TASK = c7889430[1536] 'comedi_config' THREAD: c7afe000 > GPR00: 0000ffff c7affd80 c7889430 c03f00e0 00000030 c0247d44 00000001 > c03f00e0 > GPR08: c907a000 00000000 00000001 c7810400 c7900a00 1004a5b8 c033c200 > c03c0000 > GPR16: c03b83c4 c03cfa00 fffffff0 c7afff50 c03cfa00 00000040 00000010 > c03a0ca0 > GPR24: c03f00e0 c03b2cf0 00000000 00000000 c7900800 c03d8628 fffffff0 > c03f00e0 > Call Trace: > [c7affd80] [c023c2d4] (unreliable) > [c7affda0] [c024aaf8] > [c7affdd0] [c02376f8] > [c7affdf0] [c0237830] > [c7affe30] [c0237c50] > [c7affe40] [c023a5e8] > [c7affe70] [c0089820] > [c7affeb0] [c008ba50] > [c7affec0] [c00582d0] > [c7affee0] [c0049188] > [c7afff30] [c0009644] > [c7afff40] [c0010ca4] > --- Exception: c01Instruction dump: > 38210010 7c0803a6 4e800020 9421ffe0 7c0802a6 bf61000c 7c7f1b78 3bc0fff0 > 90010024 38000000 6000ffff 81230010 <8169001c> 7f8b0000 419e001c 80010024 > ---[ end trace 78f6932e4d494a5a ]--- > > and I've managed to trace the fault > > /home/haustiq/development/eldk/ppc_6xx/usr/src/linux-2.6.24-integration/drivers/xenomai/comedi/transfer.c:295 > c0239c50: 38 00 00 00 li r0,0 > c0239c54: 60 00 ff ff ori r0,r0,65535 > c0239c58: 81 23 00 10 lwz r9,16(r3) > c0239c5c: 81 69 00 1c lwz r11,28(r9) > c0239c60: 7f 8b 00 00 cmpw cr7,r11,r0 > c0239c64: 41 9e 00 1c beq- cr7,c0239c80 <comedi_request_irq+0x48> > > What do you think ? > OK. I must have missed something obvious. I will dig further. Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
* [Xenomai-help] Driver testing procedure ?!
@ 2009-06-16 15:10 Cristian Axenie
2009-06-16 16:06 ` Alexis Berlemont
[not found] ` <72cf3fb0906160852v46b1602fwe39b135d8b11ba97@domain.hid>
0 siblings, 2 replies; 21+ messages in thread
From: Cristian Axenie @ 2009-06-16 15:10 UTC (permalink / raw)
To: Alexis Berlemont, Alexis Berlemont, xenomai
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi !
I've got a snapshot of the current git update but I still receive some
errors! Now the kernel is stable and doesn't crashes anymore but it seems
that there is a problem with attaching a driver !
Here's the output !
/usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio
PCI: Unable to reserve mem region #1:1000@domain.hid for device 0000:00:10.0
Comedi: comedi_pcimio: pcmio_attach: error setting up mite
Comedi: comedi_assign_driver: call(drv->attach) failed (ret=-5)
comedi_config: comedi_snd_attach failed ret=-5
THe fake and the loop drivers are attaching properly !
Best !
[-- Attachment #2: Type: text/html, Size: 661 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: [Xenomai-help] Driver testing procedure ?! 2009-06-16 15:10 Cristian Axenie @ 2009-06-16 16:06 ` Alexis Berlemont [not found] ` <72cf3fb0906160852v46b1602fwe39b135d8b11ba97@domain.hid> 1 sibling, 0 replies; 21+ messages in thread From: Alexis Berlemont @ 2009-06-16 16:06 UTC (permalink / raw) To: Cristian Axenie; +Cc: xenomai Hi, On Tue, Jun 16, 2009 at 5:10 PM, Cristian Axenie<cristian.axenie@domain.hid> wrote: > Hi ! > I've got a snapshot of the current git update but I still receive some > errors! Now the kernel is stable and doesn't crashes anymore but it seems > that there is a problem with attaching a driver ! > > Here's the output ! > > /usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio > PCI: Unable to reserve mem region #1:1000@domain.hid for device 0000:00:10.0 > Comedi: comedi_pcimio: pcmio_attach: error setting up mite > Comedi: comedi_assign_driver: call(drv->attach) failed (ret=-5) > comedi_config: comedi_snd_attach failed ret=-5 > Thank you for the feedback. The error message is quite clear. Could you send a dump of the command "cat /proc/iomem" on your board? Alexis. ^ permalink raw reply [flat|nested] 21+ messages in thread
[parent not found: <72cf3fb0906160852v46b1602fwe39b135d8b11ba97@domain.hid>]
[parent not found: <9c789a000906161348g43721abdu42aa2e727fcfd0cf@domain.hid>]
* [Xenomai-help] Driver testing procedure ?! [not found] ` <9c789a000906161348g43721abdu42aa2e727fcfd0cf@domain.hid> @ 2009-06-16 20:49 ` Cristian Axenie [not found] ` <9c789a000906161402y53c793f9n93635f9e044e358d@domain.hid> 0 siblings, 1 reply; 21+ messages in thread From: Cristian Axenie @ 2009-06-16 20:49 UTC (permalink / raw) To: xenomai [-- Attachment #1: Type: text/plain, Size: 1627 bytes --] Hi ! Sorry for the latency in my response ! Here the output after attaching the comedi_pcimio driver /usr/xenomai/sbin # cat /proc/iomem 80000000-8fffffff : /pci@domain.hid 90000000-9fffffff : /pci@domain.hid 90000000-90000fff : 0000:00:10.0 90000000-90000fff : mite 90001000-90001fff : 0000:00:10.0 90001000-90001fff : mite a0000000-afffffff : /pci@domain.hid c0000000-cfffffff : /pci@domain.hid e0000200-e00002ff : wdt e0004500-e0004507 : serial e0004600-e0004607 : serial e0007000-e0007fff : spi e0023000-e0023fff : usb e0023000-e0023fff : ehci_hcd e0024000-e0024fff : ethernet e0024520-e002453f : mdio e0025000-e0025fff : ethernet fe000000-fe7fffff : fe000000.nor It clears it out ?! On Tue, Jun 16, 2009 at 6:52 PM, Alexis Berlemont < alexis.berlemont@domain.hid> wrote: > Hi, > > On Tue, Jun 16, 2009 at 5:10 PM, Cristian > Axenie<cristian.axenie@domain.hid> wrote: > > Hi ! > > I've got a snapshot of the current git update but I still receive some > > errors! Now the kernel is stable and doesn't crashes anymore but it seems > > that there is a problem with attaching a driver ! > > > > Here's the output ! > > > > /usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio > > PCI: Unable to reserve mem region #1:1000@domain.hid for device > 0000:00:10.0 > > Comedi: comedi_pcimio: pcmio_attach: error setting up mite > > Comedi: comedi_assign_driver: call(drv->attach) failed (ret=-5) > > comedi_config: comedi_snd_attach failed ret=-5 > > > > Thank you for the feedback. The error message is quite clear. > > Could you send a dump of the command "cat /proc/iomem" on your board? > > Alexis. > [-- Attachment #2: Type: text/html, Size: 2332 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
[parent not found: <9c789a000906161402y53c793f9n93635f9e044e358d@domain.hid>]
* Re: [Xenomai-help] Driver testing procedure ?! [not found] ` <9c789a000906161402y53c793f9n93635f9e044e358d@domain.hid> @ 2009-06-17 12:51 ` Cristian Axenie 0 siblings, 0 replies; 21+ messages in thread From: Cristian Axenie @ 2009-06-17 12:51 UTC (permalink / raw) To: Alexis Berlemont, Alexis Berlemont, xenomai [-- Attachment #1: Type: text/plain, Size: 4958 bytes --] Hi ! If this helps , here's a dump of the PCI info! /usr/xenomai/sbin # lspci -vvxxx 00:00.0 Power PC: Freescale Semiconductor Inc Unknown device 00b4 (rev 10) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- Latency: 128, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 16 Region 2: Memory at <unassigned> (64-bit, prefetchable) Region 4: Memory at <unassigned> (64-bit, non-prefetchable) Capabilities: [48] #06 [0000] Capabilities: [80] Power Management version 3 Flags: PMEClk+ DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 57 19 b4 00 06 01 b0 20 10 00 20 0b 08 80 00 00 10: 00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00 20: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 48 00 00 00 00 00 00 00 00 01 00 00 40: 00 00 00 00 20 00 00 00 06 80 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 01 00 2b 7e 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:10.0 Class ff00: National Instruments PCI-6024E Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 128, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at 90000000 (32-bit, non-prefetchable) [size=4K] Region 1: Memory at 90001000 (32-bit, non-prefetchable) [size=4K] 00: 93 10 70 2a 06 00 80 02 00 00 00 ff 08 80 00 00 10: 00 00 00 90 00 10 00 90 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40: ac ac 00 00 00 00 00 00 00 00 00 80 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Best ! On Wed, Jun 17, 2009 at 12:02 AM, Cristian Axenie <cristian.axenie@domain.hid > wrote: > > > ---------- Forwarded message ---------- > From: Cristian Axenie <cristian.axenie@domain.hid> > Date: Tue, Jun 16, 2009 at 11:49 PM > Subject: [Xenomai-help]Driver testing procedure ?! > To: xenomai@xenomai.org > > > > > Hi ! > Sorry for the latency in my response ! > > Here the output after attaching the comedi_pcimio driver > > /usr/xenomai/sbin # cat /proc/iomem > 80000000-8fffffff : /pci@domain.hid > 90000000-9fffffff : /pci@domain.hid > 90000000-90000fff : 0000:00:10.0 > 90000000-90000fff : mite > 90001000-90001fff : 0000:00:10.0 > 90001000-90001fff : mite > a0000000-afffffff : /pci@domain.hid > c0000000-cfffffff : /pci@domain.hid > e0000200-e00002ff : wdt > e0004500-e0004507 : serial > e0004600-e0004607 : serial > e0007000-e0007fff : spi > e0023000-e0023fff : usb > e0023000-e0023fff : ehci_hcd > e0024000-e0024fff : ethernet > e0024520-e002453f : mdio > e0025000-e0025fff : ethernet > fe000000-fe7fffff : fe000000.nor > > It clears it out ?! > > > On Tue, Jun 16, 2009 at 6:52 PM, Alexis Berlemont < > alexis.berlemont@domain.hid> wrote: > >> Hi, >> >> On Tue, Jun 16, 2009 at 5:10 PM, Cristian >> Axenie<cristian.axenie@domain.hid> wrote: >> > Hi ! >> > I've got a snapshot of the current git update but I still receive some >> > errors! Now the kernel is stable and doesn't crashes anymore but it >> seems >> > that there is a problem with attaching a driver ! >> > >> > Here's the output ! >> > >> > /usr/xenomai/sbin # ./comedi_config comedi0 comedi_pcimio >> > PCI: Unable to reserve mem region #1:1000@domain.hid for device >> 0000:00:10.0 >> > Comedi: comedi_pcimio: pcmio_attach: error setting up mite >> > Comedi: comedi_assign_driver: call(drv->attach) failed (ret=-5) >> > comedi_config: comedi_snd_attach failed ret=-5 >> > >> >> Thank you for the feedback. The error message is quite clear. >> >> Could you send a dump of the command "cat /proc/iomem" on your board? >> >> Alexis. >> > > > > [-- Attachment #2: Type: text/html, Size: 6391 bytes --] ^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2009-06-17 12:51 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-25 11:46 [Xenomai-help] Driver testing procedure ?! Cristian Axenie
2009-05-25 21:28 ` Alexis Berlemont
2009-05-25 21:35 ` Cristian Axenie
2009-05-25 22:10 ` Alexis Berlemont
[not found] ` <9c789a000905251516j5272ae7bpc60aea8fdc17d50c@domain.hid>
2009-05-25 22:32 ` Cristian Axenie
2009-05-26 13:55 ` Alexis Berlemont
2009-05-26 14:36 ` Cristian Axenie
2009-05-26 15:19 ` Cristian Axenie
2009-05-26 14:29 ` Alexis Berlemont
2009-05-26 21:48 ` Philippe Gerum
[not found] ` <9c789a000905261525q45cbaa3ag25855befde1cb130@domain.hid>
2009-05-26 22:31 ` [Xenomai-help] Fwd: " Cristian Axenie
2009-05-26 22:35 ` [Xenomai-help] " Cristian Axenie
2009-05-27 21:47 ` Cristian Axenie
2009-05-28 6:38 ` Alexis Berlemont
2009-06-04 0:23 ` Alexis Berlemont
2009-06-04 8:20 ` Cristian Axenie
2009-06-04 9:00 ` Alexis Berlemont
-- strict thread matches above, loose matches on Subject: below --
2009-06-16 15:10 Cristian Axenie
2009-06-16 16:06 ` Alexis Berlemont
[not found] ` <72cf3fb0906160852v46b1602fwe39b135d8b11ba97@domain.hid>
[not found] ` <9c789a000906161348g43721abdu42aa2e727fcfd0cf@domain.hid>
2009-06-16 20:49 ` Cristian Axenie
[not found] ` <9c789a000906161402y53c793f9n93635f9e044e358d@domain.hid>
2009-06-17 12:51 ` Cristian Axenie
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.