From: David Brownell <david-b@pacbell.net>
To: "Joachim 'roh' Steiger" <roh@convergence.de>,
Miles Lane <miles@megapathdsl.net>
Cc: Thomas Dodd <ted@cypress.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Contacts within AMD? AMD-756 USB host-controller blacklisted due to
Date: Wed, 04 Apr 2001 16:00:22 -0700 [thread overview]
Message-ID: <052c01c0bd5b$0843ab60$6800000a@brownell.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0104050004060.21943-100000@campari.convergence.de>
> Apr 4 14:47:15 campari kernel: usb-ohci.c: bogus NDP=204 for OHCI
> usb-00:07.4
> Apr 4 14:47:15 campari kernel: usb-ohci.c: rereads as NDP=4
Means that your system would have oopsed if it hadn't
tested for the bogus register read (NDP). That's only one
path; other bogus reads (which could also oops) on other
paths are undetected. Slightly less-bogus reads on that
particular path may not be detected, and can still oops.
> please correct me if i'm wrong i only don't want to blacklist complete
> chipset-series
Then feel free to develop and submit a better fix. That'd
be more practical if AMD's workaround were public. As I
understand it, the bulk of the production chips have this
erratum. More power to RedHat getting info from AMD.
Meanwhile, this patch improves robustness.
- Dave
next prev parent reply other threads:[~2001-04-04 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 17:46 Contacts within AMD? AMD-756 USB host-controller blacklisted due to erratum #4 Miles Lane
2001-04-03 19:10 ` Contacts within AMD? AMD-756 USB host-controller blacklisted due to Alan Cox
2001-04-04 19:12 ` Thomas Dodd
2001-04-04 18:54 ` Miles Lane
2001-04-04 22:19 ` Joachim 'roh' Steiger
2001-04-04 21:40 ` Miles Lane
2001-04-04 23:50 ` Ryan Butler
2001-04-04 23:00 ` David Brownell [this message]
2001-04-05 0:08 ` Contacts within AMD? AMD-756 USB host-controller blacklisted dueto Thomas Dodd
2001-04-05 0:27 ` Alan Cox
2001-04-05 20:29 ` Thomas Dodd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='052c01c0bd5b$0843ab60$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
--cc=roh@convergence.de \
--cc=ted@cypress.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox