- Posts: 393
- Thank you received: 0
5i20 request for help, machine at client
8 years 9 months ago #104836
by emcPT
5i20 request for help, machine at client was created by emcPT
Hello,
I have a machine at a foreign country using a 5i20 + 7i73 connected though a 7i44 , working for about 2 years.
A problem started with the incapability of seeing the 7i73. I sold another board and the problem went away. Soon after (maybe 1 day after) the client now complains that he cannot start linuxcnc. With the following error (debug file information and dsmeg).
A reboot does not solve the issue and remotely I checked that the kernel is rtai.
Any information is appreciated as the client is top priority to me.
Debug file information:
insmod: error inserting '/home/mastor/linuxcnc-dev/rtlib/hm2_pci.ko': -1 Invalid parameters
Okuma.hal:11: exit value: 1
Okuma.hal:11: insmod failed, returned -1
See the output of 'dmesg' for more information.
2225
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
dmesg
I-pipe: head domain RTAI registered.
RTAI[hal]: compiled with gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .
RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
SYSINFO: CPUs 2, LINUX APIC IRQ 2312, TIM_FREQ 12479046, CLK_FREQ 1597066000, CPU_FREQ 1597066000
RTAI_APIC_TIMER_IPI: RTAI DEFINED 2314, VECTOR 2314; LINUX_APIC_TIMER_IPI: RTAI DEFINED 2312, VECTOR 2312
TIMER NAME: lapic; VARIOUSLY FOUND APIC FREQs: 12479046, 12479046, 12230000
RTAI[malloc]: global heap size = 131072 bytes, <BSD>.
, <uses LINUX SYSCALLs>, kstacks pool size = 524288 bytes.
RTAI[sched]: hard timer type/freq = APIC/12479046(Hz); default timing: periodic; linear timed lists.
RTAI[sched]: Linux timer freq = 1000 (Hz), TimeBase freq = 1597066000 hz.
RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
***** WARNING: GLOBAL HEAP NEITHER SHARABLE NOR USABLE FROM USER SPACE (use the vmalloc option for RTAI malloc) *****
RTAI[math]: loaded.
hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci 0000:01:06.0: enabling device (0000 -> 0003)
hm2_pci: discovered 5i20 at 0000:01:06.0
hm2/hm2_5i20.0: hm2_sserial_waitfor: Timeout (1007mS) waiting for addr 5a00 &mask ffffffff val 1
hm2/hm2_5i20.0: DATA addr 5b00 after timeout: 0
hm2/hm2_5i20.0: failed to parse Module Descriptor 4
hm2_5i20.0: board fails HM2 registration
hm2_pci: probe of 0000:01:06.0 failed with error -22
hm2: unloading
RTAI[math]: unloaded.
RTAI[malloc]: unloaded.
RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
I-pipe: head domain RTAI unregistered.
RTAI[hal]: unmounted.
I have a machine at a foreign country using a 5i20 + 7i73 connected though a 7i44 , working for about 2 years.
A problem started with the incapability of seeing the 7i73. I sold another board and the problem went away. Soon after (maybe 1 day after) the client now complains that he cannot start linuxcnc. With the following error (debug file information and dsmeg).
A reboot does not solve the issue and remotely I checked that the kernel is rtai.
Any information is appreciated as the client is top priority to me.
Debug file information:
insmod: error inserting '/home/mastor/linuxcnc-dev/rtlib/hm2_pci.ko': -1 Invalid parameters
Okuma.hal:11: exit value: 1
Okuma.hal:11: insmod failed, returned -1
See the output of 'dmesg' for more information.
2225
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
dmesg
I-pipe: head domain RTAI registered.
RTAI[hal]: compiled with gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .
RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
SYSINFO: CPUs 2, LINUX APIC IRQ 2312, TIM_FREQ 12479046, CLK_FREQ 1597066000, CPU_FREQ 1597066000
RTAI_APIC_TIMER_IPI: RTAI DEFINED 2314, VECTOR 2314; LINUX_APIC_TIMER_IPI: RTAI DEFINED 2312, VECTOR 2312
TIMER NAME: lapic; VARIOUSLY FOUND APIC FREQs: 12479046, 12479046, 12230000
RTAI[malloc]: global heap size = 131072 bytes, <BSD>.
, <uses LINUX SYSCALLs>, kstacks pool size = 524288 bytes.
RTAI[sched]: hard timer type/freq = APIC/12479046(Hz); default timing: periodic; linear timed lists.
RTAI[sched]: Linux timer freq = 1000 (Hz), TimeBase freq = 1597066000 hz.
RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
***** WARNING: GLOBAL HEAP NEITHER SHARABLE NOR USABLE FROM USER SPACE (use the vmalloc option for RTAI malloc) *****
RTAI[math]: loaded.
hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci 0000:01:06.0: enabling device (0000 -> 0003)
hm2_pci: discovered 5i20 at 0000:01:06.0
hm2/hm2_5i20.0: hm2_sserial_waitfor: Timeout (1007mS) waiting for addr 5a00 &mask ffffffff val 1
hm2/hm2_5i20.0: DATA addr 5b00 after timeout: 0
hm2/hm2_5i20.0: failed to parse Module Descriptor 4
hm2_5i20.0: board fails HM2 registration
hm2_pci: probe of 0000:01:06.0 failed with error -22
hm2: unloading
RTAI[math]: unloaded.
RTAI[malloc]: unloaded.
RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
I-pipe: head domain RTAI unregistered.
RTAI[hal]: unmounted.
Please Log in to join the conversation.
8 years 9 months ago #104838
by rodw
Replied by rodw on topic 5i20 request for help, machine at client
I can't help much but this thread reported the same (or similar) error very recently (see PCW on page 2).
forum.linuxcnc.org/30-cnc-machines/33806...ak-down?limitstart=0
So it seems it might have been caused by another cable chewing mouse!
forum.linuxcnc.org/30-cnc-machines/33806...ak-down?limitstart=0
So it seems it might have been caused by another cable chewing mouse!
Please Log in to join the conversation.
8 years 9 months ago #104844
by PCW
Replied by PCW on topic 5i20 request for help, machine at client
Sort of hard to say but in this case I would suspect the Host PC
The error is very uncommon and suggests a PCI interface problem of some kind.
A simply missing/non communicative 7I73 would not cause a low level error,
it would cause an error later when its hal pins were found missing.
The error is very uncommon and suggests a PCI interface problem of some kind.
A simply missing/non communicative 7I73 would not cause a low level error,
it would cause an error later when its hal pins were found missing.
Please Log in to join the conversation.
8 years 9 months ago #104846
by emcPT
Replied by emcPT on topic 5i20 request for help, machine at client
Thank you,
Lets see what will come up. Since the client changed the wires/touched the wiring to change the faulty 7i73, maybe some bad connection also happened.
Thank you
Lets see what will come up. Since the client changed the wires/touched the wiring to change the faulty 7i73, maybe some bad connection also happened.
Thank you
Please Log in to join the conversation.
Time to create page: 0.073 seconds
