From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: ehci-hcd on CARDBUS hangs when stopping card service
Date: Tue, 28 May 2002 15:54:19 +0200 [thread overview]
Message-ID: <20020528155419.E681@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <acm1vp$2ak$1@penguin.transmeta.com> <20020523171326.GA11562@kroah.com> <3CED6E0B.8020501@pacbell.net> <acm1vp$2ak$1@penguin.transmeta.com> <28429.1022420490@redhat.com>
On Sun, May 26, 2002 at 02:41:30PM +0100, David Woodhouse wrote:
> torvalds@transmeta.com said:
> > Also, it's generally a good idea to "just say no" to endless loops in
> > drivers. Hardware bugs _do_ happen, and it's a lot more pleasant to
> > have the driver do a
> > printk("Device does not respond\n");
> > than for the kernel to hang.
>
> Too late. On some hardware, if you try to talk to the device once it's
> gone, you're already dead. Not all the world is a PeeCee.
That happens even on a "PeeCee".
Situation:
- Normal readl() of a ioremap()ed register set of a
PCI device[1]:
-> machine hangs hard (no magic sysrq possible, no Ooops, no
panic printed)
- Several DWORD reads of the same register set succeded before
and the register is wired according to the SPEC.
Just to provide an argument here
PS: I wish I had an PCI Analyzer available...
[1] TI TMS320C6x EVM Board[2], Rev. 3
with PCI-Bridge Chip AMCC S5933[3] hanging the host side on Busmaster DMA.
[2] PCI-ID: 0x104c:0x1002
[3] PCI-ID: 0x10e8:0x4750 or 0x10e8:0x807d or 0x10e8:0x809c
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-05-28 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020523171326.GA11562@kroah.com>
2002-05-23 22:32 ` David Brownell
2002-05-24 18:49 ` Linus Torvalds
2002-05-26 13:41 ` David Woodhouse
2002-05-28 13:54 ` Ingo Oeser [this message]
[not found] ` <200205241849.g4OInTe02393@penguin.transmeta.com>
2002-05-25 17:15 ` David Brownell
2002-05-25 17:54 ` Linus Torvalds
2002-05-27 6:27 ` Borsenkow Andrej
2002-05-27 18:37 ` David Brownell
2002-05-27 10:54 ` Borsenkow Andrej
2002-05-23 6:33 Borsenkow Andrej
2002-05-23 6:39 ` Borsenkow Andrej
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=20020528155419.E681@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®