CanBus Failing during printing "Got error -1 in can write"

General Discussion
1

Basic Information:

Printer Model: Voron 2.4r2
MCU / Printerboard:

  • Raspberry PI 3B+
  • Serial Octopus V1.1
  • USB to CanBus BTT U2C (stock firmware)
    • BTT SB2040 (latest klipper commits)
      klippy.log

Describe your issue:

I am randomly seeing CAN Bus socket get closed/shutdown in klipper, klipper is failing with

b’Got error -1 in can write: (11)Resource temporarily unavailable’

The actual CAN interface seems fine,

3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/can promiscuity 0 allmulti 0 minmtu 0 maxmtu 0
can state ERROR-ACTIVE restart-ms 0
bitrate 1000000 sample-point 0.750
tq 62 prop-seg 5 phase-seg1 6 phase-seg2 4 sjw 1 brp 3
gs_usb: tseg1 1…16 tseg2 1…8 sjw 1…4 brp 1…1024 brp_inc 1
clock 48000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 0 0 0 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 parentbus usb parentdev 1-1.1.2:1.0
RX: bytes packets errors dropped missed mcast
4293699 662508 0 0 0 0
TX: bytes packets errors dropped carrier collsns
7695728 1040255 0 0 0 0
root@octoprint:/var/log/klippy#
klippy.log (7.9 MB)

2

Just started seeing these errors in my syslog,

Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 3
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 4
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 1
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 1
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 5
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 2
Apr 25 11:34:56 octoprint.local kernel:
Apr 25 11:34:56 octoprint.local kernel: WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 7
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: USB disconnect, device number 8
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: new full-speed USB device number 9 using dwc_otg
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: Product: stm32f446xx
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: Manufacturer: Klipper
Apr 25 11:34:56 octoprint.local kernel: usb 1-1.2: SerialNumber: 190045001850344D30353320

3

Rebooting back into 32 bit kernel seems to resolve this issue, I haven’t seen an error since I rebooted.

fingers crossed
knock on wood

1 Like