public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: dann frazier <dannf@hp.com>
Cc: linux-scsi@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mptsas, msi and the dl585 g2
Date: Thu, 09 Jul 2009 12:34:12 -0700	[thread overview]
Message-ID: <4A564634.1020708@kernel.org> (raw)
In-Reply-To: <4A564263.5010305@kernel.org>

Yinghai Lu wrote:
> dann frazier wrote:
>>   --------------------------------------------------------------------
>>   commit 30a18d6c3f1e774de656ebd8ff219d53e2ba4029
>>   Author: Yinghai Lu <Yinghai.Lu@Sun.COM>
>>   Date:   Tue Feb 19 03:21:20 2008 -0800
>>
>>       x86: multi pci root bus with different io resource range, on
>>       64-bit
>>   --------------------------------------------------------------------
>>
>> This appears to be the commit that actually introduced the issue.
>> I've attached dmesg w/ PCI DEBUG enabled from both sides of this
>> changeset, as well as a diff w/o printk timestamps.
>>
>> Also note that #ifdef'ing out x86_pci_root_bus_res_quirks() in
>> amd_bus.c seems to avoid the problem as well.
> 
> your BIOS didn't allocate io resources to some device under HT chain on node1/link2
> aka under peer root bus.
> 
> Kernel try to allocate resource to them.
> 
> and the patch did right thing according to range 
> bus: 40 index 1 mmio: [d9f00000, dfefffff]
> 
> YH
> 
> 
> +bus: [00,3f] on node 0 link 1
> +bus: 00 index 0 io port: [0, 2fff]
> +bus: 00 index 1 mmio: [80000000, d9efffff]
> +bus: 00 index 2 mmio: [dff00000, e3ffffff]
> +bus: 00 index 3 mmio: [a0000, bffff]
> +bus: 00 index 4 mmio: [e8000000, ffffffff]
> +bus: 00 index 5 mmio: [480000000, fbffffffff]
> +bus: [40,7f] on node 1 link 2
> +bus: 40 index 0 io port: [3000, ffff]
> +bus: 40 index 1 mmio: [d9f00000, dfefffff]
> +bus: 40 index 2 mmio: [e4000000, e7ffffff]
>  ACPI: bus type pci registered
>  PCI: Using configuration type 1 for base access
>  ACPI: EC: Look up EC in DSDT
> @@ -646,18 +659,18 @@
>    IO window: disabled.
>    MEM window: disabled.
>    PREFETCH window: disabled.
> -  got res [88000000:8801ffff] bus [88000000:8801ffff] flags 27200 for BAR 6 of 0000:41:01.0
> -  got res [88020000:8803ffff] bus [88020000:8803ffff] flags 27200 for BAR 6 of 0000:41:02.0
> +  got res [d9f00000:d9f1ffff] bus [d9f00000:d9f1ffff] flags 27200 for BAR 6 of 0000:41:01.0
> +  got res [d9f20000:d9f3ffff] bus [d9f20000:d9f3ffff] flags 27200 for BAR 6 of 0000:41:02.0
>  PCI: Bridge: 0000:40:10.0
>    IO window: disabled.
>    MEM window: 0xda000000-0xddffffff
> -  PREFETCH window: 0x0000000088000000-0x00000000880fffff
> -  got res [88200000:883fffff] bus [88200000:883fffff] flags 27200 for BAR 6 of 0000:42:01.0
> -  got res [88100000:8813ffff] bus [88100000:8813ffff] flags 27200 for BAR 6 of 0000:42:02.0
> +  PREFETCH window: 0x00000000d9f00000-0x00000000d9ffffff
> +  got res [de000000:de1fffff] bus [de000000:de1fffff] flags 27200 for BAR 6 of 0000:42:01.0
> +  got res [de200000:de23ffff] bus [de200000:de23ffff] flags 27200 for BAR 6 of 0000:42:02.0
>  PCI: Bridge: 0000:40:11.0
>    IO window: 3000-3fff
>    MEM window: 0xdfe00000-0xdfefffff
> -  PREFETCH window: 0x0000000088100000-0x00000000883fffff
> +  PREFETCH window: 0x00000000de000000-0x00000000de2fffff
> 
> 


and those range are not overlapping with IOAPIC BAR allocating
[    0.000000] ACPI: IOAPIC (id[0x08] address[0xd9cf0000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xd9cf0000, GSI 0-23
[    0.000000] ACPI: IOAPIC (id[0x09] address[0xd9fd0000] gsi_base[24])
[    0.000000] IOAPIC[1]: apic_id 9, version 0, address 0xd9fd0000, GSI 24-30
[    0.000000] ACPI: IOAPIC (id[0x0a] address[0xd9fe0000] gsi_base[31])
[    0.000000] IOAPIC[2]: apic_id 10, version 0, address 0xd9fe0000, GSI 31-37
[    0.000000] ACPI: IOAPIC (id[0x0b] address[0xd9ff0000] gsi_base[38])
[    0.000000] IOAPIC[3]: apic_id 11, version 0, address 0xd9ff0000, GSI 38-61

YH

  reply	other threads:[~2009-07-09 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090630180300.GA9971@ldl.fc.hp.com>
     [not found] ` <4A4A5B01.9040200@kernel.org>
     [not found]   ` <20090703225708.GA30664@ldl.fc.hp.com>
2009-07-04 19:30     ` mptsas, msi and the dl585 g2 Yinghai Lu
2009-07-06 16:57       ` dann frazier
2009-07-09 18:59       ` dann frazier
2009-07-09 19:17         ` Yinghai Lu
2009-07-09 19:34           ` Yinghai Lu [this message]
2009-07-09 19:48             ` Yinghai Lu
2009-07-09 20:40               ` James Bottomley
2009-07-09 21:12                 ` Yinghai Lu
2009-07-09 21:41                 ` [PATCH} x86/pci: insert ioapic resource before assign unassigned resource for pci Yinghai Lu
2009-07-09 22:01                   ` dann frazier
2009-07-10 16:36                   ` [PATCH] x86/pci: insert ioapic resource before assign unassigned resource for pci -v2 Yinghai Lu
2009-07-10 20:03                     ` Jesse Barnes
2009-07-10 21:27                     ` Linus Torvalds

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=4A564634.1020708@kernel.org \
    --to=yinghai@kernel.org \
    --cc=dannf@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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