Jump to content

Redwid

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Thanks tkaiser, as usual you provide a quite valubale answer. Do you believe that disconnects issue could be related to this one: https://github.com/rockchip-linux/kernel/issues/34
  2. Is it possible to prove that? Let's say log voltage or measure something during copy operation? Is there any threshold before which usb host goes off?
  3. I do have a setup: 2.5" disks connected to the powered USB 3.0 hub. The power adapter is 10A. If I do start rsync copy from one disk to another after a while I'm getting the error: rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] All disks disappired. There is no way to return them back, only reboot helps. In dmesg I could find that device jsut stopped and disappired: [ 2342.927583] usb 5-1.1: USB disconnect, device number 3 [ 2342.931057] usb 4-1: USB disconnect, device number 2 [ 2342.931975] usb 5-1: USB disconnect, device number 2 [ 2345.629932] usb 5-1.3: USB disconnect, device number 4 [ 2345.663838] usb 5-1.4: USB disconnect, device number 5 [ 2342.904003] xhci-hcd xhci-hcd.9.auto: xHCI host not responding to stop endpoint command. [ 2342.904016] xhci-hcd xhci-hcd.9.auto: Assuming host is dying, halting host. [ 2342.927380] xhci-hcd xhci-hcd.9.auto: Host not halted after 16000 microseconds. [ 2342.927400] xhci-hcd xhci-hcd.9.auto: Non-responsive xHCI host is not halting. [ 2342.927416] xhci-hcd xhci-hcd.9.auto: Completing active URBs anyway. [ 2342.927502] xhci-hcd xhci-hcd.9.auto: HC died; cleaning up [ 2342.927543] xhci-hcd xhci-hcd.9.auto: xHCI host not responding to stop endpoint command. [ 2342.927552] xhci-hcd xhci-hcd.9.auto: Assuming host is dying, halting host. [ 2342.930928] xhci-hcd xhci-hcd.9.auto: HC died; cleaning up Any ideas? How to find the reason of this crash?
  4. Is linux-u-boot-bananapipro-next was introduced recently? I'm trying to find out when I've made that mistake.
  5. Thanks guys for a quick response. My /proc/device-tree/model LeMaker Banana Pro After changing boot image to linux-u-boot-bananapipro-next my disk is came online: [ 3.699424] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off CAP_PMP [ 3.699478] ahci-sunxi 1c18000.sata: SSS flag set, parallel bus scan disabled [ 3.699513] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode [ 3.699527] ahci-sunxi 1c18000.sata: flags: ncq sntf stag pm led clo only pio slum part ccc [ 3.701338] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 33 [ 4.031019] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 4.361298] ata1.00: ATA-8: ST9500325AS, 0001SDM1, max UDMA/133 [ 4.361309] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 4.416053] ata1.00: configured for UDMA/133 [ 4.416949] scsi 0:0:0:0: Direct-Access ATA ST9500325AS SDM1 PQ: 0 ANSI: 5 lsblk (sda - was missed before): NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:16 0 232.9G 0 disk `-sdb1 8:17 0 232.9G 0 part /media/93f700b5-6ce7-4e6d-94bf-4e754f3ce685 sda 8:0 0 465.8G 0 disk `-sda1 8:1 0 465.8G 0 part /media/07baa8b0-2190-4369-b605-06f165d73d5a mmcblk0 179:0 0 29.8G 0 disk `-mmcblk0p1 179:1 0 29.8G 0 part /
  6. SATA worked for me on 5.01, but I've suddenly upgraded to 5.23. And now now SATA :-( root@bananapro ~ # dmesg|grep -i ata [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Memory: 1004820K/1046952K available (10240K kernel code, 703K rwdata, 2008K rodata, 1024K init, 308K bss, 25748K reserved, 16384K cma-reserved, 244136K highmem) [ 0.000000] .data : 0xc0f00000 - 0xc0faffcc ( 704 kB) [ 3.296350] libata version 3.00 loaded. [ 3.659655] ahci-sunxi 1c18000.sata: PHY power up failed. [ 3.659733] ahci-sunxi: probe of 1c18000.sata failed with error -5 [ 4.985443] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 19.382006] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,acl Unfortunately there are no 5.01 anymore root@bananapro ~ # apt-get install linux-u-boot-bananapi-next=5.01 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '5.01' for 'linux-u-boot-bananapi-next' was not found My armbian version: root@bananapro ~ # uname -a Linux bananapro 4.8.4-sunxi #6 SMP Sun Oct 23 15:55:47 CEST 2016 armv7l GNU/Linux I've tested on bananian 16.04 and SATA works there. Does anybody has any idea how to get linux-u-boot-bananapi-next=5.01? Or any other methods to return back SATA?
  7. That happened for my banana pro again for linux-u-boot-bananapi-next version 5.16 [ 3.592900] ahci-sunxi 1c18000.sata: PHY power up failed. [ 3.592980] ahci-sunxi: probe of 1c18000.sata failed with error -5 Downgrading to 5.01 works fine. apt-get install linux-u-boot-bananapi-next=5.01 For some reason 5.04 not found right now: apt-get install linux-u-boot-bananapi-next=5.04 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '5.04' for 'linux-u-boot-bananapi-next' was not found Looks like regression in the configuration.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines