From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Bob Copeland <me@bobcopeland.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath5k-devel@venema.h4ckr.net,
Alan Stern <stern@rowland.harvard.edu>,
linux-pci@vger.kernel.org
Subject: Re: [ath5k-devel] [linux-pm] PCI hotplug v.s. suspend
Date: Thu, 18 Jun 2009 12:51:26 +0100 [thread overview]
Message-ID: <4A3A2A3E.7090300@tuffmail.co.uk> (raw)
In-Reply-To: <20090616010101.GA11412@hash.localnet>
Bob Copeland wrote:
> On Mon, Jun 15, 2009 at 09:58:30PM +0200, Rafael J. Wysocki wrote:
>
>> On Monday 15 June 2009, Alan Stern wrote:
>>
>>> I'm not sure whether the example is trustworthy. There was some
>>> discussion quite a while ago regarding whether drivers should free
>>> their IRQs during suspend, but I don't remember what the outcome was.
>>>
>> No, they shouldn't.
>>
>> That's why we do the entire suspend_device_irqs() thing etc.
>>
>
> So, ath5k needs something like the following?
>
> diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
> index 55f7de0..0107cd6 100644
> --- a/drivers/net/wireless/ath/ath5k/base.c
> +++ b/drivers/net/wireless/ath/ath5k/base.c
> @@ -665,7 +665,6 @@ ath5k_pci_suspend(struct pci_dev *pdev, pm_message_t state)
>
> ath5k_led_off(sc);
>
> - free_irq(pdev->irq, sc);
> pci_save_state(pdev);
> pci_disable_device(pdev);
> pci_set_power_state(pdev, PCI_D3hot);
> @@ -686,18 +685,8 @@ ath5k_pci_resume(struct pci_dev *pdev)
> if (err)
> return err;
>
> - err = request_irq(pdev->irq, ath5k_intr, IRQF_SHARED, "ath", sc);
> - if (err) {
> - ATH5K_ERR(sc, "request_irq failed\n");
> - goto err_no_irq;
> - }
> -
> ath5k_led_enable(sc);
> return 0;
> -
> -err_no_irq:
> - pci_disable_device(pdev);
> - return err;
> }
> #endif /* CONFIG_PM */
>
>
Unfortunately this makes it worse. My eeepc-laptop hacks are now in
wireless-testing. If I apply the above patch to wireless-testing and
"remove" the device while suspended, I get a soft hang on resume.
Suspending without removal works fine.
I can see a BUG if I boot with no_console_suspend
Unable to handle kernel NULL pointer dereference
IP: klist_put
Tainted: G W
Process s2disk
Call trace:
? klist_del
? device_del
? device_unregister
? pci_stop_dev
? pci_stop_bus
? pci_remove_device
? eeepc_rfkill_hotplug [eeepc_laptop]
? eeepc_hotk_resume [eeepc_laptop]
? acpi_device_resume
? device_resume
? hibernation_snapshot
? release_console_sem
? snapshot_ioctl
? snapshot_ioctl
? vfs_ioctl
? do_vfs_ioctl
? n_tty_write
? vfs_write
? sys_ioctl
? syscall_call
next prev parent reply other threads:[~2009-06-18 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:55 PCI hotplug v.s. suspend Alan Jenkins
2009-06-15 13:58 ` [linux-pm] " 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 20:34 ` Alan Stern
2009-06-15 20:51 ` Rafael J. Wysocki
2009-06-16 1:01 ` [ath5k-devel] " Bob Copeland
2009-06-18 11:51 ` Alan Jenkins [this message]
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
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=4A3A2A3E.7090300@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).