Re: [usb-storage] Re: usb disk recognized but fails
You were right; that driver caused the problem. Matthieu Castet wrote the Cypress-ATACB driver, so maybe he can help. As shown above, this device matches the last entry in the unusual_cypress.h file (the one named Super Top). Not shown here is the bcdDevice value, which is 0x0150. Should the bcdDevice range for that unusual_devs entry be restricted to just 0x0219? Milan, the patch below should prevent the Cypress-ATACB driver from binding to your device. With this change, the original kernel config should work. Alan Stern Index: usb-3.13/drivers/usb/storage/unusual_cypress.h === --- usb-3.13.orig/drivers/usb/storage/unusual_cypress.h +++ usb-3.13/drivers/usb/storage/unusual_cypress.h @@ -31,7 +31,7 @@ UNUSUAL_DEV( 0x04b4, 0x6831, 0x, 0x Cypress ISD-300LP, USB_SC_CYP_ATACB, USB_PR_DEVICE, NULL, 0), -UNUSUAL_DEV( 0x14cd, 0x6116, 0x, 0x0219, +UNUSUAL_DEV( 0x14cd, 0x6116, 0x0219, 0x0219, Super Top, USB 2.0 SATA BRIDGE, USB_SC_CYP_ATACB, USB_PR_DEVICE, NULL, 0), This patch works. Looking forward to have it included in the master. Thanks for your help, Milan Svoboda -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [usb-storage] Re: usb disk recognized but fails
Whoaa!! I recompiled the master again, but now with a little bit modified configuration, mainly I disabled the CONFIG_USB_STORAGE_CYPRESS_ATACB and it works like a charm! Disk is properly and immediately detected and works! I also tried to boot to standard kernel and disable loading ums_cypress by putting it on the blacklist but it didn't worked out. The disk wasn't detected at all (no message about plug-in event nor report about disk size). I strongly belive that it is Linux kernel problem, not the disk's (apart it might need some quirks). If I remember correctly there hasn't been the ums_cypress from the begining, right? So, perhaps the time when it was added corresponds with the time when it worked for me last time. Best regards and thanks for all your help and wish for a quick fix in the mainstream, Milan Svoboda --- .config.old 2014-01-23 12:57:17.831854511 +0100 +++ .config 2014-01-23 10:13:20.899234729 +0100 @@ -1,6 +1,6 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 3.12.8-1 Kernel Configuration +# Linux/x86 3.13.0 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y @@ -39,7 +39,6 @@ CONFIG_HAVE_INTEL_TXT=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11 -CONFIG_ARCH_CPU_PROBE_RELEASE=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config CONFIG_IRQ_WORK=y @@ -76,7 +75,6 @@ CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y -CONFIG_AUDIT_LOGINUID_IMMUTABLE=y # # IRQ subsystem @@ -143,6 +141,7 @@ CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=19 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y +CONFIG_ARCH_SUPPORTS_INT128=y CONFIG_ARCH_WANTS_PROT_NUMA_PROT_NONE=y CONFIG_ARCH_USES_NUMA_PROT_NONE=y CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y @@ -167,7 +166,7 @@ CONFIG_CFS_BANDWIDTH=y CONFIG_RT_GROUP_SCHED=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set -CONFIG_CHECKPOINT_RESTORE=y +# CONFIG_CHECKPOINT_RESTORE is not set CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y @@ -247,7 +246,6 @@ CONFIG_HAVE_OPTPROBES=y CONFIG_HAVE_KPROBES_ON_FTRACE=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y -CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y @@ -266,11 +264,18 @@ CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSIO CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_SECCOMP_FILTER=y +CONFIG_HAVE_CC_STACKPROTECTOR=y +# CONFIG_CC_STACKPROTECTOR is not set +CONFIG_CC_STACKPROTECTOR_NONE=y +# CONFIG_CC_STACKPROTECTOR_REGULAR is not set +# CONFIG_CC_STACKPROTECTOR_STRONG is not set CONFIG_HAVE_CONTEXT_TRACKING=y +CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_SOFT_DIRTY=y CONFIG_MODULES_USE_ELF_RELA=y +CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_COMPAT_OLD_SIGACTION=y @@ -282,6 +287,7 @@ CONFIG_COMPAT_OLD_SIGACTION=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 +# CONFIG_SYSTEM_TRUSTED_KEYRING is not set CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y @@ -453,6 +459,7 @@ CONFIG_MEMORY_HOTPLUG_SPARSE=y CONFIG_MEMORY_HOTREMOVE=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 +CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_BALLOON_COMPACTION=y CONFIG_COMPACTION=y CONFIG_MIGRATION=y @@ -475,7 +482,6 @@ CONFIG_FRONTSWAP=y # CONFIG_CMA is not set CONFIG_ZBUD=y CONFIG_ZSWAP=y -CONFIG_MEM_SOFT_DIRTY=y CONFIG_X86_CHECK_BIOS_CORRUPTION=y CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y CONFIG_X86_RESERVE_LOW=64 @@ -490,7 +496,6 @@ CONFIG_X86_SMAP=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_SECCOMP=y -CONFIG_CC_STACKPROTECTOR=y # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_300=y @@ -533,13 +538,13 @@ CONFIG_PM_DEBUG=y CONFIG_PM_ADVANCED_DEBUG=y # CONFIG_PM_TEST_SUSPEND is not set CONFIG_PM_SLEEP_DEBUG=y +# CONFIG_DPM_WATCHDOG is not set CONFIG_PM_TRACE=y CONFIG_PM_TRACE_RTC=y # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y # CONFIG_ACPI_PROCFS is not set -# CONFIG_ACPI_PROCFS_POWER is not set CONFIG_ACPI_EC_DEBUGFS=m CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m @@ -555,7 +560,6 @@ CONFIG_ACPI_THERMAL=m CONFIG_ACPI_NUMA=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_INITRD_TABLE_OVERRIDE=y -CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_X86_PM_TIMER=y @@ -571,13 +575,13 @@ CONFIG_ACPI_APEI_PCIEAER=y CONFIG_ACPI_APEI_MEMORY_FAILURE=y CONFIG_ACPI_APEI_EINJ=m CONFIG_ACPI_APEI_ERST_DEBUG=m +# CONFIG_ACPI_EXTLOG is not set CONFIG_SFI=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y -CONFIG_CPU_FREQ_TABLE=y
Re: [usb-storage] Re: usb disk recognized but fails
8801fdbb2c00 2290129737 S Bo:3:004:2 -115 31 = 55534243 5f00
0010 8a28 004a856e af08 00
8801fdbb2c00 2290129782 C Bo:3:004:2 0 31
8800d4a51b40 2290129803 S Bi:3:004:1 -115 4096
8800d4a51b40 2301288990 C Bi:3:004:1 -32 512 =
8801fdbb2c00 2301289039 S Co:3:004:0 s 02 01 0081 0
8801fdbb2c00 2301289068 C Co:3:004:0 0 0
8801fdbb2c00 2301289086 S Bi:3:004:1 -115 13
8801fdbb2c00 2301289153 C Bi:3:004:1 0 13 = 55534253 5f00 01
8801fdbb2c00 2301289189 S Bo:3:004:2 -115 31 = 55534243 6000
1200 8603 0012 00
8801fdbb2c00 2301289223 C Bo:3:004:2 0 31
8800d188c780 2301289263 S Bi:3:004:1 -115 18
8800d188c780 2301299693 C Bi:3:004:1 0 18 = 7000 000a
8801fdbb2c00 2301299741 S Bi:3:004:1 -115 13
8801fdbb2c00 2301299765 C Bi:3:004:1 0 13 = 55534253 6000 00
This continued a few more times until the computer gave up. Maybe
there is something wrong with one particular block at that address on
the disk.
I tried to run fdisk /dev/sdb which obivously failed but it tried to access
sectors 0, 1, 2, 3 which resulted in kernel log
messages reporting invalid sectors.
I tried to connect the disk with Windows and it was connected immediatelly, the
partition is visible, I can read files, create files...
No signs of problems visible...
I don't know if it tells anything, but Windows reports the disk as USB 2.0 SATA
bridge even when connected to USB-3 ports.
Do you have a USB-2 port on the computer you can plug the disk into,
instead of USB-3?
I tried it, but it is only one and separated on the other side of laptop so I
could connect only one connector and the
result is the same.
Milan Svoboda
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb disk recognized but fails
Non-working: 3.12.7-2-ARCH #1 SMP PREEMPT Sun Jan 12 13:09:09 CET 2014 x86_64 GNU/Linux I'm sorry, I don't remember exactly which version worked, I have had the disk connected to TV for a long time and only recently I wanted to copy some movies on it. I guess it worked something like 6 or 9 months ago. Milan __ Od: Sarah Sharp sarah.a.sh...@linux.intel.com Komu: Milan Svoboda milan.svob...@centrum.cz Datum: 20.01.2014 19:23 Předmět: Re: usb disk recognized but fails CC: linux-...@vger.kernel.org, USB Storage List usb-stor...@lists.one-eyed-alien.net, linux-scsi@vger.kernel.org Cc-ing the USB storage list, in case this device needs some quirk. On Wed, Jan 15, 2014 at 03:47:39PM +0100, Milan Svoboda wrote: The SATA adapter has a power input, but it is not used, it is connected to the PC with Y-type USB cable. The disk works with my smart TV, it works with Windows on the same machine, it also had worked some time ago with Linux, but now it shows the following: Do you know which kernel version it worked with? What version are you currently running? Please run `uname -a`. [ 2192.027213] usb 1-3: new high-speed USB device number 5 using xhci_hcd [ 2192.042323] ums-cypress 1-3:1.0: USB Mass Storage device detected [ 2192.042500] scsi9 : usb-storage 1-3:1.0 [ 2193.044219] scsi 9:0:0:0: Direct-Access WDC WD64 00BPVT-00HXZT0 PQ: 0 ANSI: 0 [ 2193.045083] sd 9:0:0:0: [sdb] 1250263728 512-byte logical blocks: (640 GB/596 GiB) [ 2193.045240] sd 9:0:0:0: [sdb] Write Protect is off [ 2193.045245] sd 9:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 2193.045384] sd 9:0:0:0: [sdb] No Caching mode page found [ 2193.045388] sd 9:0:0:0: [sdb] Assuming drive cache: write through [ 2193.046259] sd 9:0:0:0: [sdb] No Caching mode page found [ 2193.046264] sd 9:0:0:0: [sdb] Assuming drive cache: write through [ 2193.054389] sdb: sdb1 [ 2193.055092] sd 9:0:0:0: [sdb] No Caching mode page found [ 2193.055095] sd 9:0:0:0: [sdb] Assuming drive cache: write through [ 2193.055098] sd 9:0:0:0: [sdb] Attached SCSI disk [ 2200.821345] usb 1-3: reset high-speed USB device number 5 using xhci_hcd [ 2200.835063] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800bc71e480 [ 2200.835068] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800bc71e4c0 [ 2267.897715] sd 9:0:0:0: [sdb] Unhandled sense code [ 2267.897719] sd 9:0:0:0: [sdb] [ 2267.897721] Result: hostbyte=0x07 driverbyte=0x08 [ 2267.897722] sd 9:0:0:0: [sdb] [ 2267.897724] Sense Key : 0x4 [current] [ 2267.897735] sd 9:0:0:0: [sdb] [ 2267.897736] ASC=0x0 ASCQ=0x0 [ 2267.897738] sd 9:0:0:0: [sdb] CDB: [ 2267.897740] cdb[0]=0x28: 28 00 4a 85 6e af 00 00 08 00 [ 2267.897746] end_request: I/O error, dev sdb, sector 1250258607 [ 2267.897750] Buffer I/O error on device sdb1, logical block 625129272 [ 2267.897752] Buffer I/O error on device sdb1, logical block 625129273 [ 2267.897753] Buffer I/O error on device sdb1, logical block 625129274 [ 2267.897754] Buffer I/O error on device sdb1, logical block 625129275 [ 2270.884154] usb 1-3: USB disconnect, device number 5 Bus 001 Device 010: ID 14cd:6116 Super Top M6116 SATA Bridge Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x14cd Super Top idProduct 0x6116 M6116 SATA Bridge bcdDevice1.50 iManufacturer 1 Super Top iProduct3 USB 2.0 SATA BRIDGE iSerial 2 M6116018VE15 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02
