usb autosuspend

[mbauhardt]

Hi,
i'm using arch linux arm on my raspberry pi model b.
i have an external hdd and two other hdd disks bundled in a software raid connected via usb.

sometimes it happen that my disks going not into sleep mode. when i want to check the status of my disk via hdparm i get the following message.

$this->bbcode_second_pass_code('', '
hdparm -C /dev/sda
/dev/sda: No such file or directory
')

$this->bbcode_second_pass_code('', '
ls /mnt/foo
ls: das Verzeichnis /mnt/foo wird gelesen: Eingabe-/Ausgabefehler
')

dmesg give me the following message
$this->bbcode_second_pass_code('', '
[79286.351587] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2
[79286.351851] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2
[79286.417588] ieee80211 phy0: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[79287.582035] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2
[79287.582135] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2
[79287.582163] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2
[79287.653713] ieee80211 phy0: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[79288.911604] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[79288.911734] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[79288.911764] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 10 in queue 2
[79288.911881] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2
[79288.974636] ieee80211 phy0: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[79288.974680] ieee80211 phy0: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
[79612.531524] EXT4-fs warning (device sda1): __ext4_read_dirblock:908: error reading directory block (ino 2, block 0)
[79622.287788] EXT4-fs warning (device md0): __ext4_read_dirblock:908: error reading directory block (ino 2, block 0)
')

After some googling i found some blog and forum entries about usb suspend mode. but i can't find any config file or so which is related to usb suspend.


Has someone similar experience?
Thanks, Marko

[Mikelevel]

Something similar here and this works for me...

In /usr/share/polkit-1/actions/org.freedesktop.upower.policy

There are two sections in this file, the first for suspend and the second for hibernate. Near the end of each section will be a line with:

<allow_active>yes</allow_active>
Change this entry from “yes” to “no” to disable hibernate/suspend.
<allow_active>no</allow_active>

[mbauhardt]

i have no file called org.freedesktop.upower.policy

$this->bbcode_second_pass_code('', '
ls /usr/share/polkit-1/actions/*
/usr/share/polkit-1/actions/org.freedesktop.color.policy /usr/share/polkit-1/actions/org.freedesktop.policykit.examples.pkexec.policy
/usr/share/polkit-1/actions/org.freedesktop.hostname1.policy /usr/share/polkit-1/actions/org.freedesktop.policykit.policy
/usr/share/polkit-1/actions/org.freedesktop.locale1.policy /usr/share/polkit-1/actions/org.freedesktop.systemd1.policy
/usr/share/polkit-1/actions/org.freedesktop.login1.policy /usr/share/polkit-1/actions/org.freedesktop.timedate1.policy
')

i thought i have to change files in
$this->bbcode_second_pass_code('', '/sys/module/usbcore or /sys/module/usb_storage') or so

[mbauhardt]

I'm pretty sure that this issue is not arch related. i guess that my powered usb switch has not enough power. maybe when all 3 disks waking up from spin down. because is see a usb disconnect in the logfile

$this->bbcode_second_pass_code('', '
Dec 18 06:31:32 raspberry kernel: [69702.589201] usb 1-1.3.4.4: USB disconnect, device number 14
Dec 18 06:31:32 raspberry kernel: [69702.602560] scsi 2:0:0:0: rejecting I/O to offline device
Dec 18 06:31:32 raspberry kernel: [69702.602602] scsi 2:0:0:0: [sdc] killing request
Dec 18 06:31:32 raspberry kernel: [69702.602699] scsi 2:0:0:0: [sdc] Unhandled error code
Dec 18 06:31:32 raspberry kernel: [69702.602724] scsi 2:0:0:0: [sdc]
Dec 18 06:31:32 raspberry kernel: [69702.602740] Result: hostbyte=0x01 driverbyte=0x00
Dec 18 06:31:32 raspberry kernel: [69702.602756] scsi 2:0:0:0: [sdc] CDB:
Dec 18 06:31:32 raspberry kernel: [69702.602769] cdb[0]=0x2a: 2a 00 00 00 08 10 00 00 05 00
Dec 18 06:31:32 raspberry kernel: [69702.602824] end_request: I/O error, dev sdc, sector 2064
Dec 18 06:31:32 raspberry kernel: [69702.602842] md: super_written gets error=-5, uptodate=0
Dec 18 06:31:32 raspberry kernel: [69702.602865] md/raid1:md0: Disk failure on sdc1, disabling device.
Dec 18 06:31:32 raspberry kernel: [69702.602865] md/raid1:md0: Operation continuing on 1 devices.
Dec 18 06:31:32 raspberry kernel: [69702.726312] sd 0:0:0:0: [sda] Unhandled error code
Dec 18 06:31:32 raspberry kernel: [69702.726352] sd 0:0:0:0: [sda]
....
')

[Mikelevel]

any news about this?

[mbauhardt]

I don't had this issue again. so i can resolve this issue as clarified or so.