Jan Kiszka wrote: > Juha Niskanen wrote: >> 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: >>> Juha Niskanen wrote: >>>> Hi Jan, >>>> >>> [...] >>> >>>>>> I can allready start the rtnet and get a lot of error messages. >>>>>> >>>>>> rteth0: tx queue full!. >>>>>> rteth0: tx queue full!. >>>>>> >>>>> Transmission is not working, maybe its IRQ line setup is broken. Thus >>>> Any idea of good place to start debugging? >>> Do you get interrupts? Check /proc/xenomai/irq! I briefly browsed the >>> code: a RTDM interrupt handler should return RTDM_IRQ_HANDLED and _not_ >>> IRQ_HANDLED. >> I get interrupts only for a virtual irq line 259 every time I ping. >> >> ~ $ cat /proc/xenomai/irq >> IRQ CPU0 >> 256: 57723 [virtual] >> 259: 2 [virtual] >> >> ~ $ modprobe rt_mpc8260_fcc_enet >> RTnet: registered rteth0 >> rteth0: FCC ENET Version 0.3, 00:06:70:81:04:29 >> >> ~ $ cat /proc/xenomai/irq >> IRQ CPU0 >> 32: 1 rt_mpc8260_fcc_enet >> 256: 75629 [virtual] >> 259: 2 [virtual] >> >> ... >> ~ $ rtping 10.0.0.4 >> >> ~ $ cat /proc/xenomai/irq >> IRQ CPU0 >> 32: 1 rt_mpc8260_fcc_enet >> 256: 94630 [virtual] >> 259: 3 [virtual] >> >> ~ $ rtping 10.0.0.4 >> >> ~ $ cat /proc/xenomai/irq >> IRQ CPU0 >> 32: 1 rt_mpc8260_fcc_enet >> 256: 94630 [virtual] >> 259: 4 [virtual] >> >> ..... > > Looks like an IRQ re-enabling problem. I recall Philippe recently fixing > such a thing... Here it is [1].
Does your ISR now return RTDM_IRQ_HANDLED instead of IRQ_HANDLED? Wolfgang. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
