Hi David,
This only occurs on a G4/500, my G5 works fine in this
configuration. The G4/500 fails in both 10.3.9 and 10.4.0.
system.log includes these messages:
Sep 22 03:34:32 localhost kernel:
RoperTucsonPCI::=========================>Timeout Occurred!!!!!
Sep 22 03:34:32 localhost kernel:
RoperTucsonPCI::=========================>Timeout Occurred!!!!!
Sep 22 03:34:32 localhost kernel: USBF: 180.827 [0x1b7ba00] (Reset)
USB Generic Hub @ 2 (0x9100000)
This suggests to me that the camera card (made by Roper) is timing
out, a USB reset then occurs almost immediately afterwards.
The odd thing is that the PCI card works fine with a different
(much slower) camera. I'm wondering whether the developers of the
Roper PCI driver are doing something odd to try and recover from
this timeout they've logged, which is in turn affecting the USB
host controller.
Anyway, thanks for your comments - I've passed this to the card
manufacturer now (though the solution for the customer may be just
to buy a G5)!
Cheers,
Steve.
On 26 Sep 2005, at 20:58, David Ferguson wrote:
You will need some good tools to get to the bottom of this type of
problem. Could an errant PCI device affect annother PCI device?
-- sure. Is that happening here? -- the only way to know will be
with a PCI bus analyzer.
First, you may want to install logging versions of the IOUSBFamily
-- use the logging tab of USB Prober to look at the USB log --
Also, check both the system and console logs for messages from the
relevant drivers.
I would contact the necessary vendors and see if they can provide
versions of their drivers to help you debug/analyze this problem.
What is the host you are using? Does this problem occur with all
machines, or just some configurations?
David Ferguson
Apple Computer
At 8:13 PM +0100 9/26/05, Steve Baxter wrote:
Hi,
We have a strange problem where initialising a PCI-based
scientific digital camera is causing writes to a USB serial
adapter (Keyspan) to hang our software. We are slightly stuck in
the middle of this (not having access to the driver source code
of either the PCI card or USB device), but my suspicion is that
the PCI driver is causing a USB reset, which is in turn getting
the Keyspan adapter into a strange state behind the back of the
Keyspan driver.
Does anyone know if a PCI device driver could cause a USB device
to stop working in this way? I guess that the USB controller is
a device on the PCI bus, but is there any way in which a PCI
driver could affect devices other than the ones they are supposed
to be controlling?
Cheers,
Steve.
Stephen Baxter
Software Development Manager
Improvision
email@hidden
+44-2476-692229
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
Stephen Baxter
Software Development Manager
Improvision
email@hidden
+44-2476-692229
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
