Linux ACPI
 help / color / mirror / Atom feed
From: Leho Kraav <leho@kraav.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [Bug 57961] ExpressCard hot-remove and hot-add not recognized by acpiphp
Date: Fri, 23 Aug 2013 23:35:32 +0300	[thread overview]
Message-ID: <5217C794.1020902@kraav.com> (raw)
In-Reply-To: <CAErSpo5B6dvY6ri1-NajudgS1v1tyTCCicb9vMrOYP=8yv4pPg@mail.gmail.com>

>
> I don't know anything about the LID notifications.
>
> As far as the bus checks on \_SB_.PCI0, I think that message is new or
> possibly we register for those notifications on more devices that we
> previously did.  If your laptop suspended when closing the lid, it
> doesn't surprise me that we get the Bus Check on resume, because that
> might be the only way we could discover device additions or removals
> that happened while suspended.  I'm not sure why we would get them on
> suspend.

I don't suspend on lid close, actually. I close the lid just to carry 
the laptop around, and always suspend manually.

Thanks for taking a look. I guess the key takeaway here is that the 
notify message is harmless and I should look at somewhere else to figure 
out why I'm not getting a LID event.

  reply	other threads:[~2013-08-23 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-57961-41252@https.bugzilla.kernel.org/>
     [not found] ` <bug-57961-41252-X2PJk78p44@https.bugzilla.kernel.org/>
2013-08-23 14:58   ` [Bug 57961] ExpressCard hot-remove and hot-add not recognized by acpiphp Bjorn Helgaas
2013-08-23 19:54     ` Leho Kraav
2013-08-23 20:31       ` Bjorn Helgaas
2013-08-23 20:35         ` Leho Kraav [this message]
2013-08-23 20:40           ` Bjorn Helgaas
     [not found]             ` <5217C985.20103@kraav.com>
2013-08-23 20:52               ` Bjorn Helgaas

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=5217C794.1020902@kraav.com \
    --to=leho@kraav.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox