From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: oops in bk pull (oct 03)
Date: Fri, 04 Oct 2002 19:00:53 -0700 (PDT) [thread overview]
Message-ID: <20021004.190053.69975722.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210041839430.13749-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Fri, 4 Oct 2002 18:41:25 -0700 (PDT)
On Fri, 4 Oct 2002, David S. Miller wrote:
> Another theory is that some device just dislikes being given
> a 0 in one of it's base registers, but somehow ~0 is ok :-)
I think that is the real issue. We're mapping something - probably a host
bridge - at address 0, and then accessing RAM (which is also is mapped at
PCI address 0) and the host bridge is unhappy.
We're current blindly putting ~0 in there, how can that be any
better? :-)
So excluding the change is probably the right thing to do - it's just
fundamentally buggy to blindly put a base register at zero.
And putting ~0 there is ok?
>From what you're saying, that whole routine is fundamentally broken.
next prev parent reply other threads:[~2002-10-05 2:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:14 oops in bk pull (oct 03) Paul E. Erkkila
2002-10-04 21:58 ` Linus Torvalds
2002-10-05 0:03 ` Paul E. Erkkila
2002-10-05 0:33 ` Alexander Viro
2002-10-05 0:40 ` Linus Torvalds
2002-10-05 0:51 ` Alexander Viro
2002-10-05 1:02 ` Linus Torvalds
2002-10-05 1:13 ` David S. Miller
2002-10-05 1:27 ` Alexander Viro
2002-10-05 1:41 ` Linus Torvalds
2002-10-05 2:00 ` David S. Miller [this message]
2002-10-05 2:22 ` Linus Torvalds
2002-10-05 2:22 ` David S. Miller
2002-10-05 2:00 ` Linus Torvalds
2002-10-05 3:20 ` Alexander Viro
2002-10-05 3:26 ` Linus Torvalds
2002-10-05 9:35 ` Ivan Kokshaysky
2002-10-05 1:14 ` Alexander Viro
2002-10-05 0:44 ` Alexander Viro
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=20021004.190053.69975722.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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