All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [regression][bisected] zx1 AGP GART no more detected since merge of 'acpi-scan' branch
Date: Wed, 21 May 2014 19:09:08 +0000	[thread overview]
Message-ID: <537CF9D4.2070504@intel.com> (raw)
In-Reply-To: <CAA9xbM4=Rt3hVYEUv2GoWNex8cCeaxnBUWEc4_6mF_cLRLZZ2A@mail.gmail.com>

Hi,

On 5/21/2014 5:31 PM, Émeric MASCHINO wrote:
> Again,
>
> I'm now quite confident that the regression comes from commit
> 66345d5f79fcfa0214f5d98763643d4ee8e6965d as the description talks
> about an ordering issue on hp rx2600 between the SBA I/O MMU driver
> and the container scan handler.
>
> First, I'm running on hp zx6000 that's a rx2600 with an AGP slot.
> Then, defining DEBUG_SBA_INIT in sba_iommu.c clearly shows in dmesg
> logs that, for working kernel 3.10.40, ioc_init (and thus
> ioc_iova_init) is called once the ACPI/PCI resources (is this the
> right terminology?) have been parsed, whereas for non-working kernel
> 3.11-rc1, ioc_init is called at the very beginning.

Quite evidently, acpi_sba_ioc_add() has to be executed after 
acpi_pci_root_add()
and we need to enforce that ordering somehow.

Please create a bug entry for that at bugzilla.kernel.org (against 
ACPI), mark it as a regression and
assign it to rjw@rjwysocki.net.

Thanks,
Rafael


  parent reply	other threads:[~2014-05-21 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  0:32 [regression][bisected] zx1 AGP GART no more detected since merge of 'acpi-scan' branch Émeric MASCHINO
2014-05-21 13:23 ` Émeric MASCHINO
2014-05-21 15:31 ` Émeric MASCHINO
2014-05-21 19:09 ` Rafael J. Wysocki [this message]
2014-05-21 22:09 ` Émeric MASCHINO

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=537CF9D4.2070504@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=linux-ia64@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 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.