public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Pavel Machek <pavel@ucw.cz>
Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	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: Tue, 7 Nov 2006 21:44:09 +0100	[thread overview]
Message-ID: <20061107204409.GA37488@vasa.acc.umu.se> (raw)
In-Reply-To: <20061106092117.GB2175@elf.ucw.cz>

On Mon, Nov 06, 2006 at 10:21:17AM +0100, Pavel Machek 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).
> > > 
> > > 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.
> > 
> > How about the docking station?
> 
> "Dock" for x60 only contains cdrom slot and aditional slots, no PCI or
> PCMCIA slots.

Well, when I press the undock button on the dock without the acpiphp
module loaded, I never get the green light that confirms that removing
the laptop is safe.  If acpiphp is loaded, things work just fine.


Regards: David
-- 
 /) David Weinehall <tao@acc.umu.se> /) Northern lights wander      (\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\)  http://www.acc.umu.se/~tao/    (/   Full colour fire           (/

  parent reply	other threads:[~2006-11-07 20:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 11:56 acpiphp makes noise on every lid close/open Pavel Machek
2006-11-03  1:54 ` Kristen Carlson Accardi
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 19:13         ` Stefan Seyfried
2006-11-06 19:47           ` Henrique de Moraes Holschuh
2006-11-07 20:44       ` David Weinehall [this message]
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=20061107204409.GA37488@vasa.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=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