public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Lopes <alvieboy-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI PCI bus mismatch ?
Date: Thu, 06 Feb 2003 12:07:25 +0000	[thread overview]
Message-ID: <3E424FFD.3040504@alvie.com> (raw)
In-Reply-To: <3E413D88.2020001-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>

OK, I tracked the problem down to acpi_os_derive_pci_id(). If I remove 
the call to acpi_os_derive_pci_id() in acpi_ev_pci_config_region_setup() 
it works fine.

Will do some tests on 2.5.x now and let you know.


Alvaro Lopes wrote:

> Hi all
>
> I was debugging ACPI in my laptop and was comparing 2.4.18 against 
> latest 2.4.19pre4-ac1+acpi, when I found this:
>
> There's a method in my DSTD that looks like this:
>
>        Method (_L08, 0, Serialized)
>        {
>            Store (\_SB.PCI0.PCIB.BRGB, Local0)
>            ShiftLeft (Local0, 0x18, Local0)
>            Or (Local0, 0x0020B10B, Local0)
>            Store (0xAF, \_SB.MEM.IEDI)
> .
> .
> .
>
> When it runs on 2.4.18, I can see it working almost properly. I 
> debugged exregion and this was the result, with my comments:
>
>
> Feb  5 16:18:09 supernova kernel: exregion-0353 [25] 
> Ex_pci_config_space_ha: Pci_config 0 (8) Seg(0000) Bus(0000) Dev(001e) 
> Func(0000) Reg(0019)
>    This one is reading \_SB.PCI0.PCIB.BRGB,  device 0x1e @ bus #0, 
> which according to lspci, is my PCI bridge (which is correct):
>
>    00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI 
> (-M) (rev 42)
>
>
> But, when I boot 2.4.20pre4-ac1+acpi, the handler instead of using Bus 
> #0, uses Bus #2:
>
> Feb  5 16:25:28 supernova kernel: exregion-0352 [25] 
> ex_pci_config_space_ha: pci_config 0 (8) Seg(0000) Bus(0002) Dev(001e) 
> Func(0000) Reg(0019)
>
> .... and always reads 0xFF.
>
> lspci with 2.4.20pre4-ac1+acpi is:
>
> alvieboy@supernova:~$ uname -a
> Linux supernova 2.4.21-pre4-ac1 #2 SMP Ter Fev 4 12:18:03 WET 2003 
> i686 unknown unknown GNU/Linux
> alvieboy@supernova:~$ lspci
> 00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host 
> Bridge (rev 05)
> 00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP 
> Bridge (rev 05)
> 00:1d.0 USB Controller: Intel Corp.: Unknown device 2482 (rev 02)
> 00:1d.1 USB Controller: Intel Corp.: Unknown device 2484 (rev 02)
> 00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (-M) 
> (rev 42)
> 00:1f.0 ISA bridge: Intel Corp.: Unknown device 248c (rev 02)
> 00:1f.1 IDE interface: Intel Corp.: Unknown device 248a (rev 02)
> 00:1f.5 Multimedia audio controller: Intel Corp. AC'97 Audio 
> Controller (rev 02)
> 00:1f.6 Modem: Intel Corp.: Unknown device 2486 (rev 02)
> 01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 
> 0175 (rev a3)
> 02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) Chipset 
> Ethernet Controller (rev 42)
> 02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to 
> Cardbus Bridge with ZV Support (rev 32)
> 02:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to 
> Cardbus Bridge with ZV Support (rev 32)
>
>
> Anyone sees which might me causing this ?
>
> TYA
>
>


-- 

Álvaro Lopes 
---------------------
A .sig is just a .sig




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

      parent reply	other threads:[~2003-02-06 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 16:36 ACPI PCI bus mismatch ? Alvaro Lopes
     [not found] ` <3E413D88.2020001-JkNoWtNHh5AAvxtiuMwx3w@public.gmane.org>
2003-02-06 12:07   ` Alvaro Lopes [this message]

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=3E424FFD.3040504@alvie.com \
    --to=alvieboy-jknowtnhh5aavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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