public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thockin@hockin.org
To: "Campbell, Shawn" <scampbell@malone.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FW: PCI Express or TG3 issue
Date: Wed, 21 Sep 2005 11:11:51 -0700	[thread overview]
Message-ID: <20050921181151.GA809@hockin.org> (raw)
In-Reply-To: <15F23A40330F5742B268A041F003055705D2A3@srv-elijah1.malone.int>

On Wed, Sep 21, 2005 at 01:34:58PM -0400, Campbell, Shawn wrote:
> hexdump /proc/bus/pci/02/00.0
> 
> 0000010 0004 d000 0001 8000 0000 0000 0000 0000
             ^ means 64-bit memory BAR

This device is claiming that it has a 64-bit base-address which has been
programmed by BIOS to be at 0x80000001d0000000.

I suspect that the 4 bytes at offset 0x14 want to be 0.  The address
0xd0000000 jives with the rest of your PCI listing.

I don't know where that extra 0x80000001 comes from, but it's pretty
clearly wrong.  BIOS bug?  I can't see where kernel would have boned that
up *that* badly.

  reply	other threads:[~2005-09-21 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 17:34 FW: PCI Express or TG3 issue Campbell, Shawn
2005-09-21 18:11 ` thockin [this message]
2005-09-22 15:25   ` Atsushi Nemoto
2005-09-22 15:58     ` thockin

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=20050921181151.GA809@hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scampbell@malone.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