mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	ACPI mailing list <linux-acpi@vger.kernel.org>
Subject: Re: acpiphp makes noise on every lid close/open
Date: Thu, 2 Nov 2006 17:54:03 -0800	[thread overview]
Message-ID: <20061102175403.279df320.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <20061101115618.GA1683@elf.ucw.cz>

On Wed, 1 Nov 2006 12:56:18 +0100
Pavel Machek <pavel@ucw.cz> wrote:

> Hi!
> 
> With 2.6.19-rc4, acpi complains about "acpiphp_glue: cannot get bridge
> info" each time I close/reopen the lid... On thinkpad x60. Any ideas?
> (-mm1 behaves the same).
> 									Pavel
> -- 
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Looks like acpi is sending a BUS_CHECK notification to acpiphp on the 
PCI Root Bridge whenever the lid opens up.

There is a bug here in that acpiphp shouldn't even be used on the X60 -
it has no hotpluggable slots.  This problem only occurs when acpiphp is
built in, as when a module it just doesn't load.  It appears to not clean
up after itself properly when it finds no ejectable slots and leaves the
acpi notifier installed for the PCI Root Bridge.  The message is printing
"cannot get bridge info" because it partially cleaned some stuff up (without
actually removing the notifier).  I'll put this bug into bugzilla since
I won't have time to fix right away:

http://bugzilla.kernel.org/show_bug.cgi?id=7452

Feel free to add yourself to the CC list if you are interested in being
notified when it is fixed.

Kristen
 

  reply	other threads:[~2006-11-03  1:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 11:56 Pavel Machek
2006-11-03  1:54 ` Kristen Carlson Accardi [this message]
2006-11-05 23:29   ` David Weinehall
2006-11-06  8:19     ` Stefan Seyfried
2006-11-06  9:21     ` Pavel Machek
2006-11-06 13:29       ` Henrique de Moraes Holschuh
2006-11-06 17:32         ` Tomasz Torcz
2006-11-06 19:13         ` Stefan Seyfried
2006-11-06 19:47           ` Henrique de Moraes Holschuh
2006-11-07 20:44       ` David Weinehall
2006-11-07 21:44         ` Kristen Carlson Accardi
2006-11-17 10:22           ` David Weinehall
2006-11-17 15:13             ` Matthew Garrett
2006-11-17 15:15               ` Pavel Machek
2006-11-17 15:37               ` David Weinehall
2006-11-17 15:46                 ` Matthew Garrett
2006-11-17 16:08                   ` David Weinehall
2006-11-17 16:31                     ` Matthew Garrett
2006-11-17 18:18                       ` David Weinehall
2006-11-17 18:35                       ` Matthew Garrett

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=20061102175403.279df320.kristen.c.accardi@intel.com \
    --to=kristen.c.accardi@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®