Sorry, I don't think I'll make time to put into
developing any patch without the chip errata
unless it's just to prevent that chip from initting.
With a chip erratum like that one, consistent
failure modes aren't guaranteed. But you're
right to imply there may be other gremlins
at play here.
- Dave
----- Original Message -----
From: "Thomas Dodd" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 7:03 AM
Subject: Re: [linux-usb-devel] Re: Bug report (2.4.1)
> Miles Lane wrote:
> >
> > 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'll test them too.
> The only USN device I have is a mouse, but
> it's enough to trigger the problem.
>
> Still, If it's a chip bug, why is it only showing
> in the newer 2.4.2-ac patches? ac3 worked fine.
> Something changed to cause this to show up.
>
> -Thomas
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
