Re: usb/185628: usbd_req_re_enumerate set address failed USB_ERR_STALLED for Seagate USB drives between r259425 and r260321

2014-01-10 Thread Alex Goncharov 
The following reply was made to PR usb/185628; it has been noted by GNATS.

From: Alex Goncharov 
To: Hans Petter Selasky ,
  "freebsd-gnats-sub...@freebsd.org" 
Cc:  
Subject: Re: usb/185628: usbd_req_re_enumerate set address failed 
USB_ERR_STALLED for Seagate USB drives between r259425 and r260321
Date: Fri, 10 Jan 2014 19:50:58 -0800 (PST)

 --464114708-874558429-1389412258=:8299
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 I rebuilt the kernel with change 259722 reverted:=0A=0A=A0 ident /boot/kern=
 el.scsi_all-back/kernel | grep /scsi_all.c=0A=A0 =3D>=0A=A0=A0=A0=A0 $FreeB=
 SD: stable/9/sys/cam/scsi/scsi_all.c 257050 2013-10-24 10:34:13Z mav $=0A=
 =0AStill have the same dmesges:=0A=0A-=0Ausbd_req_re_enumerate: addr=3D=
 2, set address failed! (USB_ERR_STALLED, ignored)=0Ausbd_setup_device_desc:=
  getting device descriptor at addr 2 failed, USB_ERR_STALLED=0Ausbd_req_re_=
 enumerate: addr=3D2, set address failed! (USB_ERR_STALLED, ignored)=0Ausbd_=
 setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_STAL=
 LED=0Ausb_alloc_device: Failure selecting configuration index 0:USB_ERR_STA=
 LLED, port 4, addr 2 (ignored)=0Augen5.2:  at usbus5=0A=0A=0AI=
 'll launch another rebuild for the night, after 'svn up' -- maybe something=
  will be discovered.=A0 If anybody has suggestions on debugging the issue, =
 please let me know.=0A=0A-- Alex=0A=0A=0A=0A=0AOn Friday, January 10, 2014 =
 8:08 AM, Hans Petter Selasky  wrote:=0A =0AOn 01/10/14 12:=
 49, Alex Goncharov wrote:=0A>> >If devices simply re-attach either they are=
  not respond and software=0A>> >initiates a reset, which can be disabled by=
  setting=0A>> >"hw.usb.no_cs_fail" or the software in the USB HDD died and=
 =0A>> >rebooted.=0A> May be; but think about the fact correlations: the fac=
 t of the two=0A> system's upgrade, two identical Seagate units, and other H=
 DDs being=0A> non-stalled.=0A>=0A=0AHi,=0A=0AIf you are running EHCI, there=
  has been no changes in the USB stack, and =0Ayou should look for CAM/SCSI =
 related changes:=0A=0AJust grepping quickly, can this be related to what yo=
 u are seeing?=0A=0Ahttp://svnweb.freebsd.org/changeset/base/259722=0A=0A--H=
 PS
 --464114708-874558429-1389412258=:8299
 Content-Type: text/html; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 I rebuilt the kernel with change 259722 reverted:  ident /boot/kernel.scsi_all-back/kernel | grep /scsi=
 _all.c  =3D> $FreeBSD: stable/9/sys=
 /cam/scsi/scsi_all.c 257050 2013-10-24 10:34:13Z mav $Still have th=
 e same dmesges:-usbd_req_re_enumerate: addr=3D2, set addres=
 s failed! (USB_ERR_STALLED, ignored)usbd_setup_device_desc: getting dev=
 ice descriptor at addr 2 failed, USB_ERR_STALLEDusbd_req_re_enumerate: =
 addr=3D2, set address failed! (USB_ERR_STALLED, ignored)usbd_setup_devi=
 ce_desc: getting device descriptor at addr 2 failed, USB_ERR_STALLEDusb=
 _alloc_device: Failure selecting configuration index 0:USB_ERR_STALLED, por=
 t 4, addr 2 (ignored)ugen5.2:  at
  usbus5I'll launch another rebuild for the night, after 'sv=
 n up' -- maybe something will be discovered.  If anybody has suggestio=
 ns on debugging the issue, please let me know.-- Alex   On Friday, January 10, 2014 8:08 AM, Hans Petter Selasky  wrote:On=
  01/10/14 12:49, Alex Goncharov wrote:>> >If devices simply re=
 -attach either they are not respond and software>> >initiates =
 a reset, which can be disabled by setting>> >"hw.usb.no_cs_fai=
 l" or the
  software in the USB HDD died and>> >rebooted.> May be;=
  but think about the fact correlations: the fact of the two> system'=
 s upgrade, two identical Seagate units, and other HDDs being> non-st=
 alled.>Hi,If you are running EHCI, there has been no=
  changes in the USB stack, and you should look for CAM/SCSI related cha=
 nges:Just grepping quickly, can this be related to what you are see=
 ing?http://svnweb.freebsd.org/changeset/base/259722"; tar=
 get=3D"_blank">http://svnweb.freebsd.org/changeset/base/259722-=
 -HPS  
 --464114708-874558429-1389412258=:8299--
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Re: usb/185628: usbd_req_re_enumerate set address failed USB_ERR_STALLED for Seagate USB drives between r259425 and r260321

2014-01-10 Thread Alex Goncharov 
The following reply was made to PR usb/185628; it has been noted by GNATS.

From: Alex Goncharov 
To: Hans Petter Selasky ,
  "freebsd-gnats-sub...@freebsd.org" 
Cc:  
Subject: Re: usb/185628: usbd_req_re_enumerate set address failed 
USB_ERR_STALLED for Seagate USB drives between r259425 and r260321
Date: Fri, 10 Jan 2014 06:05:04 -0800 (PST)

 --464114708-1921223609-1389362704=:6984
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 > If you are running EHCI, there has been no changes in the USB stack, and=
 =0A> you should look for CAM/SCSI related changes:=0A> =0A> Just grepping q=
 uickly, can this be related to what you are seeing?=0A> =0A> http://svnweb.=
 freebsd.org/changeset/base/259722=0A=0A=A0 Author: =A0=A0=A0 mav=0A=A0 Date=
 : =A0=A0=A0 Sun Dec 22 13:03:33 2013 UTC (2 weeks, 5 days ago)=0A=0AThank y=
 ou: this may be the trouble-causing change.=A0 Later, I'll see if=0Areverti=
 ng it results in being able to use the Seagate HDDs again.=0A=0AThe 'pcicon=
 f' for the desktop (upgraded, Seagate-problematic now):=0A=0A--=
 =0Apciconf -lv=0A=
 =3D>=0Ahostb0@pci0:0:0:0:=A0=A0=A0=A0=A0 class=3D0x06 card=3D0x01271028=
  chip=3D0x25608086 rev=3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D=
  'Intel Corporation'=0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82845G/GL[Brookdal=
 e-G]/GE/PE DRAM Controller/Host-Hub Interface'=0A=A0=A0=A0 class=A0=A0=A0=
 =A0=A0 =3D bridge=0A=A0=A0=A0 subclass=A0=A0 =3D HOST-PCI=0Avgapci0@pci0:0:=
 2:0:=A0=A0=A0=A0 class=3D0x03 card=3D0x01271028 chip=3D0x25628086 rev=
 =3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=
 =0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82845G/GL[Brookdale-G]/GE Chipset Inte=
 grated Graphics Device'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =3D display=0A=A0=
 =A0=A0 subclass=A0=A0 =3D VGA=0Auhci0@pci0:0:29:0:=A0=A0=A0=A0=A0 class=3D0=
 x0c0300 card=3D0x01271028 chip=3D0x24c28086 rev=3D0x01 hdr=3D0x00=0A=A0=A0=
 =A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=0A=A0=A0=A0 device=A0=A0=A0=
 =A0 =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller'=0A=A0=A0=
 =A0 class=A0=A0=A0=A0=A0 =3D serial bus=0A=A0=A0=A0 subclass=A0=A0 =3D USB=
 =0Auhci1@pci0:0:29:1:=A0=A0=A0=A0=A0 class=3D0x0c0300 card=3D0x01271028 chi=
 p=3D0x24c48086 rev=3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'In=
 tel Corporation'=0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82801DB/DBL/DBM (ICH4/=
 ICH4-L/ICH4-M) USB UHCI Controller'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =3D se=
 rial bus=0A=A0=A0=A0 subclass=A0=A0 =3D USB=0Auhci2@pci0:0:29:2:=A0=A0=A0=
 =A0=A0 class=3D0x0c0300 card=3D0x01271028 chip=3D0x24c78086 rev=3D0x01 hdr=
 =3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=0A=A0=A0=A0 =
 device=A0=A0=A0=A0 =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Contr=
 oller'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =3D serial bus=0A=A0=A0=A0 subclass=
 =A0=A0 =3D USB=0Aehci0@pci0:0:29:7:=A0=A0=A0=A0=A0 class=3D0x0c0320 card=3D=
 0x01271028 chip=3D0x24cd8086 rev=3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=
 =A0=A0 =3D 'Intel Corporation'=0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82801DB/=
 DBM (ICH4/ICH4-M) USB2 EHCI Controller'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =
 =3D serial bus=0A=A0=A0=A0 subclass=A0=A0 =3D USB=0Apcib1@pci0:0:30:0:=A0=
 =A0=A0=A0=A0 class=3D0x060400 card=3D0x chip=3D0x244e8086 rev=3D0x8=
 1 hdr=3D0x01=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=0A=A0=
 =A0=A0 device=A0=A0=A0=A0 =3D '82801 PCI Bridge'=0A=A0=A0=A0 class=A0=A0=A0=
 =A0=A0 =3D bridge=0A=A0=A0=A0 subclass=A0=A0 =3D PCI-PCI=0Aisab0@pci0:0:31:=
 0:=A0=A0=A0=A0=A0 class=3D0x060100 card=3D0x chip=3D0x24c08086 rev=
 =3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=
 =0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82801DB/DBL (ICH4/ICH4-L) LPC Interfac=
 e Bridge'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =3D bridge=0A=A0=A0=A0 subclass=
 =A0=A0 =3D PCI-ISA=0Aatapci0@pci0:0:31:1:=A0=A0=A0 class=3D0x01018a card=3D=
 0x01271028 chip=3D0x24cb8086 rev=3D0x01 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=
 =A0=A0 =3D 'Intel Corporation'=0A=A0=A0=A0 device=A0=A0=A0=A0 =3D '82801DB =
 (ICH4) IDE Controller'=0A=A0=A0=A0 class=A0=A0=A0=A0=A0 =3D mass storage=0A=
 =A0=A0=A0 subclass=A0=A0 =3D ATA=0Anone0@pci0:0:31:3:=A0=A0=A0=A0=A0 class=
 =3D0x0c0500 card=3D0x01271028 chip=3D0x24c38086 rev=3D0x01 hdr=3D0x00=0A=A0=
 =A0=A0 vendor=A0=A0=A0=A0 =3D 'Intel Corporation'=0A=A0=A0=A0 device=A0=A0=
 =A0=A0 =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller'=0A=A0=A0=
 =A0 class=A0=A0=A0=A0=A0 =3D serial bus=0A=A0=A0=A0 subclass=A0=A0 =3D SMBu=
 s=0Adc0@pci0:1:7:0: class=3D0x02 card=3D0x05741317 chip=3D0x09851317 re=
 v=3D0x11 hdr=3D0x00=0A=A0=A0=A0 vendor=A0=A0=A0=A0 =3D 'ADMtek'=0A=A0=A0=A0=
  device=A0=A0=A0=A0 =3D 'NC100 Network Everywhere Fast Ethernet 10/100'=0A=
 =A0=A0=A0 class=A0=A0=A0=A0=A0 =3D network=0A=A0=A0=A0 subclass=A0=A0 =3D e=
 thernet=0Afxp0@pci0:1:

Re: usb/185628: usbd_req_re_enumerate set address failed USB_ERR_STALLED for Seagate USB drives between r259425 and r260321

2014-01-10 Thread Hans Petter Selasky 
The following reply was made to PR usb/185628; it has been noted by GNATS.

From: Hans Petter Selasky 
To: Alex Goncharov , 
 "freebsd-gnats-sub...@freebsd.org" 
Cc:  
Subject: Re: usb/185628: usbd_req_re_enumerate set address failed 
USB_ERR_STALLED
 for Seagate USB drives between r259425 and r260321
Date: Fri, 10 Jan 2014 14:09:05 +0100

 On 01/10/14 12:49, Alex Goncharov wrote:
 >> >If devices simply re-attach either they are not respond and software
 >> >initiates a reset, which can be disabled by setting
 >> >"hw.usb.no_cs_fail" or the software in the USB HDD died and
 >> >rebooted.
 > May be; but think about the fact correlations: the fact of the two
 > system's upgrade, two identical Seagate units, and other HDDs being
 > non-stalled.
 >
 
 Hi,
 
 If you are running EHCI, there has been no changes in the USB stack, and 
 you should look for CAM/SCSI related changes:
 
 Just grepping quickly, can this be related to what you are seeing?
 
 http://svnweb.freebsd.org/changeset/base/259722
 
 --HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Re: usb/185628: usbd_req_re_enumerate set address failed USB_ERR_STALLED for Seagate USB drives between r259425 and r260321

2014-01-10 Thread Alex Goncharov 
The following reply was made to PR usb/185628; it has been noted by GNATS.

From: Alex Goncharov 
To: Hans Petter Selasky ,
  "freebsd-gnats-sub...@freebsd.org" 
Cc:  
Subject: Re: usb/185628: usbd_req_re_enumerate set address failed 
USB_ERR_STALLED for Seagate USB drives between r259425 and r260321
Date: Fri, 10 Jan 2014 03:49:00 -0800 (PST)

 --464114708-973494774-1389354540=:24518
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 Hello Hans,=0A=0AThank you for your prompt replies; I'll make this a short =
 note, before=0Arunning to work, and we can work on this later.=0A=0A> Here =
 is a patch you can try, as an attachment.=0A=0AOK, re-building now.=0A=0A> =
 Can you give some more details? Are these in some kind of enclosure?=0A=0AT=
 his model:=0A=0A=A0=A0 http://www.amazon.com/gp/product/B008R7FC74/ref=3Dwm=
 s_ohs_product?ie=3DUTF8&psc=3D1=0A=0A> What USB speed are they connected at=
 ?=0A=0A"A normal" one -- I speak as a layman here; later I can give you all=
 =0A'usbconfig' information.=0A=0A> If you are using an XHCI controller and =
 the drives are connected at=0A> Super Speed (5.0 GBit),=0A=0ADon't think so=
 .=0A=0A> Do other USB devices connected to the same USB host controller=0A>=
  continue to work?=0A=0ADidn't try many but, Buffalo and Sony USB drives di=
 dn't show anything=0Alike the Seagate's behavior -- see my original posting=
 .=0A=0ANow: the two upgraded computers, both of which get these=0AUSB_ERR_S=
 TALLED events, are totally different: one is a self-built=0Adesktop, the ot=
 her -- a Compaq laptop.=A0 The OS upgrade is the common=0Afactor.=0A=0A> Ca=
 n you tell which USB controllers you have in your system (PCI=0A> devices) =
 and tell to which of these your HDD's are attaching to.=0A=0A(Later).=0A=0A=
 > If devices simply re-attach either they are not respond and software=0A> =
 initiates a reset, which can be disabled by setting=0A> "hw.usb.no_cs_fail"=
  or the software in the USB HDD died and=0A> rebooted.=0A=0AMay be; but thi=
 nk about the fact correlations: the fact of the two=0Asystem's upgrade, two=
  identical Seagate units, and other HDDs being=0Anon-stalled.=0A=0A> Linux =
 hide these problems, but they are visible through the fact that=0A> you'll =
 see some requests delaying for some seconds to complete instead=0A> of some=
  milliseconds.=0A=0AI copied the 1 TB of data from Seagate UFS to Sony Ext4=
  and Sony NTFS,=0Amuch faster than I expected it to happen based on my past=
  FreeBSD=0Aperceptions.=A0 This is just a perception, not a measured fact, =
 but I=0Areally don't care about a 25% slower if I can use an HDD.=A0 In the=
 =0Apast, I had to return a 1 TB Western Digital HDD, because it was=0Apredi=
 ctably lost while even being read on my FreeBSD systems.=A0 Seagate=0Aand T=
 oshiba apparently do some retries which WD didn't.=0A=0A> Beware that many =
 USB HDD's contain reprogramable software and that there=0A> might be timing=
  reasons for HDD's breaking down on one system and not on=0A> another. For =
 example Linux buffer at lot more using 64K reads, while=0A> under FreeBSD y=
 ou'll see more different block sizes being read and written.=0A> =0A> Do yo=
 u have dmesg from around the spurious detach?=0A=0ALater -- I have to go *n=
 ow*.=0A=0A=0A-- Alex=0A=0A=0A=0A=0AOn Friday, January 10, 2014 2:47 AM, Han=
 s Petter Selasky  wrote:=0A =0AOn 01/10/14 04:02, Alex Gon=
 charov wrote:=0A>=0A>> Number:=A0 =A0 =A0 =A0  185628=0A>> Category:=A0 =A0=
  =A0  usb=0A>> Synopsis:=A0 =A0 =A0  usbd_req_re_enumerate set address fail=
 ed USB_ERR_STALLED for Seagate USB drives between r259425 and r260321=0A>> =
 Confidential:=A0  no=0A>> Severity:=A0 =A0 =A0  non-critical=0A>> Priority:=
 =A0 =A0 =A0  low=0A>> Responsible:=A0 =A0 freebsd-usb=0A>> State:=A0 =A0 =
 =A0 =A0 =A0 open=0A>> Quarter:=0A>> Keywords:=0A>> Date-Required:=0A>> Clas=
 s:=A0 =A0 =A0 =A0 =A0 sw-bug=0A>> Submitter-Id:=A0  current-users=0A>> Arri=
 val-Date:=A0  Fri Jan 10 03:10:00 UTC 2014=0A>> Closed-Date:=0A>> Last-Modi=
 fied:=0A>> Originator:=A0 =A0  Alex Goncharov=0A>> Release:=A0 =A0 =A0 =A0 =
 9.2-STABLE, built from svn source, r260321=0A>> Organization:=0A>> Environm=
 ent:=0A> FreeBSD 9.2-STABLE FreeBSD 9.2-STABLE #0 r260321 Sun Jan=A0 5 13:0=
 6:01 EST 2014=0A>> Description:=0A> This is an extremely reproducible and v=
 ery upsetting new problem.=0A=0AHere is a patch you can try, as an attachme=
 nt.=0A=0A--HPS
 --464114708-973494774-1389354540=:24518
 Content-Type: text/html; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 Hello Hans,Thank you for your prompt repli=
 es; I'll make this a short note, beforerunning to work, and we can work=
  on this later.> Here is a patch you can try, as an attachment.<=
 br>OK, re-building now.> Can you give some more details? Are=
  these in some kind of enclosure?This model:   ht=
 tp://www.amazon.com/gp/product/B008R7FC74/ref=3Dwms_ohs_product?ie=3DUTF8&a=
 mp;psc=3D1> What USB speed are