linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Yannick Roehlly <yannick.roehlly@free.fr>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	x86@kernel.org
Subject: Re: [PATCH] pci: increase alignment to make more space for hidden code
Date: Mon, 12 Oct 2009 12:44:52 -0700	[thread overview]
Message-ID: <4AD38734.2040600@kernel.org> (raw)
In-Reply-To: <20091012192242.GA2691@elte.hu>

Ingo Molnar wrote:
> * Yinghai Lu <yinghai@kernel.org> wrote:
> 
>>> This feels like a hack that accidentally covers up the problem.  I 
>>> don't think we understand what's happening well enough.
>> yes, we need to figure out why when acpi=on, those BAR are cleared, 
>> before pci code try to scan and read BAR. (node early pic print out 
>> untouched, but after APCI subsystem is enabled, those BAR got 
>> clearred)
> 
> I'm wondering, how did it get cleared - some AML script told the kernel 
> to clear it?


[    0.012392] ACPI: Core revision 20090521
...
[    0.117217] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.117223] ACPI: bus type pci registered
[    0.117292] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
[    0.117297] PCI: Not using MMCONFIG.
[    0.117301] PCI: Using configuration type 1 for base access
[    0.118064] bio: create slab <bio-0> at 0
[    0.118995] ACPI: EC: Look up EC in DSDT
[    0.125066] ACPI: BIOS _OSI(Linux) query ignored
[    0.127077] ACPI: EC: non-query interrupt received, switching to interrupt mode
[    0.632002] ACPI: EC: missing confirmations, switch off interrupt mode.
[    0.793109] ACPI: Interpreter enabled
[    0.793114] ACPI: (supports S0 S3 S4 S5)
[    0.793139] ACPI: Using IOAPIC for interrupt routing
[    0.793193] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
[    0.795871] PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
[    0.806419] PCI: Using MMCONFIG at e0000000 - efffffff
[    0.812767] ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
[    0.812772] ACPI: EC: driver started in poll mode
[    0.813206] ACPI: No dock devices found.
[    0.813879] ACPI: PCI Root Bridge [PCI0] (0000:00)

could be ACPI EC AML code related.

because with pci=nommconf, the BARs still get cleared.

need the reporter to boot with acpi.debug_layer=0x400000 acpi.debug_level=
to get more info

YH

  reply	other threads:[~2009-10-12 19:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 22:33 Regression in ACPI in 2.6.31-rc5 Ricardo Jorge da Fonseca Marques Ferreira
2009-08-13  3:53 ` Len Brown
2009-08-16  3:00   ` Ricardo Jorge da Fonseca Marques Ferreira
2009-10-06  3:17     ` Len Brown
2009-10-06  4:38       ` Yinghai Lu
     [not found]       ` <4ACAC8F1.1050706@kernel.org>
2009-10-11 21:17         ` [PATCH] pci: increase alignment to make more space for hidden code Yinghai Lu
2009-10-12 16:59           ` Bjorn Helgaas
2009-10-12 17:19             ` Ingo Molnar
2009-10-12 18:43               ` Yinghai Lu
2009-10-12 18:59             ` Yinghai Lu
2009-10-12 19:22               ` Ingo Molnar
2009-10-12 19:44                 ` Yinghai Lu [this message]
2009-10-13  6:08                   ` Bjorn Helgaas
2009-10-13  6:49                     ` Ingo Molnar
2009-10-13 15:15                       ` Bjorn Helgaas
2009-10-13 19:05                     ` Ricardo Jorge da Fonseca Marques Ferreira

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=4AD38734.2040600@kernel.org \
    --to=yinghai@kernel.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jesse.barnes@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=storm@sys49152.net \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=yannick.roehlly@free.fr \
    /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;
as well as URLs for NNTP newsgroup(s).