From: Yinghai Lu <yinghai@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, Ingo Molnar <mingo@elte.hu>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>,
cebbert@redhat.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 13940] iwlagn and sky2 stopped working, ACPI-related
Date: Tue, 25 Aug 2009 12:00:42 -0700 [thread overview]
Message-ID: <4A9434DA.1010603@kernel.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0908251127460.3218@localhost.localdomain>
Linus Torvalds wrote:
>
> On Tue, 25 Aug 2009, Yinghai Lu wrote:
>> please try to attached patch, that will increae alignment from 32M to 64M.
>
> Hmm. That may indeed fix the problem, because we have:
>
> - working-2.6.30.log:
>
> Allocating PCI resources starting at b8000000 (gap: b6000000:4a000000)
>
> - not-working-2.6.31.log:
>
> Allocating PCI resources starting at b6000000 (gap: b6000000:4a000000)
>
> HOWEVER. We also have:
>
> - working-2.6.31_acpi=off.log:
>
> Allocating PCI resources starting at b6000000 (gap: b6000000:4a000000)
>
> ie it really does seem to be ACPI-related somehow: starting PCI
> allocations at that b6000000 address works perfectly fine if ACPI is not
> enabled.
>
> In the not-working version, we end up getting:
>
> [ 1.408588] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:07
> [ 1.408593] pci 0000:00:1c.4: IO window: 0x2000-0x2fff
> [ 1.408600] pci 0000:00:1c.4: MEM window: 0xb6000000-0xb60fffff
> [ 1.408606] pci 0000:00:1c.4: PREFETCH window: disabled
> [ 1.408623] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:08
> [ 1.408626] pci 0000:00:1c.5: IO window: disabled
> [ 1.408633] pci 0000:00:1c.5: MEM window: 0xb6100000-0xb61fffff
> [ 1.408639] pci 0000:00:1c.5: PREFETCH window: disabled
>
>
> while in the working version we have:
>
> - ACPI off - looks like a BIOS allocated memory window:
>
> [ 0.290854] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:07
> [ 0.290854] pci 0000:00:1c.4: IO window: 0x3000-0x3fff
> [ 0.290854] pci 0000:00:1c.4: MEM window: 0xf4500000-0xf45fffff
> [ 0.290854] pci 0000:00:1c.4: PREFETCH window: disabled
> [ 0.290854] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:08
> [ 0.290854] pci 0000:00:1c.5: IO window: disabled
> [ 0.290854] pci 0000:00:1c.5: MEM window: 0xf4600000-0xf46fffff
> [ 0.290854] pci 0000:00:1c.5: PREFETCH window: disabled
interesting, when acpi=off, BIOS does allocate resource for them
[ 0.261960] pci 0000:07:00.0: reg 10 64bit mmio: [0xf4500000-0xf4503fff]
[ 0.261970] pci 0000:07:00.0: reg 18 io port: [0x3000-0x30ff]
[ 0.262049] pci 0000:07:00.0: supports D1 D2
[ 0.262051] pci 0000:07:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.262058] pci 0000:07:00.0: PME# disabled
[ 0.272117] pci 0000:00:1c.4: bridge io port: [0x3000-0x3fff]
[ 0.272122] pci 0000:00:1c.4: bridge 32bit mmio: [0xf4500000-0xf45fffff]
[ 0.272212] pci 0000:08:00.0: reg 10 64bit mmio: [0xf4600000-0xf4601fff]
[ 0.272321] pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
[ 0.272330] pci 0000:08:00.0: PME# disabled
[ 0.280128] pci 0000:00:1c.5: bridge 32bit mmio: [0xf4600000-0xf46fffff]
>
> - ACPI on - we allocated the memory window, but at 0xb8000000+, rather
> than directly after end-of-RAM:
>
> [ 0.842970] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:07
> [ 0.842975] pci 0000:00:1c.4: IO window: 0x2000-0x2fff
> [ 0.842983] pci 0000:00:1c.4: MEM window: 0xb8000000-0xb80fffff
> [ 0.842989] pci 0000:00:1c.4: PREFETCH window: disabled
> [ 0.843012] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:08
> [ 0.843016] pci 0000:00:1c.5: IO window: disabled
> [ 0.843023] pci 0000:00:1c.5: MEM window: 0xb8100000-0xb81fffff
> [ 0.843029] pci 0000:00:1c.5: PREFETCH window: disabled
>
> ie for some reason ACPI caused that bus to be re-allocated, and
> re-allocating it right after the memory window doesn't work.
>
> Crazy.
>
> I wonder what is hiding at that 0xb6000000 address. And while I think that
> in this case rounding up to 64MB will fix it, I worry that our old model
> (of never starting directly after RAM, even if it was aligned) may not
> have been safer.
>
acpi does clear sth.
YH
next prev parent reply other threads:[~2009-08-25 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13940-13546@http.bugzilla.kernel.org/>
[not found] ` <200908251555.n7PFt7Wt015763@demeter.kernel.org>
2009-08-25 17:56 ` [Bug 13940] iwlagn and sky2 stopped working, ACPI-related Yinghai Lu
2009-08-25 18:42 ` Linus Torvalds
2009-08-25 19:00 ` Yinghai Lu [this message]
2009-08-26 17:44 ` Yinghai Lu
2009-10-01 19:53 2.6.32-rc1-git2: Reported regressions 2.6.30 -> 2.6.31 Rafael J. Wysocki
2009-10-01 19:55 ` [Bug #13940] iwlagn and sky2 stopped working, ACPI-related Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2009-09-06 17:15 2.6.31-rc9: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-09-06 17:24 ` [Bug #13940] iwlagn and sky2 stopped working, ACPI-related Rafael J. Wysocki
2009-09-06 17:24 ` Rafael J. Wysocki
2009-09-06 20:55 ` Ricardo Jorge da Fonseca Marques Ferreira
2009-09-06 20:55 ` Ricardo Jorge da Fonseca Marques Ferreira
2009-09-06 21:11 ` Rafael J. Wysocki
2009-08-25 20:00 2.6.31-rc7-git2: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-08-25 20:34 ` [Bug #13940] iwlagn and sky2 stopped working, ACPI-related Rafael J. Wysocki
2009-08-25 20:34 ` Rafael J. Wysocki
2009-08-26 0:00 ` Ricardo Jorge da Fonseca Marques Ferreira
2009-08-26 0:00 ` Ricardo Jorge da Fonseca Marques Ferreira
[not found] ` <200908260100.57360.storm-cOTmPFJTJjbk1uMJSBkQmQ@public.gmane.org>
2009-08-26 20:58 ` Rafael J. Wysocki
2009-08-26 20:58 ` Rafael J. Wysocki
2009-08-19 20:20 2.6.31-rc6-git5: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-08-19 20:26 ` [Bug #13940] iwlagn and sky2 stopped working, ACPI-related Rafael J. Wysocki
2009-08-19 23:54 ` Ricardo Jorge da Fonseca Marques Ferreira
2009-08-19 23:54 ` Ricardo Jorge da Fonseca Marques Ferreira
[not found] ` <200908200054.36939.storm-cOTmPFJTJjbk1uMJSBkQmQ@public.gmane.org>
2009-08-20 14:59 ` Rafael J. Wysocki
2009-08-20 14:59 ` Rafael J. Wysocki
2009-08-09 20:36 2.6.31-rc5-git5: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-08-09 20:44 ` [Bug #13940] iwlagn and sky2 stopped working, ACPI-related Rafael J. Wysocki
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=4A9434DA.1010603@kernel.org \
--to=yinghai@kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=cebbert@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=storm@sys49152.net \
--cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.