On Thu, Oct 26, 2006 at 06:21:01PM -0400, Alan Stern wrote: > On Thu, 26 Oct 2006, Frank van Maarseveen wrote: > > > On Thu, Oct 26, 2006 at 10:12:55AM -0400, Alan Stern wrote: > > > On Wed, 25 Oct 2006, Frank van Maarseveen wrote: > > > > > > > 2.6.18.1, x386, VIA epia CL6000 + Sandisk USB memory stick (see below > > > > for data) > > > > > > > > It took me a while to figure it out but when this particular USB > > > > storage device > > > > is booted from after switching on power (no standby or powersave but a > > > > real cold boot) > > > > then with EHCI configured the partition table cannot be read by kernel > > > > and not by > > > > "hdparm -z". Instead I see > > > > > > > > usb 1-3: reset high speed USB device using ehci_hcd and address > > > > 2 > > > > > > > > every few (say 10) seconds. From this point on: > > > > > > > > - A warm reboot doesn't fix it. > > > > - A poweroff (apm=power-off) + pressing reset button doesn't fix > > > > it > > > > - replugging the device while the kernel runs fixes it > > > > - plugging main power renders it unusable again > > > > > > > > When another brand USB storage device is connected at the same time, > > > > that one > > > > remains usable all the time. Without EHCI in the kernel both works. > > > > > > It would help if you build your kernel with both CONFIG_USB_DEBUG and > > > CONFIG_USB_STORAGE_DEBUG set. The log for the bootup would then contain > > > more useful information. > > > > Too big to post, see www.frankvm.com/tmp/u139.kmsg > > There aren't any timestamps in the log, so I can't tell when any pauses > may have occurred. After the device initially failed, did you remove it > and then plug it back in again?
Yes, I gave it some time to get more logging and then replugged the USB stick. > My only thought is that maybe the device doesn't like the long delay > during boot-up. It's just sitting there, getting power from the USB port > but not receiving any signals, for 30 seconds or more before the drivers > get loaded and start talking to it. Whereas if you plug it in after the > system is already up, then it gets enumerated right away at high speed. But the BIOS succesfully booted the kernel from this USB stick. And replugging the USB stick is a fix which survives a reboot and even power standby mode (USB stick has a LED which stays on though). The issue only occurs after power has completely been removed and restored + EHCI driver in kernel. And not with every USB stick so that's a factor too. Anyway, it's not that important for me anymore. I was just hoping that it would provide a clue to avoid similar ehci problems in the future. > I have no idea whether this is the actual cause of the problem. You could > find out by running a simple test: > > rmmod ehci-hcd > rmmod uhci-hcd > Plug in the device > Wait 60 seconds > modprobe ehci-hcd > > That would reproduce the boot-up sequence of events, more or less. > > Even if this does cause the device to fail, it doesn't explain why or > suggest a possible solution. Perhaps this is just a peculiarity of the > device and there's no way around it. > > Alan Stern -- Frank ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
