> Date: Wed, 07 Nov 2007 14:03:27 +0000 Darren wrote: > Juergen Keil wrote: > > And its a single cpu / single core box. > > > > > > A wild guess: Has the user installed Casper's powernow driver? > > Yes I did install powernow. > > > > > I'm asking because I've observed similar timeouts: > > > > - on AMD64 boxes with nVidia chipset integrated ehci > > > > and > > > > - powernow driver set to automatic (and cpu is idle), > > or cpu forced to the slowest frquency > > > > and > > > > - Maxtor Personal Storage USB2.0 HDD > > Yep we tried one of those drives too! > > > The timeouts never happen when I force the cpu frequency to anything > > other than the slowest setting. That is, I've been using this shell > > script hack to work around the usb timeout problem: > > > > # avoid running in the slowest powernow state with the ASUS > > M2NPV-VM, > > # for some reason that breaks usb on the maxtor usb backup hdd > > date +"Backup is running: %T" > > > > /usr/sbin/powernowadm manual > > sleep 5 > > /usr/sbin/powernowadm slow > > /usr/sbin/powernowadm faster > > > > > > I was able to reproduce the same timeout / powernow issue using an > > ASUS M2N-SLI deluxe mainboard. > > > > Using the above powernowadm commands, the M2NPV-VM never again > > had the timeout issue, and the Maxtor USB2.0 HDDs have been used for > > writing about ~180GB each night, 5 times a week, for several month now. > > Thanks I'll give that a go and report back on how we get on.
Interesting test case, because on my two ASUS / nVidia chipset boxes I'm using dual core amd64 X2 cpus, and a slightly modified powernow driver which has dual core cpu powernow support added. I always suspected a possible problem with highres kernel timestamps and my powernow dual core modifications, but maybe this Asrock system shows that the problem also occurs on single core cpus & powernow... _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
