Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Greg KH <gregkh@linux.com>, Oliver Neukum <oneukum@suse.de>
Subject: Re: acpiphp and pciehp not working together on Thinkpad X200s
Date: Mon, 12 Aug 2013 23:34:34 +0200	[thread overview]
Message-ID: <520954EA.2060308@message-id.googlemail.com> (raw)
In-Reply-To: <CAErSpo6HThAr7MXX1-qpzryy7=F7+eMfNK_zWuP9j5arLb1RXA@mail.gmail.com>

Hi Bjorn,

Am 12.08.2013 19:21, schrieb Bjorn Helgaas:

> Thanks for the report, Stefan.  I opened
> https://bugzilla.kernel.org/show_bug.cgi?id=60736 so we don't forget
> about this.  If you could attach complete dmesg logs for both cases
> (working and failing) to that bugzilla, that would be great.  An
> acpidump might also be interesting, since the ACPI namespace
> determines what acpiphp does.

Ok, I added all that information to the bug.

> I suspect that we're being too aggressive about determining when we
> should use one or the other of acpiphp and pciehp.  We basically
> decide up front which one we expect the platform to use, and we only
> listen to signals from that one.  But I wonder if we should just
> prepare for signals from both.

Actually I booted an older Kernel (3.7.10, openSUSE 12.3 kernel) which
has both drivers configured as modules.
The interesting thing is: I was not able to load acpiphp there, it
errored out with ENODEV.
So maybe something changed, making acpiphp more (too?) relaxed.

Should I try building the latest kernel with both drivers as modules to
see if this makes a difference?

Best regards,

	Stefan
-- 
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

  reply	other threads:[~2013-08-12 21:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11  8:13 acpiphp and pciehp not working together on Thinkpad X200s Stefan Seyfried
2013-08-11 21:25 ` Rafael J. Wysocki
2013-08-11 21:18   ` Stefan Seyfried
2013-08-11 21:36     ` Rafael J. Wysocki
2013-08-12 17:21       ` Bjorn Helgaas
2013-08-12 21:34         ` Stefan Seyfried [this message]
2013-08-12 21:43           ` Bjorn Helgaas
2013-08-12 22:54         ` Rafael J. Wysocki
2013-08-13  9:50       ` Stefan Seyfried
2013-08-13 12:08         ` 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=520954EA.2060308@message-id.googlemail.com \
    --to=stefan.seyfried@googlemail.com \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=rjw@sisk.pl \
    /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