castalla wrote:
> I was wondering whether it's worth trying a powered hub setup? I could
> probably get one tomorrow & return if no success.
With the exception of one old PSU - my drives work OK with an external
PSU on one branch of the Y cable.
In the case of failures - the dmesg log always have an "over-current" or
similar message .
If you don't get the "over-current" type message - then I think the
issues is not PSU related.
What I did notice in dmesg logs yesterday was these "under-voltage"
messages which say the PI PSU is under-strains. I don''t get these
messages my PSU is an official Pi rated 2.5A
Code:
--------------------
[ 32.249034] Voltage normalised (0x00080008)
[ 34.329116] Under-voltage detected! (0x000d0005)
[ 38.489227] Voltage normalised (0x00080008)
[ 51.898103] Finished piCorePlayer v8.1.0 startup.
[ 193.410948] dwc_otg 3f980000.usb: dev 1.3 ep1in scatterlist error -121/-121
[ 254.048982] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 254.186181] dwc_otg 3f980000.usb: dev 1.3 ep1in scatterlist error -121/-121
[ 315.488983] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 315.625328] dwc_otg 3f980000.usb: dev 1.3 ep1in scatterlist error -121/-121
[ 376.928992] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 377.075960] dwc_otg 3f980000.usb: dev 1.3 ep1in scatterlist error -121/-121
[ 377.529030] Under-voltage detected! (0x00050005)
[ 381.689044] Voltage normalised (0x00000000)
[ 438.368995] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
--------------------
I also have decoded the output from cdda2wav below. These message
indicate Read errors but I think they are not consecutive - it means
there may be successful ones in between or they are overlapped reads
(need to find a way to disable overlapped reads) . Not sure what this
actually means except perhaps CPU loads or USB Bus activity (shared with
network) may be a factor. With power issues, the command is delayed
with short time delay and is retried and usually succeeds. Your errors
are always 60se c delay and seem to always fail.
Code:
--------------------
0%Errno: 5 (Input/output error), ReadCD MMC 12 scsi sendcmd: cmd timeout
after 61.439 (60) s
CDB: BE 04 00 00 00 21 00 00 34 10 00 00
resid: 122290
cmd finished after 61.439s timeout 60s
0%Errno: 5 (Input/output error), ReadCD MMC 12 scsi sendcmd: cmd timeout
after 61.440 (60) s
CDB: BE 04 00 00 00 55 00 00 34 10 00 00
resid: 122290
cmd finished after 61.440s timeout 60s
--------------------
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=47288
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
