Miles Lane wrote:
>
>
> Personally, I agree with you, but I can also understand David's
> desire to avoid wasting time chasing phantom bugs that only
> show up due to this broken hardware. If it turns out that
> there is actually a well-defined workaround that AMD will
> tell us about, it
Joachim 'roh' Steiger wrote:
> i would like to help to track down this problem
> i'm using a gigabyte 7IXE revision 1.1
> kernel is 2.4.1
>
> lspci output for usb:
> 00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
> (rev 06) (prog-i
> f 10 [OHCI])
> Flags: bus
Thomas Dodd wrote:
> Alan Cox wrote:
>
>>> David Brownell recently added this check to the usb-ohci driver
>>> since noone has gotten information from AMD for the workaround,
>>> which is rumored to exist, for this bug.
>>>
>>> Do any of you have contacts within AMD who might be able to
>>>
Alan Cox wrote:
>
> > David Brownell recently added this check to the usb-ohci driver
> > since noone has gotten information from AMD for the workaround,
> > which is rumored to exist, for this bug.
> >
> > Do any of you have contacts within AMD who might be able to
> > get an explanation of the
Alan Cox wrote:
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to exist, for this bug.
Do any of you have contacts within AMD who might be able to
get an explanation of the workaround
Thomas Dodd wrote:
Alan Cox wrote:
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to exist, for this bug.
Do any of you have contacts within AMD who might be able to
get an explanation of
Joachim 'roh' Steiger wrote:
i would like to help to track down this problem
i'm using a gigabyte 7IXE revision 1.1
kernel is 2.4.1
lspci output for usb:
00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
(rev 06) (prog-i
f 10 [OHCI])
Flags: bus master,
Miles Lane wrote:
Personally, I agree with you, but I can also understand David's
desire to avoid wasting time chasing phantom bugs that only
show up due to this broken hardware. If it turns out that
there is actually a well-defined workaround that AMD will
tell us about, it shouldn't
> David Brownell recently added this check to the usb-ohci driver
> since noone has gotten information from AMD for the workaround,
> which is rumored to exist, for this bug.
>
> Do any of you have contacts within AMD who might be able to
> get an explanation of the workaround to David Brownell?
Running 2.4.2-ac28, I get the following error:
usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756 [Viper] USB):
blacklisted, erratum #4
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to
Running 2.4.2-ac28, I get the following error:
usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756 [Viper] USB):
blacklisted, erratum #4
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to
David Brownell recently added this check to the usb-ohci driver
since noone has gotten information from AMD for the workaround,
which is rumored to exist, for this bug.
Do any of you have contacts within AMD who might be able to
get an explanation of the workaround to David Brownell?
We
12 matches
Mail list logo
