Jump to content
Ultimaker Community of 3D Printing Experts
sthacher

UM3 Failed prints

Recommended Posts

I'm having issues with a print that keeps failing a few hours into a ~26hr print. I sliced with cura 2.5 stable, the first attempt was sent over network to the UM3. I used a USB drive for the second attempt failed but in a different location.

Printer Firmware : 3.6.90.20170411

 

Apr 22 22:39:52 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:39:52,545 INFO     nfcPrinterHotendInfo PrintCore 1 extruded 10.155390000000011 mm in 19.106929625002522, remaining length = 15793.194245488805 mm, stat record usage duration: 62574.127667849054Apr 22 22:39:52 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:39:52,546 INFO     nfcController   Queueing tag for hotend 1, tag: , record: Apr 22 22:40:21 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:40:21,521 INFO     nfcPrinterHotendInfo PrintCore 1 extruded 10.363679999999988 mm in 2.801614937990962, remaining length = 15782.830565488804 mm, stat record usage duration: 62574.127667849054Apr 22 22:40:21 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:40:21,527 INFO     nfcController   Queueing tag for hotend 1, tag: , record: Apr 22 22:41:04 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:41:04,225 INFO     nfcPrinterHotendInfo PrintCore 1 extruded 10.027229999999975 mm in 36.13182920499821, remaining length = 15772.803335488807 mm, stat record usage duration: 62574.127667849054Apr 22 22:41:04 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:41:04,229 INFO     nfcController   Queueing tag for hotend 1, tag: , record: Apr 22 22:41:20 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:41:20,867 INFO     nfcPrinterHotendInfo PrintCore 1 extruded 10.018940000000043 mm in 15.204076590001932, remaining length = 15762.784395488805 mm, stat record usage duration: 62574.127667849054Apr 22 22:41:20 ultimakersystem-ccbdd3000ccc python3.4[372]: 2017-04-22 22:41:20,868 INFO     nfcController   Queueing tag for hotend 1, tag: , record: Apr 22 22:41:23 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:23 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10469 callbacks suppressedApr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:29 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10476 callbacks suppressedApr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:34 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10475 callbacks suppressedApr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:39 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10475 callbacks suppressedApr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:44 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: INFO: rcu_sched self-detected stall on CPUApr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel:         0-...: (1 GPs behind) idle=8ed/140000000000002/0 softirq=258686/258687 fqs=1000Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel:          (t=2100 jiffies g=65597 c=65596 q=6)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: Task dump for CPU 0:Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: python3.4       R  running task        0   365      1 0x00000002Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (unwind_backtrace) from [] (show_stack+0xb/0xc)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (show_stack) from [] (rcu_dump_cpu_stacks+0x5b/0x80)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (rcu_dump_cpu_stacks) from [] (rcu_check_callbacks+0x56d/0x6b8)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (rcu_check_callbacks) from [] (update_process_times+0x23/0x48)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (update_process_times) from [] (tick_sched_timer+0x31/0x5c)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (tick_sched_timer) from [] (__hrtimer_run_queues+0xc3/0x114)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (__hrtimer_run_queues) from [] (hrtimer_interrupt+0x87/0x180)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (hrtimer_interrupt) from [] (arch_timer_handler_phys+0x1f/0x24)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (arch_timer_handler_phys) from [] (handle_percpu_devid_irq+0x47/0xd4)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (handle_percpu_devid_irq) from [] (generic_handle_irq+0x17/0x20)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (generic_handle_irq) from [] (__handle_domain_irq+0x3f/0x80)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (__handle_domain_irq) from [] (gic_handle_irq+0x3b/0x70)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: [] (gic_handle_irq) from [] (__irq_svc+0x65/0x94)Apr 22 22:41:45 ultimakersystem-ccbdd3000ccc kernel: Exception stack(0xe72dde80 to 0xe72ddec8)Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: dfa0:                                     00000000 00000001 00318f98 00000000Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: dfc0: 00318848 00000000 a24ff930 003dd468 a24f5298 a24f529c 0000000b 002b0cd8Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: dfe0: 002b02d8 a24f5218 00126997 001269a0 600f0030 ffffffffApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 9928 callbacks suppressedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10475 callbacks suppressedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10475 callbacks suppressedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10475 callbacks suppressedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250_interrupt: 10476 callbacks suppressedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc kernel: serial8250: too much work for irq48Apr 22 22:45:39 ultimakersystem-ccbdd3000ccc systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd-journal[114]: Journal stoppedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd-journal[11875]: Permanent journal is using 59.8M (max allowed 47.8M, trying to leave 71.7M free of 59.1M available → current limit 59.8M).Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd-journald[114]: Received SIGTERM from PID 1 (systemd).Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Unit systemd-journald.service entered failed state.Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Stopping Journal Service...Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Starting Journal Service...Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Started Journal Service.Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd-journal[11875]: Journal startedApr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...Apr 22 22:46:24 ultimakersystem-ccbdd3000ccc systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.

 

Share this post


Link to post
Share on other sites

Ah ok, so not a printing issue but I guess a hardware issue.

Really not an expert here but my guess maybe some communication issue between the main board and the olimex controller board?

Did it print ok before?

Beside getting in contact with your re-seller to solve the issue for you, you could have a look if all cables and connectors are properly seated. If you decide to have a look yourself be careful with the Olimex board and static electricity....

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!