mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Mike Houston <mikeserv@bmts.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sky2/pci issues on Gigabyte
Date: Thu, 24 May 2007 15:48:23 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0705241524350.26602@woody.linux-foundation.org> (raw)
In-Reply-To: <20070524150845.07d0608f@freepuppy>



On Thu, 24 May 2007, Stephen Hemminger wrote:
> 
> Looking at the 88e8056 PCI config values:

I think you're looking at the wrong device.

The ones that matter are likely the PCI-X bridge, not the device. The 
device cannot reasonably screw up DMA (unless it's really scrogged, but 
then it wouldn't work under Vista either).

So it's much more likely to be about device 00:1c.4, which is the bridge 
to PCI bus #4:

	00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 
		Bus: primary=00, secondary=04, subordinate=04, sec-latency=0

So I'd look at its config space instead ("-" is Vista, "+" is Linux):

	-00: 86 80 47 28 07 00 10 00 02 00 04 06 08 00 81 00
	+00: 86 80 47 28 07 04 10 00 02 00 04 06 08 00 81 00

	 10: 00 00 00 00 00 00 00 00 00 04 04 00 b0 b0 00 00

	-20: 00 f7 f0 f8 f1 ff 01 00 00 00 00 00 00 00 00 00
	+20: 00 f7 f0 f8 01 80 01 80 00 00 00 00 00 00 00 00

	-30: 00 00 00 00 40 00 00 00 00 00 00 00 10 01 04 00
	+30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 04 00

	-40: 10 80 41 01 c0 8f 00 00 00 00 10 00 11 24 11 05
	+40: 10 80 41 01 c0 8f 00 00 0f 00 11 00 11 24 11 05

	 50: 40 00 11 30 60 05 a0 00 00 00 48 01 00 00 00 00
	 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

	-80: 05 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	+80: 05 90 01 00 0c 10 e0 fe d1 41 00 00 00 00 00 00

	 90: 0d a0 00 00 58 14 01 50 00 00 00 00 00 00 00 00
	 a0: 01 00 02 c8 00 00 00 00 00 00 00 00 00 00 00 00
	 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Which I _think_ is (I tried to be careful, but..):

		Vista		Linux
		
	04:	0x00100007	0x00100407
	24:	0x0001fff1	0x08018001
	3c:	0x00040110	0x0004010b
	48:	0x00100000	0x0011000f
	80:	0x00009005	0x00019005
	84:	0x00000000	0xfee0100c
	88:	0x00000000	0x000041d1

but I have not looked at what the _meaning_ of those register
differences are. 

The host bridge itself could be the problem, but that one is identical
in the PCI config space.  I guess it could also be this one:

	00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02) (prog-if 00 [Normal decode])
		Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

but I don't know how "port 5" (which is the bus that the ethernet
controller is behind) is related to that "root port" (which is reported
to bridge only subordinate bus 01).  The "root port" thing makes me
suspect that device 00:01.0 is somehow related to 00:1c.4 despite the
apparent lack of relationship in the bus topology itself (and the root
port does _not_ decode the IO/MEM resources that lead to the ethernet
chip).

There _are_ differences in that root port device too, but I haven't done
the diff of them yet. 

			Linus

  reply	other threads:[~2007-05-24 22:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  5:17 Linux 2.6.22-rc2 Linus Torvalds
2007-05-19  6:54 ` Andrey Borzenkov
2007-05-19 14:28 ` [BUG: 2.6.22-rc2] SLAB doesn't like usb_get_configuration() Indan Zupancic
     [not found]   ` <6101e8c40705190950jb093d65l611995895a182ec0@mail.gmail.com>
2007-05-19 16:51     ` Fwd: " oliver pinter
2007-05-19 18:20   ` Christoph Lameter
2007-05-19 19:33     ` Greg KH
2007-05-19 22:10       ` Indan Zupancic
2007-05-20 12:57 ` Linux 2.6.22-rc2: make -j makes it unresponsive Rafael J. Wysocki
2007-05-20 13:01   ` Krzysztof Halasa
2007-05-20 13:23     ` Rafael J. Wysocki
2007-05-20 21:05 ` Linux 2.6.22-rc2 Mike Houston
2007-05-21 15:45   ` Stephen Hemminger
2007-05-21 17:10     ` Mike Houston
2007-05-21 17:37       ` Stephen Hemminger
2007-05-22  2:58         ` Mike Houston
2007-05-22  4:31           ` Stephen Hemminger
2007-05-22  4:36             ` Jeff Garzik
2007-05-22  4:42               ` Stephen Hemminger
2007-05-22  5:04                 ` Linus Torvalds
2007-05-22 17:19                   ` Stephen Hemminger
2007-05-22 17:54                   ` H. Peter Anvin
2007-05-22 22:14             ` Mike Houston
2007-05-23  0:00               ` Linus Torvalds
2007-05-23  0:29                 ` Stephen Hemminger
2007-05-23  1:53                   ` Linus Torvalds
2007-05-23 14:58                     ` Stephen Hemminger
2007-05-23 17:39                 ` Mike Houston
2007-05-23 17:46                   ` Linus Torvalds
2007-05-23 18:04                     ` Stephen Hemminger
2007-05-24 18:26                     ` Mike Houston
2007-05-24 22:08                       ` sky2/pci issues on Gigabyte Stephen Hemminger
2007-05-24 22:48                         ` Linus Torvalds [this message]
2007-05-24 23:04                           ` Stephen Hemminger
2007-05-25  0:01                             ` Mike Houston

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=alpine.LFD.0.98.0705241524350.26602@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeserv@bmts.com \
    --cc=shemminger@linux-foundation.org \
    /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®