David Brownell wrote:
> If this is the same erratum I remember from before,
> it shouldn't show up in recent hardware. Only chips
> made before last May or so, not more recent ones;
> recent Socket-A systems tend to have Via (or ALi,
> DDR now available :-) chipsets, especially for the
> southgate with the usb controller.
>
> This might be good to have in a FAQ, unless/until
> someone gets the workaround from AMD and puts
> it into a patch. (Always an extra read in the irq
> handler?)
Hi,
I would be happy to test a patch which adds an extra
read in the irq handler. I have an AMD-756 in my
Athlon machine. With some of the recent -ac builds
of 2.4.2, I get an OOPS after loading usb-ohci
(hotplug tries to set up the devices).
I just tried unplugging all my devices from the
internal host-controller and rebooting. This time
"/etc/rc.d/init.d/hotplug start" ran without causing
an OOPS. This would seem to support the notion that
enumerating the devices and loading the required
drivers is related to the OOPS (eg. it isn't caused
by loading usb-ohci).
I am curious to see whether adding the second read
makes the OOPS go away.
Thanks,
Miles
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
