Matthew Dharm wrote:
>
> Some questions:
> (1) I'm guessing that this is an OHCI system, based on your other
> messages. Please confirm/deny this.
Yes. I am seeing this problem on an Athlon-based machine with OHCI.
> (2) Does anyone know why we're not seeing the "OHCI Root Hub" string in
> the output? Did that patch (to identify virtual root hubs) not make it
> into the kernel?
>
> (3) I'm guessing that the ORB drive had media in it when this was done.
> Please confirm/deny.
Yes. Media was present and I had reset power to the drive before
booting, so itought to be in a known good state.
> (4) Does this always fail, or just sometimes? It's clear that at least
> one command makes it to the device in this trace -- do others sometime
> make it?
It failed twice during different boot sessions.
> (5) Can you send the logfile processed by syslog with timestamps? That
> can be helpful, especially with timeout/reset conditions.
Yes. I will send this.
> (6) Can you test this on a UHCI system (or OHCI, which ever you don't have
> -- see question 1)?
Yes. I will get the latest stuff up on my laptop and test with UHCI.
> (7) I find it somewhat odd that the INQUIRY data returned happens to be
> exactly 255 bytes. It just rubs my instincts funny. Could you hack the
> driver to, in the case of an INQUIRY, only get like 50 bytes? You should
> be able to do this by editing us_transfer_length(). Do that, retest, and
> let me know if it makes a difference.
I will try this on the Athlon machine.
Best wishes,
Miles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
