From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: acpi_bus_register_driver() returns -ENODEV after resume
Date: Tue, 2 Sep 2003 00:26:19 +0200 [thread overview]
Message-ID: <20030901222619.GC27945@hell.org.pl> (raw)
Hi,
I've received some feedback about problems loading the asus_acpi driver
back after swsusp resume. I managed to hit that problem on a 2.4.21 +
20030619 ACPI + swsusp1.1-rc2. I don't know yet if it is present in more
recent versions, since this behaviour is not common (at least on my
machine). Usually, the module can be loaded and unloaded without problems.
Anyway, judging on my quick glance at the code, it would seem that something
disables acpi (i.e. sets acpi_disabled to a non-zero value) somewhere
during the suspend / resume cycle, which in turn causes
acpi_bus_register_driver to return -ENODEV. Is my reasoning correct, or am
I missing some codepath? If not, it would signify a bug in ACPI / swsusp
interaction. I'll try yet to hit this on a recent kernel.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2003-09-01 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 22:26 Karol Kozimor [this message]
[not found] ` <20030901222619.GC27945-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-09-02 22:39 ` [ACPI] acpi_bus_register_driver() returns -ENODEV after resume Patrick Mochel
[not found] ` <Pine.LNX.4.33.0309021529410.1737-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-09-02 22:51 ` Patrick Mochel
2003-09-02 23:22 ` Karol Kozimor
[not found] ` <20030902232208.GA17674-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-09-02 23:23 ` Patrick Mochel
2003-09-03 0:58 ` Matthew Wilcox
2003-09-08 22:07 ` Karol Kozimor
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=20030901222619.GC27945@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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