Author

Topic: Raspberry PI + Stickminer : dmesg error report - WARN::dwc_otg_hcd_urb_dequeue.. (Read 65 times)

member
Activity: 163
Merit: 57
Beam me up Scotty
Which Pi?
1, 2, or 3, 3B, 3B+? Orange Pi?


Only Raspberry PI series and only when using the stock Raspberry PI 64bit OS, it doesn't seem to happen on the 32bit version of the OS.

I've tested on Raspberry PI 3B, 3B+, 4B and Zero 2W.

Each show the error when using the 64bit OS.

Orange PI is not related to Raspberry. Completely different vendor, hardware and OS build. I've not tested an Orange PI as I dont have one.

I did try a Pine ROCK64, that worked without any issues.
legendary
Activity: 3738
Merit: 2656
Evil beware: We have waffles!
Which Pi?
1, 2, or 3, 3B, 3B+? Orange Pi?
member
Activity: 163
Merit: 57
Beam me up Scotty
This might help anyone else that is using a Raspberry PI for running a few stick miners, CompacF et'al

Using the stock Raspberry PI 64bit (Bullseye) OS

If you're seeing lots of warnings in dmesg like this :-

Code:
WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 2

That eventually cripple USB performance, this is due to the 64bit driver not fully supporting FIQ (whatever the hell that is!)

See thread here:-

https://github.com/raspberrypi/firmware/issues/1804


By appending the following to the end of /boot/cmdline.txt command line parameters,

Code:
dwc_otg.fiq_enable=0 dwc_otg.fiq_fsm_enable=0

this disables fiq and after a reboot, no more error messages and no more crippled USB performance.


Hopefully it'll help you out too.

It certainly seems to have fixed the problems I was seeing.

Cheers

G.


Additional:-

This change seems to have removed all the sperious PT_NONONCE resets with the CompacF's I was also seeing with CGMiner

Code:
GSF 0 - plateau_type PT_NONONCE \[0] 7676 > 5113.06 (lock=0)

Stability of the rig using this set-up has improved massively since I made this change, average hash rate has marginally improved also.

So anyone using a Raspberry PI with the 64Bit Stock OS. Take a look at dmesg to see if you're suffering the same issue.






Jump to: