From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-pm@lists.linux-foundation.org
Cc: ath5k-devel@lists.ath5k.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: PCI hotplug v.s. suspend
Date: Mon, 15 Jun 2009 11:55:15 +0100 [thread overview]
Message-ID: <4A362893.2060607@tuffmail.co.uk> (raw)
Hi,
I triggered a WARNING while hacking on eeepc-laptop's
rfkill-by-pci-hotplug. I saw "Trying to free already-free IRQ" in
ath5k_pci_remove(), because the IRQ was already freed by
ath5k_pci_suspend(). My changes to eeepc-laptop had allowed the PCI
device to be removed while suspended.
Are PCI drivers supposed to handle remove() while suspended?
Thanks
Alan
next reply other threads:[~2009-06-15 10:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:55 Alan Jenkins [this message]
2009-06-15 13:58 ` [linux-pm] PCI hotplug v.s. suspend Alan Stern
2009-06-15 14:03 ` Alan Jenkins
2009-06-15 14:37 ` Alan Stern
2009-06-15 19:58 ` Rafael J. Wysocki
2009-06-15 19:58 ` [linux-pm] " Rafael J. Wysocki
2009-06-15 20:34 ` Alan Stern
2009-06-15 20:51 ` Rafael J. Wysocki
2009-06-15 20:51 ` Rafael J. Wysocki
2009-06-15 20:34 ` Alan Stern
2009-06-16 1:01 ` [ath5k-devel] [linux-pm] " Bob Copeland
2009-06-18 11:51 ` Alan Jenkins
2009-06-18 18:45 ` Alan Stern
2009-06-18 21:18 ` Alan Jenkins
2009-06-19 8:34 ` Alan Jenkins
2009-06-19 11:08 ` Bob Copeland
2009-06-19 11:08 ` [ath5k-devel] " Bob Copeland
2009-06-19 8:34 ` Alan Jenkins
2009-06-18 21:18 ` Alan Jenkins
2009-06-18 18:45 ` Alan Stern
2009-06-18 11:51 ` Alan Jenkins
2009-06-16 1:01 ` Bob Copeland
2009-06-15 14:37 ` Alan Stern
2009-06-15 14:03 ` Alan Jenkins
2009-06-15 13:58 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 10:55 Alan Jenkins
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=4A362893.2060607@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@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.