Date: Wed, 30 Mar 2005 15:40:36 +0400 From: Alexandre Jouravlev <bofh@mail.ru> To: ticso@cicely.de Cc: freebsd-usb@freebsd.org Subject: Re: Ezload problems. Message-ID: <6ea402e33ab5f4d1a9e66c51c5ddc78a@mail.ru> In-Reply-To: <20050330110436.GM33677@cicely12.cicely.de> References: <d6c9e248f5b46757d8083af2d48db088@mail.ru> <20050330104411.GL33677@cicely12.cicely.de> <dd8d511271eeba61ce9b9b25c8d4e123@mail.ru> <20050330110436.GM33677@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 30, 2005, at 3:04 PM, Bernd Walter wrote: > > E.g. you switch firmware by issuing an USB request and if the > device disconnects bevor the request is completed things may hang > until timeout or even forever. > Device disconnects normal, as I can see the device after reboot. (At least I think so.) > You say that you see the disconnect. > In which lock state (ps -axl) are the usb* and ezload processes > after the disconnect message? There is no ezdownload process after disconnect message. usb* in different states like usbevt and usbtsk. With USB_DEBUG I can see that download process is completed before disconnection. Hidden flag -r of ezdownload utility also does not help. > Is there any change if you wait a minute? > No change even if I wait for a whole night.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ea402e33ab5f4d1a9e66c51c5ddc78a>